AccountSet

[Source]

An AccountSet transaction modifies the properties of an account in the XRP Ledger.

Example AccountSet JSON

{
    "TransactionType": "AccountSet",
    "Account" : "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
    "Fee": "12",
    "Sequence": 5,
    "Domain": "6578616D706C652E636F6D",
    "SetFlag": 5,
    "MessageKey": "03AB40A0490F9B7ED8DF29D246BF2D6269820A0EE7742ACDD457BEA7C7D0931EDB"
}

Query example transaction. >

AccountSet Fields

In addition to the common fields, AccountSet transactions use the following fields:

If none of these options are provided, then the AccountSet transaction has no effect (beyond destroying the transaction cost). See Cancel or Skip a Transaction for more details.

Domain

The Domain field is represented as the hex string of the lowercase ASCII of the domain. For example, the domain example.com would be represented as "6578616D706C652E636F6D".

To remove the Domain field from an account, send an AccountSet with the Domain set to an empty string.

You can put any domain in your account's Domain field. To prove that an account and domain belong to the same person or business, you need a "two-way link":

• Accounts you own should have a domain you own in the Domain field.
• At that domain, host an xrp-ledger.toml file listing accounts you own, and optionally other information about how you use the XRP Ledger.

AccountSet Flags

There are several options which can be either enabled or disabled for an account. Account options are represented by different types of flags depending on the situation:

• The AccountSet transaction type has several "AccountSet Flags" (prefixed asf) that can enable an option when passed as the SetFlag parameter, or disable an option when passed as the ClearFlag parameter. Newer options have only this style of flag. You can enable up to one asf flag per transaction, and disable up to one asf flag per transaction.
• The AccountSet transaction type has several transaction flags (prefixed tf) that can be used to enable or disable specific account options when passed in the Flags parameter. You can enable and disable a combination of settings in one transaction using multiple tf flags, but not all settings have tf flags.
• The AccountRoot ledger object type has several ledger-state-flags (prefixed lsf) which represent the state of particular account options within a particular ledger. These settings apply until a transaction changes them.

To enable or disable Account Flags, use the SetFlag and ClearFlag parameters of an AccountSet transaction. AccountSet flags have names that begin with asf.

All flags are disabled by default.

The available AccountSet flags are:

To enable the asfDisableMaster or asfNoFreeze flags, you must authorize the transaction by signing it with the master key pair. You cannot use a regular key pair or a multi-signature. You can disable asfDisableMaster (that is, re-enable the master key pair) using a regular key pair or multi-signature.

The following Transaction flags (tf flags), specific to the AccountSet transaction type, serve the same purpose. Due to limited space, some settings do not have associated tf flags, and new tf flags are not being added to the AccountSet transaction type. You can use a combination of tf and asf flags to enable multiple settings with a single transaction.

Caution: The numeric values of tf and asf flags in transactions do not match up with the values they set in the accounts "at rest" in the ledger. To read the flags of an account in the ledger, see AccountRoot flags.

Blocking Incoming Transactions

Incoming transactions with unclear purposes may be an inconvenience for financial institutions, who would have to recognize when a customer made a mistake, and then potentially refund accounts or adjust balances depending on the mistake. The asfRequireDest and asfDisallowXRP flags are intended to protect users from accidentally sending funds in a way that is unclear about the reason the funds were sent.

For example, a destination tag is typically used to identify which hosted balance should be credited when a financial institution receives a payment. If the destination tag is omitted, it may be unclear which account should be credited, creating a need for refunds, among other problems. By using the asfRequireDest tag, you can ensure that every incoming payment has a destination tag, which makes it harder for others to send you an ambiguous payment by accident.

You can protect against unwanted incoming payments for non-XRP currencies by not creating trust lines in those currencies. Since XRP does not require trust, the asfDisallowXRP flag is used to discourage users from sending XRP to an account. However, this flag is not enforced in the XRP Ledger protocol because it could potentially cause accounts to become unusable if they run out of XRP. Instead, client applications should disallow or discourage XRP payments to accounts with the asfDisallowXRP flag enabled.

If you want to block all incoming payments, you can enable Deposit Authorization. This prevents any transaction from sending money to you, even XRP, unless your account is below the reserve requirement.

If the DisallowIncoming amendment is enabled, you also have the option to block all incoming Checks, NFTokenOffers, Payment Channels, and trust lines. It is generally harmless to be on the receiving end of these objects, but they can block you from deleting your account and it can be confusing to have objects you didn't expect mixed in with the list of objects you created. To block incoming objects, use one or more of these account flags:

• asfDisallowIncomingCheck - for Check objects
• asfDisallowIncomingNFTOffer - for NFTokenOffer objects
• asfDisallowIncomingPayChan - for PayChannel objects
• asfDisallowIncomingTrustline - for RippleState (trust line) objects

When a transaction would create one of these ledger entries, if the destination account has the corresponding flag enabled, the transaction fails with the result code tecNO_PERMISSION. Unlike Deposit Authorization, these settings do not prevent you from receiving payments in general. Also, enabling this setting doesn't stop you from creating these types of objects yourself (unless the destination of your transaction is also using the setting, of course).

TransferRate

The TransferRate field specifies a fee to charge whenever counterparties transfer the currency you issue.

In the HTTP and WebSocket APIs, the transfer fee is represented as an integer, the amount that must be sent for 1 billion units to arrive. For example, a 20% transfer fee is represented as the value 1200000000. The value cannot be less than 1000000000. (Less than that would indicate giving away money for sending transactions, which is exploitable.) You can specify 0 as a shortcut for 1000000000, meaning no fee.

See Transfer Fees for more information.

NFTokenMinter

To remove an authorized minter, set ClearFlag to 10 (asfAuthorizedNFTokenMinter) and omit the NFTokenMinter field.