# Sponsorship

[[Source]](https://github.com/tequdev/rippled/blob/sponsor/include/xrpl/protocol/detail/ledger_entries.macro#L611-L624)

A  ledger entry represents a sponsoring relationship between a sponsor and a sponsee. This allows sponsors to *pre-fund* sponsees, if they so desire.

Note
This object does not need to be created in order to sponsor accounts. It is an offered convenience, so that sponsors do not have to co-sign every sponsored transaction if they don't want to, especially for transaction fees. It also allows sponsors to set a maximum balance even if they still want to co-sign transactions.

*(Requires the [Sponsor amendment](https://xls.xrpl.org/xls/XLS-0068-sponsored-fees-and-reserves.html) )*

## Example JSON


```json
{
  "LedgerEntryType": "Sponsorship",
  "Flags": 0,
  "Owner": "rN7n7otQDd6FczFgLdlqtyMVrn3HMfXpf",
  "Sponsee": "rfkDkFai4jUfCvAJiZ5Vm7XvvWjYvDqeYo",
  "FeeAmount": "1000000",
  "MaxFee": "1000",
  "ReserveCount": 5,
  "OwnerNode": "0000000000000000",
  "SponseeNode": "0000000000000000",
  "PreviousTxnID": "1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF",
  "PreviousTxnLgrSeq": 12345678
}
```

##  Fields

In addition to the [common ledger entry fields](/docs/xls-68-sponsored-fees-and-reserves/references/ledger-entries/updated-ledger-entries#common-ledger-entry-updates#common-ledger-entry-fields), a  entry has the following fields:

| Field Name | JSON Type | [Internal Type](https://xrpl.org/docs/references/protocol/binary-format/) | Required? | Description |
|  --- | --- | --- | --- | --- |
| `FeeAmount` | String | Amount | No | The remaining amount of XRP that the sponsor has provided for the sponsee to use for transaction fees. |
| `MaxFee` | String | Amount | No | The maximum fee per transaction that the sponsor will cover. This field helps prevent excessive draining of the pre-funded fee pool. If the sponsee submits a transaction with a fee exceeding this value, the transaction fails. |
| `Owner` | String | AccountID | Yes | The address of the sponsor account. This account pays the reserve for this object. |
| `OwnerNode` | String | UInt64 | Yes | A hint indicating which page of the sponsor's owner directory links to this object, in case the directory consists of multiple pages. |
| `PreviousTxnID` | String | Hash256 | Yes | The identifying hash of the transaction that most recently modified this entry. |
| `PreviousTxnLgrSeq` | Number | UInt32 | Yes | The [ledger index](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#ledger-index) of the ledger that contains the transaction that most recently modified this object. |
| `ReserveCount` | Number | UInt32 | No | The remaining number of owner reserves the sponsor has pre-funded for the sponsee. |
| `Sponsee` | String | AccountID | Yes | The address of the sponsee account associated with this relationship. |
| `SponseeNode` | String | UInt64 | Yes | A hint indicating which page of the sponsee's owner directory links to this object, in case the directory consists of multiple pages. |


##  Flags

A  entry can have the following flags:

| Flag Name | Flag Value | Description |
|  --- | --- | --- |
| `lsfSponsorshipRequireSignForFee` | `0x00010000` | If enabled, every transaction that uses this sponsorship for fees requires a signature from the sponsor. If disabled, no signature is necessary, as the existence of the  object is sufficient. |
| `lsfSponsorshipRequireSignForReserve` | `0x00020000` | If enabled, every transaction that uses this sponsorship for reserves requires a signature from the sponsor. If disabled, no signature is necessary, as the existence of the  object is sufficient. |


## Deleting a Sponsorship Object

Either the sponsor or the sponsee can delete a  object using the [SponsorshipSet transaction](/docs/xls-68-sponsored-fees-and-reserves/references/transactions/sponsorshipset) with the `tfDeleteObject` flag enabled.

Warning
The  object is a [deletion blocker](https://xrpl.org/docs/concepts/accounts/deleting-accounts#requirements). A sponsor cannot delete their account until all their  objects are removed.

## Sponsorship ID Format

The ID of a  entry is the [SHA-512Half](https://xrpl.org/docs/references/protocol/data-types/basic-data-types#hashes) of the following values, concatenated in order:

1. The Sponsorship space key (`0x003E`)
2. The AccountID of the sponsor (`Owner` field)
3. The AccountID of the `Sponsee`