ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-05 04:15:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix amendment name: MPToken to MPTokensV1

Browse Source
This commit is contained in:
tequ
2025-02-19 10:54:02 +09:00
parent 8bc6ed6507
commit 9d9dbec483
16 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md
View File

@@ -810,7 +810,7 @@ rippled json ledger_entry '{ "nft_page": "255DD86DDF59D778081A06D02701E9B2C9F4F0
### MPT Issuanceオブジェクトを取得する
_([MPToken amendment][]が必要です。 {% not-enabled /%})_
_([MPTokensV1 amendment][]が必要です。 {% not-enabled /%})_
`MPTokenIssuance`オブジェクトを返します。
@@ -856,7 +856,7 @@ rippled json ledger_entry '{ "mpt_issuance": "000004C463C52827307480341125DA0577
### MPTokenオブジェクトを取得する
_([MPToken amendment][]が必要です。 {% not-enabled /%})_
_([MPTokensV1 amendment][]が必要です。 {% not-enabled /%})_
`MPToken`オブジェクトを返します。

2
@l10n/ja/docs/references/protocol/data-types/mptoken.md
View File

@@ -9,7 +9,7 @@ labels:
`MPTokenIssuanceID`.`MPToken`オブジェクトは、トークン発行者ではないアカウントが保有する複数のトークンを表します。MPTは通常の支払いやDEXトランザクションを通じて取得され、これらと同じタイプのトランザクションを使用してオプションで償還または交換することができます。MPTokenのオブジェクトキーは、スペースキー、保有者のアドレス、および`MPTokenIssuanceID`をハッシュ化することで生成されます。
_([MPTokenV1_1 amendment][]により追加されました。)_
_([MPTokensV1_1 amendment][]により追加されました。)_
## MPToken JSONの例

2
@l10n/ja/docs/references/protocol/data-types/mptokenissuance.md
View File

@@ -9,7 +9,7 @@ labels:
`MPTokenIssuance`オブジェクトは、単一のMPT Issuanceを表し、Issuance自体に関連するデータを保持します。このIssuanceは`MPTokenIssuanceCreate`トランザクションを使用して作成され、`MPTokenIssuanceDestroy`トランザクションによって破棄することができます。
_([MPTokenV1_1 amendment][]により追加されました。)_
_([MPTokensV1_1 amendment][]により追加されました。)_
## MPTokenIssuance JSONの例

4
docs/_snippets/common-links.md
View File

