# SponsorshipTransfer

[[Source]](https://github.com/tequdev/rippled/blob/sponsor/src/libxrpl/tx/transactors/Sponsor/SponsorshipTransfer.cpp)

Create, transfer, or end reserve sponsorship for a ledger object or account. The transaction can be submitted by the sponsor or sponsee, depending on the required operation. See [Sponsorship Scenarios](#sponsorship-scenarios) for details on each operation.

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

## Example JSON


```json
{
    "TransactionType": "SponsorshipTransfer",
    "Account": "rN7n7otQDd6FczFgLdlqtyMVrn3HMfXpf",
    "ObjectID": "1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF",
    "Flags": 2,
    "Fee": "12",
    "Sequence": 43
}
```

##  Fields

In addition to the [common fields](/docs/xls-68-sponsored-fees-and-reserves/references/transactions/updated-common-transaction-fields#common-transaction-updates#common-transaction-fields),  transactions use the following fields:

| Field Name | JSON Type | [Internal Type](https://xrpl.org/docs/references/protocol/binary-format/) | Required? | Description |
|  --- | --- | --- | --- | --- |
| `ObjectID` | String | Hash256 | No | The ID of the ledger object to transfer sponsorship. Required if the transaction is dealing with a sponsored object, rather than a sponsored account. If omitted, the transaction refers to the `Account` sending the transaction. |
| `Sponsee` | String | AccountID | No | The wallet address of the sponsee account. Required if the sponsor is ending a sponsorship on behalf of a sponsee. If omitted, the `Account` field is assumed to be the sponsee. |


##  Flags

 transactions support additional values in the `Flags` field, as follows:

| Flag Name | Hex Value | Decimal Value | Description |
|  --- | --- | --- | --- |
| `tfSponsorshipEnd` | `0x00000001` | 1 | End an existing sponsorship. The reserve burden returns to the object's owner. |
| `tfSponsorshipCreate` | `0x00000002` | 2 | Create a new sponsorship for an unsponsored object or account. |
| `tfSponsorshipReassign` | `0x00000004` | 4 | Transfer an existing sponsorship to a new sponsor. |


## Sponsorship Scenarios

Create Sponsorship
Use the `tfSponsorshipCreate` flag to sponsor an object or account. Only the sponsee can submit the transaction with this configuration. The reserve sponsorship transfers to the account specified in the `Sponsor` field.

To submit a transaction for this scenario:

- Include the `ObjectID` field when sponsoring an object. Omit when sponsoring an account.
- The target object or account must not currently be sponsored.
- Provide the `Sponsor` field and the `SponsorFlags.spfSponsorReserve` flag.
- Include the `SponsorSignature` when sponsoring an account. This is optional when sponsoring an object.
- Do not include the `Sponsee` field.


When successful:

- The `Sponsor` field is set on the object or account.
- The new sponsor's `SponsoringOwnerCount` or `SponsoringAccountCount` is incremented.
- For objects, the owner's `SponsoredOwnerCount` is also incremented.


Reassign Sponsorship
Use the `tfSponsorshipReassign` flag to transfer an existing sponsorship to a new sponsor specified in the `Sponsor` field. Only the sponsee can submit the transaction with this configuration.

To submit a transaction for this scenario:

- Include the `ObjectID` field when reassigning sponsorship of an object. Omit when reassigning sponsorship of an account.
- The target object or account must currently be sponsored.
- Provide the `Sponsor` field with the `SponsorFlags.spfSponsorReserve` flag.
- Include the `SponsorSignature` when sponsoring an account. This is optional when sponsoring an object.
- Do not include the `Sponsee` field.


When successful:

- The `Sponsor` field is updated to the new sponsor.
- The old sponsor's `SponsoringOwnerCount` or `SponsoringAccountCount` is decremented.
- The new sponsor's `SponsoringOwnerCount` or `SponsoringAccountCount` is incremented.


End Sponsorship
Use the `tfSponsorshipEnd` flag to dissolve an existing sponsorship. Either the sponsor or the sponsee can submit the transaction with this configuration. The reserve burden returns to the object or account owner.

To submit a transaction for this scenario:

- Provide the `ObjectID` when ending sponsorship for an object. Omit when ending sponsorship for an account.
- The target object or account must currently be sponsored.
- Do not include the `Sponsor` and the `SponsorFlags.spfSponsorReserve` flag.


When successful:

- The `Sponsor` field is removed from the object or account.
- The old sponsor's `SponsoringOwnerCount` or `SponsoringAccountCount` is decremented.
- For objects, the owner's `SponsoredOwnerCount` is also decremented.


## Error Cases

Besides errors that can occur for all transactions,  transactions can result in the following [transaction result codes](https://xrpl.org/docs/references/protocol/transactions/transaction-results):

| Error Code | Description |
|  --- | --- |
| `tecINSUFFICIENT_RESERVE` | The owner or new sponsor does not have sufficient XRP to cover the reserve for this object or account. |
| `tecNO_ENTRY` | The `ObjectID` is specified but does not exist on the ledger. |
| `tecNO_PERMISSION` | The transaction lacks the required permissions. This can occur when:The submitter is not the current sponsor or owner when ending a sponsorship.The submitter is not the owner when creating or reassigning a sponsorship.The object or account is already sponsored when creating a sponsorship.The object or account is not sponsored when reassigning or ending a sponsorship.The `Sponsor` field is missing when creating or reassigning a sponsorship.The `Sponsor` field is present when ending a sponsorship. |
| `temINVALID_FLAG` | The transaction has invalid flags. This can occur when:The transaction does not have exactly one of `tfSponsorshipCreate`, `tfSponsorshipReassign`, or `tfSponsorshipEnd` set.The `spfSponsorReserve` flag is missing when creating or reassigning a sponsorship.The `spfSponsorReserve` flag is present when ending a sponsorship. |
| `temMALFORMED` | The transaction is malformed. This can occur when:The `Sponsee` field is present when creating or reassigning a sponsorship.The `Sponsee` field is the same as the `Account` field.Sponsoring an account without providing the `SponsorSignature` field. |