Skip to content

Commit b06f58f

Browse files
authored
Merge pull request #3090 from XRPLF/mvadari-patch-1
Update documentation to better explain authorized trustline deletion
2 parents e2887a8 + a3233e7 commit b06f58f

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The Authorized Trust Lines feature enables issuers to create tokens that can onl
1313

1414
To use the Authorized Trust Lines feature, enable the **Require Auth** flag on your issuing account. While the setting is enabled, other accounts can only hold tokens you issue if you have authorized those accounts' trust lines to your issuing account.
1515

16-
You can authorize a trust line by sending a [TrustSet transaction][] from your issuing address, configuring the trust line between your account and the account to authorize. After you have authorized a trust line, you can never revoke that authorization. (You can, however, [freeze](freezes.md) that trust line if you need to.)
16+
You can authorize a trust line by sending a [TrustSet transaction][] from your issuing address, configuring the trust line between your account and the account to authorize. After you have authorized a trust line, you can't revoke that authorization, but the authorization status is reset if the trust line is automatically deleted for being otherwise in its default state. (You can, however, [freeze](freezes.md) that trust line if you need to.)
1717

1818
The transaction to authorize a trust line must be signed by the issuing address, which unfortunately means an increased risk exposure for that address.
1919

docs/references/protocol/transactions/types/trustset.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,6 @@ Transactions of the TrustSet type support additional values in the [`Flags` fiel
6363

6464
If a transaction tries to enable No Ripple but cannot, it fails with the result code `tecNO_PERMISSION`. Before the [fix1578 amendment][] became enabled, such a transaction would result in `tesSUCCESS` (making any other changes it could) instead.
6565

66-
The Auth flag of a trust line does not determine whether the trust line counts towards its owner's XRP reserve requirement. However, an enabled Auth flag prevents the trust line from being in its default state. An authorized trust line can never be deleted. An issuer can pre-authorize a trust line with the `tfSetfAuth` flag only, even if the limit and balance of the trust line are 0.
66+
The Auth flag of a trust line does not determine whether the trust line counts towards its owner's XRP reserve requirement. An issuer can pre-authorize a trust line with the `tfSetfAuth` flag only, even if the limit and balance of the trust line are 0.
6767

6868
{% raw-partial file="/docs/_snippets/common-links.md" /%}

0 commit comments

Comments
 (0)