Add 'asfAllowTrustLineLocking' flag to accountset.md #3307
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bronek
reviewed
Sep 17, 2025
| |:----------------------------------|:--------------|:--------------| | ||
| | `asfAccountTxnID` | 5 | Track the ID of this account's most recent transaction. Required for [`AccountTxnID`](../common-fields.md#accounttxnid) | | ||
| | `asfAllowTrustLineClawback` | 16 | Allow account to claw back tokens it has issued. _(Requires the Clawback amendment.)_ Can only be set if the account has an empty owner directory (no trust lines, offers, escrows, payment channels, checks, or signer lists). After you set this flag, it cannot be reverted. The account permanently gains the ability to claw back issued assets on trust lines. | | ||
| | `asfAllowTrustLineLocking` | 17 | Allow account to lock trust lines for **IOU** tokens it has issued. **IOU** Tokens: If the issuer's account does not have the `lsfAllowTrustLineLocking` flag set, the transaction fails with `tecNO_PERMISSION`. | |
There was a problem hiding this comment.
"the EscrowCreate transaction fails with" perhaps ? I guess this can be polished.
There was a problem hiding this comment.
Yeah, I think this one is missing some important context.
- "IOU" is specifically not a term we encourage since (a) tokens don't have to refer to amounts owed and (b) "IOU" has an unprofessional connotation
- "Locking" on trust lines (allowing amounts to be escrowed) is completely unrelated to "locking" on MPTs (equivalent to deep freezing on trust lines). It's annoying that the terminology is like that, but we're stuck with it at this point.
- This field is not currently available on mainnet because it requires the TokenEscrow amendment.
There was a problem hiding this comment.
"the
EscrowCreatetransaction fails with" perhaps ? I guess this can be polished.
something like that
| `asfAllowTrustLineLocking` | 17 | Allow account to lock trust lines for tokens it has issued. If the issuer's account does not have the `lsfAllowTrustLineLocking` flag set, the `EscrowCreate` transaction fails with `tecNO_PERMISSION`. (Requires the TokenEscrow amendment.) |
|
Noting this one for #3260 |
mDuo13
requested changes
Sep 18, 2025
| |:----------------------------------|:--------------|:--------------| | ||
| | `asfAccountTxnID` | 5 | Track the ID of this account's most recent transaction. Required for [`AccountTxnID`](../common-fields.md#accounttxnid) | | ||
| | `asfAllowTrustLineClawback` | 16 | Allow account to claw back tokens it has issued. _(Requires the Clawback amendment.)_ Can only be set if the account has an empty owner directory (no trust lines, offers, escrows, payment channels, checks, or signer lists). After you set this flag, it cannot be reverted. The account permanently gains the ability to claw back issued assets on trust lines. | | ||
| | `asfAllowTrustLineLocking` | 17 | Allow account to lock trust lines for **IOU** tokens it has issued. **IOU** Tokens: If the issuer's account does not have the `lsfAllowTrustLineLocking` flag set, the transaction fails with `tecNO_PERMISSION`. | |
There was a problem hiding this comment.
Yeah, I think this one is missing some important context.
- "IOU" is specifically not a term we encourage since (a) tokens don't have to refer to amounts owed and (b) "IOU" has an unprofessional connotation
- "Locking" on trust lines (allowing amounts to be escrowed) is completely unrelated to "locking" on MPTs (equivalent to deep freezing on trust lines). It's annoying that the terminology is like that, but we're stuck with it at this point.
- This field is not currently available on mainnet because it requires the TokenEscrow amendment.
|
Which specific wording issues should I address for this entry? And what other TokenEscrow docs need fixes - should we handle those in this PR or separately? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.