From b80c58d54516b10088d83928b41a9f5131b2afa7 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 21 Nov 2019 13:23:53 -0800 Subject: [PATCH] Deletable Accounts: edits per peer review --- content/concepts/payment-system-basics/accounts/accounts.md | 6 ++++-- .../transaction-formats/transaction-results/tef-codes.md | 2 +- .../transaction-formats/transaction-types/accountdelete.md | 6 +++--- 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/content/concepts/payment-system-basics/accounts/accounts.md b/content/concepts/payment-system-basics/accounts/accounts.md index eabda90dbf..8257a7d0ce 100644 --- a/content/concepts/payment-system-basics/accounts/accounts.md +++ b/content/concepts/payment-system-basics/accounts/accounts.md @@ -70,10 +70,12 @@ To be deleted, an account must meet the following requirements: - `PayChannel` - `RippleState` - `Check` :not_enabled: -- The account must own less than 1000 objects in the ledger. +- The account must own fewer than 1000 objects in the ledger. - The [AccountDelete transaction][] must pay a special [transaction cost][] equal to at least the [owner reserve](reserves.html) for one item (currently 5 XRP). -Unlike Bitcoin and many other crypto-currencies, each new version of the XRP Ledger's public ledger chain contains the full state of the ledger, which increases in size with each new account. It is thus best to avoid creating new accounts unless entirely necessary. Institutions who send and receive value on behalf of many users can use [**Source Tags** and **Destination Tags**](become-an-xrp-ledger-gateway.html#source-and-destination-tags) to distinguish payments from and to their customers while only using one (or a handful) of accounts in the XRP Ledger. +Unlike Bitcoin and many other cryptocurrencies, each new version of the XRP Ledger's public ledger chain contains the full state of the ledger, which increases in size with each new account. For that reason, you should not create new XRP Ledger accounts unless necessary. You can recover some of an account's 20 XRP [reserve](reserves.html) by deleting the account, but you must still destroy at least 5 XRP to do so. + +Institutions who send and receive value on behalf of many users can use [**Source Tags** and **Destination Tags**](become-an-xrp-ledger-gateway.html#source-and-destination-tags) to distinguish payments from and to their customers while only using one (or a handful) of accounts in the XRP Ledger. diff --git a/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md b/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md index 81eb21f728..28c1580a11 100644 --- a/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md +++ b/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md @@ -23,7 +23,7 @@ These codes indicate that the transaction failed and was not included in a ledge | `tefNO_AUTH_REQUIRED` | The [TrustSet transaction][] tried to mark a trustline as authorized, but the `lsfRequireAuth` flag is not enabled for the corresponding account, so authorization is not necessary. | | `tefNOT_MULTI_SIGNING` | The transaction was [multi-signed](multi-signing.html), but the sending account has no SignerList defined. | | `tefPAST_SEQ` | The sequence number of the transaction is lower than the current sequence number of the account sending the transaction. | -| `tefTOO_BIG` | The transaction would affect too many objects in the ledger. For example, this was an [AccountDelete transaction][] but the account to be deleted owns over 1000 deletable objects in the ledger. The transaction could succeed on retry if some of those objects were deleted first. | +| `tefTOO_BIG` | The transaction would affect too many objects in the ledger. For example, this was an [AccountDelete transaction][] but the account to be deleted owns over 1000 objects in the ledger. | | `tefWRONG_PRIOR` | The transaction contained an `AccountTxnID` field (or the deprecated `PreviousTxnID` field), but the transaction specified there does not match the account's previous transaction. | diff --git a/content/references/rippled-api/transaction-formats/transaction-types/accountdelete.md b/content/references/rippled-api/transaction-formats/transaction-types/accountdelete.md index e523d514e4..cbe22963ea 100644 --- a/content/references/rippled-api/transaction-formats/transaction-types/accountdelete.md +++ b/content/references/rippled-api/transaction-formats/transaction-types/accountdelete.md @@ -4,7 +4,7 @@ _Requires the [DeletableAccounts amendment](known-amendments.html#deletableaccounts) :not_enabled:_ -An AccountDelete transaction deletes an [account from the XRP Ledger](accountroot.html) if possible, sending its XRP to a specified destination account. See [Deletion of Accounts](accounts.html#deletion-of-accounts) for the requirements to delete an account. +An AccountDelete transaction deletes an [account](accountroot.html) and any objects it owns in the XRP Ledger, if possible, sending the account's remaining XRP to a specified destination account. See [Deletion of Accounts](accounts.html#deletion-of-accounts) for the requirements to delete an account. ## Example {{currentpage.name}} JSON @@ -26,7 +26,7 @@ An AccountDelete transaction deletes an [account from the XRP Ledger](accountroo | Field | JSON Type | [Internal Type][] | Description | |:-----------------|:-----------------|:------------------|:-------------------| | `Destination` | String - [Address][] | Account | The address of an account to receive any leftover XRP after deleting the sending account. Must be a funded account in the ledger, and must not be the sending account. | -| `DestinationTag` | Number | UInt32 | _(Optional)_ Arbitrary [destination tag](source-and-destination-tags.html) that identifies the a hosted recipient or other information to the recipient of the deleted account's leftover XRP. | +| `DestinationTag` | Number | UInt32 | _(Optional)_ Arbitrary [destination tag](source-and-destination-tags.html) that identifies a hosted recipient or other information for the recipient of the deleted account's leftover XRP. | ## Error Cases @@ -42,7 +42,7 @@ In addition to errors that can occur for all transactions, {{currentpage.name}} | `tecNO_PERMISSION` | Occurs if the `Destination` account requires [deposit authorization](depositauth.html) and the sender is not preauthorized. | | `tecTOO_SOON` | Occurs if the sender's `Sequence` number is too high. The transaction's `Sequence` number plus 256 must be less than the current [Ledger Index][]. | | `tecHAS_OBLIGATIONS` | Occurs if the account to be deleted is connected to objects that cannot be deleted in the ledger. (This includes objects created by other accounts, such as [escrows](escrow.html).) | -| `tefTOO_BIG` | Occurs if the account to be deleted is connected to over 1000 deletable objects in the ledger. ***TODO: this will probably change to a ter*** | +| `tefTOO_BIG` | Occurs if the sending account is linked to more than 1000 objects in the ledger. The transaction could succeed on retry if some of those objects were deleted separately first. |