Skip to content

Commit a3233e7

Browse files
mvadarimDuo13
andauthored
Update docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md
Co-authored-by: Rome Reginelli <rome@ripple.com>
1 parent c3dd930 commit a3233e7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
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 (unless the authorized account deletes the trustline). (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

0 commit comments

Comments
 (0)