@@ -134,7 +134,7 @@
[LedgerHashesエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md
[LedgerHashesオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md
[Marker]: /docs/references/http-websocket-apis/api-conventions/markers-and-pagination.md
[MPToken amendment]: /resources/known-amendments.md#mptokensv1
[MPTokensV1 amendment]: /resources/known-amendments.md#mptokensv1
[MultiSign amendment]: /resources/known-amendments.md#multisign
[MultiSignReserve amendment]: /resources/known-amendments.md#multisignreserve
[NFTokenAcceptOffer transaction]: /docs/references/protocol/transactions/types/nftokenacceptoffer.md
@@ -220,7 +220,7 @@
[Payment]: /docs/references/protocol/transactions/types/payment.md
[Paymentトランザクション]: /docs/references/protocol/transactions/types/payment.md
[PriceOracle amendment]: /resources/known-amendments.md#priceoracle
[MPTokenV1_1 amendment]: /resources/known-amendments.md#priceoracle
[MPTokensV1_1 amendment]: /resources/known-amendments.md#priceoracle
[RFC-1751]: https://tools.ietf.org/html/rfc1751
[Reporting Mode]: /docs/concepts/networks-and-servers/rippled-server-modes.md#reporting-mode
[RequireFullyCanonicalSig amendment]: /resources/known-amendments.md#requirefullycanonicalsig

2
docs/concepts/tokens/fungible-tokens/multi-purpose-tokens.md
View File

@@ -8,7 +8,7 @@ status: not_enabled
---
# Multi-purpose Tokens
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
Multi-purpose tokens (MPTs) are a more compact and flexible type of fungible token.

2
docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders.md
View File

@@ -7,7 +7,7 @@ labels:
# mpt_holders
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
For a given `MPTokenIssuanceID` and ledger sequence, `mpt_holders` returns all holders of that MPT and their balance. This method likely returns very large data sets, so you should expect to implement paging via the `marker` field. This API is only available using Clio, not rippled.

4
docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md
View File

@@ -925,7 +925,7 @@ An example of a successful response:
### Get MPT Issuance Object
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
Return an `MPTokenIssuance` object.
@@ -967,7 +967,7 @@ rippled json ledger_entry '{ "mpt_issuance": "000004C463C52827307480341125DA0577
### Get MPToken Object
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
Return an `MPToken` object.

4
docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md
View File

@@ -5,11 +5,11 @@ labels:
---
# MPToken
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
The `MPToken` object represents a number of tokens held by an account that is not the token issuer. MPTs are acquired via ordinary payment or DEX transactions, and can optionally be redeemed or exchanged using these same types of transactions. The object key of the MPToken is derived from hashing the space key, the holder's address, and the `MPTokenIssuanceID`.
<!-- _(Added by the [MPTokenV1_1 amendment][].)_ -->
<!-- _(Added by the [MPTokensV1_1 amendment][].)_ -->
## Example MPToken JSON

4
docs/references/protocol/ledger-data/ledger-entry-types/mptokenissuance.md
View File

@@ -5,11 +5,11 @@ labels:
---
# MPTokenIssuance
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
The `MPTokenIssuance` object represents a single MPT issuance and holds data associated with the issuance itself. Token issuances are created using the `MPTokenIssuanceCreate` transaction and can be destroyed by the `MPTokenIssuanceDestroy` transaction.
<!-- _(Added by the [MPTokenV1_1 amendment][].)_ -->
<!-- _(Added by the [MPTokensV1_1 amendment][].)_ -->
## Example MPTokenIssuance JSON

2
docs/references/protocol/transactions/metadata.md
View File

@@ -256,7 +256,7 @@ Transactions (`tx` and `account_tx`) involving NFTs can contain the following fi
| `offer_id` | String | Shows the `OfferID`of a new `NFTokenOffer` in a response from a `NFTokenCreateOffer` transaction. |
## MPT Fields
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
### Synthetic mpt_issuance_id field
`MPTokenIssuanceID` is an identifier that allows you to specify an `MPTokenIssuance` in RPCs. The server adds a synthetically parsed `mpt_issuance_id` field to API responses to avoid the need for client-side parsing of the `MPTokenIssuanceID`.

2
docs/references/protocol/transactions/types/clawback.md
View File

@@ -35,7 +35,7 @@ Clawback is disabled by default. To use clawback, you must send an [AccountSet t
| Field | JSON Type | [Internal Type][] | Description |
|:-------------------|:----------|:------------------|:------------------|
| `Amount` | [Currency Amount][] | Amount |Indicates the amount being clawed back, as well as the counterparty from which the amount is being clawed back. The quantity to claw back, in the `value` sub-field, must not be zero. If this is more than the current balance, the transaction claws back the entire balance. The sub-field `issuer` within `Amount` represents the token holder's account ID, rather than the issuer's.|
| `Holder` | string | AccountID | (Optional) Specifies the holder's address from which to claw back. The holder must already own an `MPToken` object with a non-zero balance. _(Requires the [MPToken amendment][] {% not-enabled /%})_ |
| `Holder` | string | AccountID | (Optional) Specifies the holder's address from which to claw back. The holder must already own an `MPToken` object with a non-zero balance. _(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_ |
{% admonition type="info" name="Note" %}For an IOU (trust line) in the XRP Ledger, the party that created a token is called the _issuer_, but trust lines are bidirectional and, under some configurations, both sides can be seen as the issuer. In this transaction, the token issuer's address is in the `Account` field, and the token holder's address is in the `Amount` field's `issuer` sub-field.{% /admonition %}

4
docs/references/protocol/transactions/types/mptokenauthorize.md
View File

@@ -9,7 +9,7 @@ labels:
# MPTokenAuthorize
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "Source")
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
This transaction enables an account to hold an amount of a particular MPT issuance. When applied successfully, it creates a new `MPToken` object with an initial zero balance, owned by the holder account.
@@ -34,4 +34,4 @@ Transactions of the MPTokenAuthorize type support additional values in the Flags
|:-------------------|:-------------|:--------------|:------------------------------|
| `tfMPTUnauthorize` | `0x00000001` | 1 | If set, and transaction is submitted by a holder, it indicates that the holder no longer wants to hold the `MPToken`, which will be deleted as a result. If the holder's `MPToken` has a non-zero balance while trying to set this flag, the transaction fails. On the other hand, if set, and transaction is submitted by an issuer, it would mean that the issuer wants to unauthorize the holder (only applicable for allow-listing), which would unset the `lsfMPTAuthorized` flag on the `MPToken`. |
{% raw-partial file="/docs/_snippets/common-links.md" /%}
{% raw-partial file="/docs/_snippets/common-links.md" /%}

2
docs/references/protocol/transactions/types/mptokenissuancecreate.md
View File

@@ -9,7 +9,7 @@ labels:
# MPTokenIssuanceCreate
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "Source")
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
The `MPTokenIssuanceCreate` transaction creates an [MPTokenIssuance](../../ledger-data/ledger-entry-types/mptokenissuance.md) object and adds it to the relevant directory node of the creator account. This transaction is the only opportunity an issuer has to specify any token fields that are defined as immutable (for example, MPT Flags).

2
docs/references/protocol/transactions/types/mptokenissuancedestroy.md
View File

@@ -8,7 +8,7 @@ labels:
# MPTokenIssuanceDestroy
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "Source")
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
The `MPTokenIssuanceDestroy` transaction is used to remove an `MPTokenIssuance` object from the directory node in which it is being held, effectively removing the token from the ledger ("destroying" it).

2
docs/references/protocol/transactions/types/mptokenissuanceset.md
View File

@@ -8,7 +8,7 @@ labels:
# MPTokenIssuanceSet
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "Source")
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
Use this transaction to update a mutable property for a Multi-purpose Token.

2
docs/references/protocol/transactions/types/payment.md
View File

@@ -141,7 +141,7 @@ In the above example with a ¥95/$15 offer and a ¥5/$2 offer, the situation is
## MPT Payments
_(Requires the [MPToken amendment][] {% not-enabled /%})_
_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_
When you send a payment using MPTs, the _Amount_ field requires only the `mpt_issuance_id` and the `value`. The `MPTokenIssuanceID` is used to uniquely identify the MPT for the transaction.