Use component amendment disclaimers for MPTs

This commit is contained in:
Maria Shodunke
2025-10-02 16:06:25 +01:00
parent 3b9a1834ba
commit 68433983d1
11 changed files with 15 additions and 15 deletions

View File

@@ -887,7 +887,7 @@ rippled json ledger_entry '{ "nft_page": "255DD86DDF59D778081A06D02701E9B2C9F4F0
### Get MPT Issuance Object
_(Requires the [MPToken amendment][] {% not-enabled /%})_
{% amendment-disclaimer name="MPTokensV1" /%}
Return an `MPTokenIssuance` object.
@@ -933,7 +933,7 @@ rippled json ledger_entry '{ "mpt_issuance": "000004C463C52827307480341125DA0577
### Get MPToken Object
_(Requires the [MPToken amendment][] {% not-enabled /%})_
{% amendment-disclaimer name="MPTokensV1" /%}
Return an `MPToken` object.

View File

@@ -12,11 +12,11 @@ label:
The XRP Ledger has three kinds of digital asset: XRP, [tokens](../../../concepts/tokens/index.md), and [Multi-purpose Tokens (MPTs)](../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md). All three types have high precision, although their formats are different.
_(Requires the [MPToken amendment][] {% not-enabled /%})_
{% amendment-disclaimer name="MPTokensV1" /%}
## Comparison
The following table summarizes some of the differences XRP, tokens, and MPTs in the XRP Ledger:
The following table summarizes some of the differences between XRP, tokens, and MPTs in the XRP Ledger:
| XRP | Tokens | MPTs |
|:---------------------------------------------------------|:------------------|:---------------------|

View File

@@ -73,8 +73,8 @@ Granular Permissions have numeric types of 65537 and up, corresponding to specif
| `65544` | `AccountTickSizeSet` | [AccountSet][] | Can set the [tick size of fungible tokens issued by the account](/docs/concepts/tokens/decentralized-exchange/ticksize). |
| `65545` | `PaymentMint` | [Payment][] | Can send payments that mint new fungible tokens or MPTs. |
| `65546` | `PaymentBurn` | [Payment][] | Can send payments that burn fungible tokens or MPTs. |
| `65547` | `MPTokenIssuanceLock` | [MPTokenIssuanceSet][] | Can lock the balances of a particular MPT issued by the account. _(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_ |
| `65548` | `MPTokenIssuanceUnlock` | [MPTokenIssuanceSet][] | Can unlock the balances of a particular MPT issued by the account. _(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_ |
| `65547` | `MPTokenIssuanceLock` | [MPTokenIssuanceSet][] | Can lock the balances of a particular MPT issued by the account. {% amendment-disclaimer name="MPTokensV1" /%} |
| `65548` | `MPTokenIssuanceUnlock` | [MPTokenIssuanceSet][] | Can unlock the balances of a particular MPT issued by the account. {% amendment-disclaimer name="MPTokensV1" /%} |
### Limitations to Granular Permissions

View File

@@ -9,7 +9,7 @@ status: not_enabled
An `MPToken` entry tracks [MPTs](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) held by an account that is not the token issuer. You can create or delete an empty `MPToken` entry by sending an [MPTokenAuthorize transaction][]. You can send and receive MPTs using several other transaction types including [Payment][] and [OfferCreate][] transactions.
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
## Example MPToken JSON

View File

@@ -9,7 +9,7 @@ status: not_enabled
An `MPTokenIssuance` entry represents a single [MPT](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) issuance and holds data associated with the issuance itself. You can create an `MPTokenIssuance` using an [MPTokenIssuanceCreate transaction][], and can delete it with an [MPTokenIssuanceDestroy transaction][].
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
## Example MPTokenIssuance JSON

View File

@@ -15,7 +15,7 @@ An MPTokenAuthorize transaction controls whether an account can hold a given [Mu
- An account revokes their willingness to hold an MPT, deleting the [MPToken entry][]. This can only be done if their balance of the given MPT is zero.
- For an MPT that uses allow-listing, an issuer grants or revokes permission for another account to hold the given MPT.
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%}

View File

@@ -15,7 +15,7 @@ If the transaction is successful, the newly created token is owned by the accoun
Whenever your query returns an `MPTokenIssuance` transaction response, there will always be an `mpt_issuance_id` field on the Transaction Metadata page.
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
## Example MPTokenIssuanceCreate JSON

View File

@@ -12,7 +12,7 @@ The `MPTokenIssuanceDestroy` transaction is used to remove an `MPTokenIssuance`
If this operation succeeds, the corresponding `MPTokenIssuance` is removed and the owners reserve requirement is reduced by one. This operation must fail if there are any holders of the MPT in question.
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
## Example MPTokenIssuanceDestroy JSON

View File

@@ -10,7 +10,7 @@ status: not_enabled
Use this transaction to update a mutable property for a Multi-purpose Token. The transaction flags determine which change(s) to apply.
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
{% amendment-disclaimer name="MPTokensV1" /%}
## Example