From 28de18d7d60244e93b48e1cfbb97468ae4c85f05 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Fri, 3 Oct 2025 16:17:49 -0700 Subject: [PATCH 1/9] Use amendment disclaimer & update tx ref intros --- .../accounts/decentralized-identifiers.md | 1 - .../ja/docs/_snippets/clawback-disclaimer.md | 1 - .../docs/concepts/accounts/multi-signing.md | 2 +- @l10n/ja/docs/concepts/accounts/tickets.md | 2 +- .../decentralized-identifiers.md | 6 +-- .../automated-market-makers.md | 2 +- .../fungible-tokens/clawing-back-tokens.md | 6 +-- .../tokens/fungible-tokens/deep-freeze.md | 2 +- .../fungible-tokens/stablecoins/settings.md | 3 +- @l10n/ja/docs/concepts/tokens/nfts/index.md | 2 +- @l10n/ja/docs/concepts/tokens/nfts/trading.md | 2 +- .../account-methods/account_nfts.md | 2 +- .../ledger-methods/ledger_entry.md | 4 +- .../path-and-order-book-methods/amm_info.md | 2 +- .../nft_buy_offers.md | 2 +- .../nft_sell_offers.md | 2 +- .../references/protocol/data-types/nftoken.md | 2 +- .../ledger-entry-types/accountroot.md | 18 ++++----- .../ledger-data/ledger-entry-types/amm.md | 2 +- .../ledger-data/ledger-entry-types/mptoken.md | 2 +- .../ledger-entry-types/mptokenissuance.md | 2 +- .../ledger-entry-types/negativeunl.md | 2 +- .../ledger-entry-types/nftokenoffer.md | 2 +- .../ledger-entry-types/nftokenpage.md | 2 +- .../pseudo-transaction-types/unlmodify.md | 2 +- .../transaction-results/tec-codes.md | 28 +++++++------- .../protocol/transactions/types/accountset.md | 10 ++--- .../protocol/transactions/types/ammbid.md | 2 +- .../transactions/types/ammclawback.md | 2 +- .../protocol/transactions/types/ammcreate.md | 2 +- .../protocol/transactions/types/ammdelete.md | 2 +- .../protocol/transactions/types/ammdeposit.md | 2 +- .../protocol/transactions/types/ammvote.md | 2 +- .../transactions/types/ammwithdraw.md | 2 +- .../transactions/types/checkcreate.md | 2 +- .../protocol/transactions/types/clawback.md | 6 +-- .../transactions/types/nftokenacceptoffer.md | 2 +- .../transactions/types/nftokenburn.md | 2 +- .../transactions/types/nftokencanceloffer.md | 2 +- .../transactions/types/nftokencreateoffer.md | 4 +- .../transactions/types/nftokenmint.md | 2 +- .../types/paymentchannelcreate.md | 2 +- .../protocol/transactions/types/trustset.md | 2 +- .../tokenization/stablecoin-issuer.md | 2 +- docs/_snippets/clawback-disclaimer.md | 1 - docs/concepts/accounts/deleting-accounts.md | 4 +- docs/concepts/accounts/depositauth.md | 24 +++++------- docs/concepts/accounts/multi-signing.md | 2 +- .../accounts/permission-delegation.md | 2 +- docs/concepts/accounts/tickets.md | 4 +- .../consensus-protocol/negative-unl.md | 8 ++-- .../decentralized-storage/credentials.md | 1 - .../decentralized-identifiers.md | 2 +- .../decentralized-storage/price-oracles.md | 18 +++++---- .../automated-market-makers.md | 2 +- .../permissioned-domains.md | 5 ++- .../tokens/fungible-tokens/deep-freeze.md | 2 +- .../fungible-tokens/stablecoins/settings.md | 3 +- docs/concepts/tokens/nfts/dynamic-nfts.md | 21 ++-------- docs/concepts/tokens/nfts/index.md | 2 +- docs/concepts/tokens/nfts/trading.md | 2 +- .../xrpl-sidechains/cross-chain-bridges.md | 2 +- docs/concepts/xrpl-sidechains/index.md | 2 +- .../xrpl-sidechains/witness-servers.md | 2 +- .../account-methods/account_channels.md | 2 +- .../account-methods/account_info.md | 8 ++-- .../account-methods/account_nfts.md | 2 +- .../clio-methods/mpt_holders.md | 2 +- .../ledger-methods/ledger_entry.md | 8 ++-- .../path-and-order-book-methods/amm_info.md | 2 +- .../book_offers.md | 2 +- .../get_aggregate_price.md | 2 +- .../nft_buy_offers.md | 2 +- .../nft_sell_offers.md | 2 +- .../path-and-order-book-methods/path_find.md | 2 +- .../ripple_path_find.md | 2 +- .../channel_authorize.md | 6 +-- .../payment-channel-methods/channel_verify.md | 4 +- .../subscription-methods/subscribe.md | 2 +- .../references/protocol/data-types/nftoken.md | 2 +- .../protocol/data-types/permission-values.md | 3 +- .../ledger-entry-types/accountroot.md | 26 ++++++------- .../ledger-entry-types/amendments.md | 4 +- .../ledger-data/ledger-entry-types/amm.md | 6 +-- .../ledger-data/ledger-entry-types/bridge.md | 2 +- .../ledger-data/ledger-entry-types/check.md | 2 +- .../ledger-entry-types/credential.md | 2 +- .../ledger-entry-types/delegate.md | 2 +- .../ledger-entry-types/depositpreauth.md | 3 +- .../ledger-data/ledger-entry-types/did.md | 2 +- .../ledger-entry-types/directorynode.md | 8 ++-- .../ledger-data/ledger-entry-types/escrow.md | 2 +- .../ledger-entry-types/feesettings.md | 8 ++-- .../ledger-data/ledger-entry-types/mptoken.md | 2 +- .../ledger-entry-types/negativeunl.md | 6 +-- .../ledger-entry-types/nftokenoffer.md | 2 +- .../ledger-entry-types/nftokenpage.md | 2 +- .../ledger-data/ledger-entry-types/offer.md | 6 +-- .../ledger-data/ledger-entry-types/oracle.md | 2 +- .../ledger-entry-types/paychannel.md | 2 +- .../ledger-entry-types/permissioneddomain.md | 2 +- .../ledger-entry-types/signerlist.md | 6 +-- .../ledger-data/ledger-entry-types/ticket.md | 2 +- .../ledger-entry-types/xchainownedclaimid.md | 2 +- .../xchainownedcreateaccountclaimid.md | 2 +- .../protocol/transactions/common-fields.md | 6 +-- .../protocol/transactions/metadata.md | 2 +- .../pseudo-transaction-types/unlmodify.md | 2 +- .../transaction-results/tec-codes.md | 38 +++++++++---------- .../transaction-results/tef-codes.md | 6 +-- .../transaction-results/tem-codes.md | 10 ++--- .../transaction-results/ter-codes.md | 2 +- .../transactions/types/accountdelete.md | 3 +- .../protocol/transactions/types/accountset.md | 19 +++++----- .../protocol/transactions/types/ammbid.md | 2 +- .../transactions/types/ammclawback.md | 6 +-- .../protocol/transactions/types/ammcreate.md | 4 +- .../protocol/transactions/types/ammdelete.md | 4 +- .../protocol/transactions/types/ammdeposit.md | 4 +- .../protocol/transactions/types/ammvote.md | 4 +- .../transactions/types/ammwithdraw.md | 4 +- .../protocol/transactions/types/batch.md | 4 +- .../transactions/types/checkcancel.md | 4 +- .../protocol/transactions/types/checkcash.md | 6 +-- .../transactions/types/checkcreate.md | 6 +-- .../protocol/transactions/types/clawback.md | 30 ++++++--------- .../transactions/types/credentialaccept.md | 8 ++-- .../transactions/types/credentialcreate.md | 8 ++-- .../transactions/types/credentialdelete.md | 8 ++-- .../transactions/types/delegateset.md | 2 +- .../transactions/types/depositpreauth.md | 8 ++-- .../protocol/transactions/types/diddelete.md | 7 ++-- .../protocol/transactions/types/didset.md | 7 ++-- .../transactions/types/escrowcancel.md | 7 ++-- .../transactions/types/escrowcreate.md | 7 ++-- .../transactions/types/escrowfinish.md | 7 ++-- .../transactions/types/ledgerstatefix.md | 8 ++-- .../transactions/types/mptokenauthorize.md | 6 +-- .../types/mptokenissuancecreate.md | 12 ++---- .../types/mptokenissuancedestroy.md | 8 +--- .../transactions/types/mptokenissuanceset.md | 5 +-- .../transactions/types/nftokenacceptoffer.md | 4 +- .../transactions/types/nftokenburn.md | 8 ++-- .../transactions/types/nftokencanceloffer.md | 4 +- .../transactions/types/nftokencreateoffer.md | 8 ++-- .../transactions/types/nftokenmint.md | 6 ++- .../transactions/types/nftokenmodify.md | 6 +-- .../transactions/types/offercancel.md | 4 +- .../transactions/types/offercreate.md | 9 ++--- .../transactions/types/oracledelete.md | 9 ++--- .../protocol/transactions/types/oracleset.md | 9 ++--- .../protocol/transactions/types/payment.md | 12 +++--- .../transactions/types/paymentchannelclaim.md | 4 +- .../types/paymentchannelcreate.md | 4 +- .../transactions/types/paymentchannelfund.md | 2 +- .../types/permissioneddomaindelete.md | 7 ++-- .../types/permissioneddomainset.md | 7 ++-- .../transactions/types/setregularkey.md | 5 +-- .../transactions/types/signerlistset.md | 7 ++-- .../transactions/types/ticketcreate.md | 5 +-- .../protocol/transactions/types/trustset.md | 4 +- .../types/xchainaccountcreatecommit.md | 8 ++-- .../xchainaddaccountcreateattestation.md | 5 +-- .../types/xchainaddclaimattestation.md | 5 +-- .../transactions/types/xchainclaim.md | 7 ++-- .../transactions/types/xchaincommit.md | 8 ++-- .../transactions/types/xchaincreatebridge.md | 7 ++-- .../transactions/types/xchaincreateclaimid.md | 7 ++-- .../transactions/types/xchainmodifybridge.md | 7 ++-- .../create-an-automated-market-maker.md | 2 +- .../set-up-iou-iou-bridge.md | 2 +- .../set-up-xrp-xrp-bridge.md | 2 +- .../submit-cross-chain-transaction.md | 2 +- .../tokenization/stablecoin-issuer.md | 4 +- 174 files changed, 404 insertions(+), 478 deletions(-) delete mode 100644 @l10n/ja/docs/_snippets/clawback-disclaimer.md delete mode 100644 docs/_snippets/clawback-disclaimer.md diff --git a/@l10n/es-ES/docs/concepts/accounts/decentralized-identifiers.md b/@l10n/es-ES/docs/concepts/accounts/decentralized-identifiers.md index 9bbed0905bf..1b78f341d40 100644 --- a/@l10n/es-ES/docs/concepts/accounts/decentralized-identifiers.md +++ b/@l10n/es-ES/docs/concepts/accounts/decentralized-identifiers.md @@ -3,7 +3,6 @@ html: decentralized-identifiers.html parent: accounts.html seo: description: Los identificadores decentralizados permiten identidades digitales decentralizadas verificables. -status: not_enabled labels: - DID --- diff --git a/@l10n/ja/docs/_snippets/clawback-disclaimer.md b/@l10n/ja/docs/_snippets/clawback-disclaimer.md deleted file mode 100644 index bc3139d57b4..00000000000 --- a/@l10n/ja/docs/_snippets/clawback-disclaimer.md +++ /dev/null @@ -1 +0,0 @@ -_[Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039d-clawback)が必要です。_ diff --git a/@l10n/ja/docs/concepts/accounts/multi-signing.md b/@l10n/ja/docs/concepts/accounts/multi-signing.md index a6a0672c49a..a5273fc1823 100644 --- a/@l10n/ja/docs/concepts/accounts/multi-signing.md +++ b/@l10n/ja/docs/concepts/accounts/multi-signing.md @@ -38,7 +38,7 @@ _([ExpandedSignerList amendment][]により更新されました。)_ また、リスト内の各署名者のエントリに最大256ビットの任意のデータを追加することができます。このデータはネットワークで必要とされたり使用されたりすることはありませんが、スマートコントラクトや他のアプリケーションが署名者に関する他のデータを特定したり確認したりするために使用することができます。 -_([ExpandedSignerList amendment][]により追加されました。)_ +{% amendment-disclaimer name="ExpandedSignerList" /%} ### Signer WeightとQuorumの使用例 diff --git a/@l10n/ja/docs/concepts/accounts/tickets.md b/@l10n/ja/docs/concepts/accounts/tickets.md index 5598738263b..5fb39a1cdef 100644 --- a/@l10n/ja/docs/concepts/accounts/tickets.md +++ b/@l10n/ja/docs/concepts/accounts/tickets.md @@ -9,7 +9,7 @@ labels: --- # Ticket -_([TicketBatch amendment][]により追加されました。)_ +{% amendment-disclaimer name="TicketBatch" /%} XRP Ledgerのチケットは、取引をすぐに送信せずに、その取引のために[シーケンス番号][]を確保する方法です。チケットを使うことで、通常の順序以外で取引を送信することができます。この使用例としては、必要な署名を集めるのに時間がかかるような[マルチサイン取引](multi-signing.md)などが挙げられます。 diff --git a/@l10n/ja/docs/concepts/decentralized-storage/decentralized-identifiers.md b/@l10n/ja/docs/concepts/decentralized-storage/decentralized-identifiers.md index 3a871e21a48..937a136b348 100644 --- a/@l10n/ja/docs/concepts/decentralized-storage/decentralized-identifiers.md +++ b/@l10n/ja/docs/concepts/decentralized-storage/decentralized-identifiers.md @@ -1,16 +1,11 @@ --- -html: decentralized-identifiers.html -parent: accounts.html seo: description: 分散型IDは、検証可能な分散型デジタルIDを可能にします。 -status: not_enabled labels: - DID --- # 分散型ID -_([DID Amendment][] {% not-enabled /%} が必要です。)_ - 分散型ID(DID)は、検証可能なデジタルIDを可能にするWorld Wide Web Consortium(W3C)によって定義された新しいタイプの識別子です。DIDはDID所有者の完全な管理下にあり、中央管理レジストリ、IDプロバイダ、認証局から独立しています。 DIDの主な基本原則は以下の通りです。 @@ -25,6 +20,7 @@ DIDの主な基本原則は以下の通りです。 {% admonition type="info" name="注記" %}XRP LedgerにおけるDIDの実装は、[DID v1.0仕様](https://www.w3.org/TR/did-core/)の仕様に準拠しています。{% /admonition %} +{% amendment-disclaimer name="DID" /%} ## 仕組み diff --git a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md index 862581e11eb..87eb9e84cac 100644 --- a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md +++ b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md @@ -8,7 +8,7 @@ labels: --- # 自動マーケットメーカー(AMM)とは? -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} 自動マーケットメーカー(AMM)は、XRP Ledgerの分散型取引所において流動性を提供します。個々のAMMは2つの資産のプールを保有します。ユーザは数式で定められた取引レートによりその2つの資産間でスワップが可能です。 diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/clawing-back-tokens.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/clawing-back-tokens.md index fdbf9edec22..36535a0f532 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/clawing-back-tokens.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/clawing-back-tokens.md @@ -1,6 +1,4 @@ --- -html: clawing-back-tokens.html -parent: trust-lines-and-issuing.html seo: description: 発行者は、トークンを発行する前にClawback機能を有効にすると、規制遵守の目的でトークンを取り戻すことができます。 labels: @@ -8,8 +6,6 @@ labels: --- # トークンの回収 -{% partial file="/@l10n/ja/docs/_snippets/clawback-disclaimer.md" /%} - 規制上の目的から、トークンがアカウントに送信された後にトークンを回収する機能を必要とする発行者が存在します。例えば、トークンが違法行為で制裁を受けたアカウントに送られたことが発覚した場合、発行者はその資金を「回収」することができます。 発行者は、発行アカウントで**Allow Clawback**フラグを有効にすることで、トークンを回収する権限を得ることができます。発行者がすでにトークンを発行している場合、このフラグを有効にすることはできません。 @@ -21,6 +17,8 @@ Clawback機能はデフォルトで無効になっています。使用するに `lsfNoFreeze`が設定されているときに`lsfAllowTrustLineClawback`を設定しようとすると、トランザクションは`tecNO_PERMISSION`を返します。 逆に、`lsfAllowTrustLineClawback`が設定されている時に`lsfNoFreeze`を設定しようとすると、トランザクションは`tecNO_PERMISSION`を返します。 +{% amendment-disclaimer name="Clawback" /%} + ## Clawbackトランザクションの例 ```json diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/deep-freeze.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/deep-freeze.md index f2e5ff2f487..128c5675ab5 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/deep-freeze.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/deep-freeze.md @@ -14,7 +14,7 @@ labels: ディープフリーズは、支払い、オファー、分散型取引所（DEX）、自動マーケットメイカー（AMM）に関わるトラストラインに影響を与えます。発行者は、ディープフリーズ状態の保有者に対して、送金および受取をブロックできます。 -_([DeepFreeze amendment][]により追加されました。)_ +{% amendment-disclaimer name="DeepFreeze" /%} ## ディープフリーズの仕組み diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md index 0697f28f884..3405dd50f71 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md @@ -82,12 +82,11 @@ KYC(Know Your Customer)やAML(Anti-Money Laundering)などのコンプライア ### Clawbackフラグ -_([Clawback amendment](/resources/known-amendments.md#clawback) が必要です。)_ - Clawbackにより、特定の状況下でトラストラインからステーブルコインを回収(クローバック)することができます。これにより、アカウントへのアクセス不能や悪意のある活動などの課題に対応する能力が追加されます。 [Clawback](../../../../references/protocol/transactions/types/clawback.md)をご覧ください。 +{% amendment-disclaimer name="Clawback" /%} ### 固定供給量 diff --git a/@l10n/ja/docs/concepts/tokens/nfts/index.md b/@l10n/ja/docs/concepts/tokens/nfts/index.md index 8d8f6d644f6..25876f970e9 100644 --- a/@l10n/ja/docs/concepts/tokens/nfts/index.md +++ b/@l10n/ja/docs/concepts/tokens/nfts/index.md @@ -11,7 +11,7 @@ labels: XRP Ledgerは、非代替性トークン(NFT)をネイティブにサポートしています。 非代替性トークンは、芸術作品やゲーム内アイテムなど、ユニークな物理的、非物理的、あるいは純粋なデジタル商品の所有権を証明する役割を果たします。 -_([NonFungibleTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} このようなデジタル資産を表現するには、XRP LedgerのNon-Fungible Tokens機能（スタンダードドラフト番号で[XLS-20](https://github.com/XRPLF/XRPL-Standards/discussions/46)と呼ばれることもあります）を使用します。 diff --git a/@l10n/ja/docs/concepts/tokens/nfts/trading.md b/@l10n/ja/docs/concepts/tokens/nfts/trading.md index 1e798717c61..612f84f42a8 100644 --- a/@l10n/ja/docs/concepts/tokens/nfts/trading.md +++ b/@l10n/ja/docs/concepts/tokens/nfts/trading.md @@ -12,7 +12,7 @@ labels: XRP Ledger上のアカウント間で`NFToken`オブジェクトを転送することができます。`NFToken`の売買をオファーしたり、他のアカウントから自分が保有するNFTokenへの売買オファーを受け入れることができます。`NFToken`を無料(価格が0)で売却することで、`NFToken`を配布することもできます。すべてのオファーは[NFTokenCreateOfferトランザクション][]を使って作成されます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## 売却オファー diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md index 28e3bf5d280..36a0318b4d1 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md @@ -11,7 +11,7 @@ labels: `account_nfts`メソッドは、指定したアカウントの`NFToken`オブジェクトの一覧を返します。 -_([NonFungibleTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## リクエストのフォーマット リクエストのフォーマットの例 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index c3515fb5830..b91fd1f7111 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -164,7 +164,7 @@ rippled json ledger_entry '{ "account_root": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 ### AMMエントリを取得する -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} レジャーからAutomated Market-Maker(AMM)エントリを取得します。これは[amm_infoメソッド][]と似ていますが、`ledger_entry`は保存されているレジャーエントリのみを返します。 @@ -787,7 +787,7 @@ rippled json ledger_entry '{ "deposit_preauth": { "owner": "rf1BiGeXwwQoi8Z2ueFY ### Ticketエントリを取得する -将来の使用のために確保された[シーケンス番号][]を表す[Ticketエントリ](../../../protocol/ledger-data/ledger-entry-types/ticket.md)を取得します。文字列(TicketのエントリID)またはオブジェクトを指定します。 _([TicketBatch amendment][]により追加されました。)_ +将来の使用のために確保された[シーケンス番号][]を表す[Ticketエントリ](../../../protocol/ledger-data/ledger-entry-types/ticket.md)を取得します。文字列(TicketのエントリID)またはオブジェクトを指定します。 {% amendment-disclaimer name="TicketBatch" /%} | フィールド | 型 | 説明 | |:--------------------|:-----------------------|:----------------------| diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md index 95f891f5090..dde560028f6 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md @@ -14,7 +14,7 @@ labels: {% code-page-name /%}メソッドは、自動マーケットメーカー（AMM）インスタンスに関する情報を取得します。 -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} ### リクエストのフォーマット diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md index 583589fb2a2..1e6c08539a2 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md @@ -11,7 +11,7 @@ labels: `nft_buy_offers`メソッドは、与えられた[NFToken][]オブジェクトに対する購入オファーのリストを返します。 -_([NonFungibleTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## リクエストのフォーマット リクエストのフォーマットの例： diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md index 9382f4abf0a..f7747f85815 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md @@ -11,7 +11,7 @@ labels: `nft_sell_offers`メソッドは、与えられた[NFToken][]オブジェクトに対する売却オファーのリストを返します。 -_([NonFungibleTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## リクエストのフォーマット リクエストのフォーマットの例： diff --git a/@l10n/ja/docs/references/protocol/data-types/nftoken.md b/@l10n/ja/docs/references/protocol/data-types/nftoken.md index c966c0e0edc..86b2617e7e0 100644 --- a/@l10n/ja/docs/references/protocol/data-types/nftoken.md +++ b/@l10n/ja/docs/references/protocol/data-types/nftoken.md @@ -10,7 +10,7 @@ labels: `NFToken`オブジェクトは、1つの非代替性トークン(NFT)を表します。単体では保存されず、他の`NFToken`オブジェクトと共に[NFTokenPageオブジェクト][]に格納されます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index 92f5ac3a7f8..f0d37784f0f 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -1,6 +1,4 @@ --- -html: accountroot.html -parent: ledger-entry-types.html seo: description: あるアカウントの設定、XRP残高、その他のメタデータを表します。 labels: @@ -41,7 +39,7 @@ labels: |:------------------------------|:---------|:------------------|:------|:------| | `Account` | 文字列 | AccountID | はい | この[アカウント](../../../../concepts/accounts/index.md)を識別するための（クラシック）アドレスです。 | | `AccountTxnID` | 文字列 | UInt256 | いいえ | このアカウントから直近に送信されたトランザクションの識別ハッシュ。このフィールドは、[`AccountTxnID`トランザクションフィールド](../../transactions/common-fields.md#accounttxnid)を使うために有効になっていなければなりません。これを有効にするには、[`asfAccountTxnID`フラグを有効にしたAccountSetトランザクション](../../transactions/types/accountset.md#accountsetのフラグ)を送信してください。 | -| `AMMID` | 文字列 | UInt256 | いいえ | _([AMM amendment][]により追加されました。)_ 対応するAMMレジャーエントリのレジャーエントリID。アカウント作成時に設定します。AMM以外のアカウントでは常に省略されます。 | +| `AMMID` | 文字列 | UInt256 | いいえ | {% amendment-disclaimer name="AMM" /%} 対応するAMMレジャーエントリのレジャーエントリID。アカウント作成時に設定します。AMM以外のアカウントでは常に省略されます。 | | `Balance` | 文字列 | Amount | いいえ | アカウントの現在の[XRPのdrop数][]で、文字列で表現されます。 | | `BurnedNFTokens` | 数値 | UInt32 | いいえ | このアカウントで発行された [非代替性トークン](../../../../concepts/tokens/nfts/index.md) のうち、バーンしたトークンの総数を表します。この数値は常に `MintedNFTokens` と同じかそれ以下となります。 | | `Domain` | 文字列 | VariableLength | いいえ | このアカウントに関連付けられたドメイン。JSONでは、ドメインのASCII表現を16進数で表現します。[256バイトを超える長さは使用できません](https://github.com/xrplf/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | @@ -56,7 +54,7 @@ labels: | `PreviousTxnLgrSeq` | 数値 | UInt32 | はい | 最後にこのオブジェクトを変更したトランザクションが記録された[レジャーインデックス][]。 | | `RegularKey` | 文字列 | AccountID | いいえ | このアカウントのトランザクションに署名するときにマスターキーの代わりに使用できる[キーペア](../../../../concepts/accounts/cryptographic-keys.md)のアドレス。この値を変更するには[SetRegularKeyトランザクション][]を使用してください。 | | `Sequence` | 数値 | UInt32 | はい | このアカウントの有効な次のトランザクションの[シーケンス番号](../../data-types/basic-data-types.md#アカウントシーケンス) を表します。 | -| `TicketCount` | 数値 | UInt32 | いいえ | このアカウントが台帳に保有する[チケット](../../../../concepts/accounts/tickets.md)の数です。これは、アカウントが一度に250 チケットという上限以内に留まることを保証するために自動的に更新されます。このフィールドは、チケットの数がゼロの場合は省略されます。 _([TicketBatch amendment][]により追加されました)_ | +| `TicketCount` | 数値 | UInt32 | いいえ | このアカウントが台帳に保有する[チケット](../../../../concepts/accounts/tickets.md)の数です。これは、アカウントが一度に250 チケットという上限以内に留まることを保証するために自動的に更新されます。このフィールドは、チケットの数がゼロの場合は省略されます。 {% amendment-disclaimer name="TicketBatch" /%} | | `TickSize` | 数値 | UInt8 | いいえ | このアドレスが発行した通貨が関わるオファーの為替レートに使用する有効桁数。有効な値は`3`以上`15`以下です。_（[TickSize Amendment][]により追加されました。）_ | | `TransferRate` | 数値 | UInt32 | いいえ | このアカウントが発行した通貨を他のユーザが相互に送金する際に、これらのユーザに請求する[送金手数料](../../../../concepts/tokens/fungible-tokens/transfer-fees.md)。 | | `WalletLocator` | 文字列 | UInt256 | いいえ | ユーザが設定できる任意の256bit値。 | @@ -64,7 +62,7 @@ labels: ## AMMの特殊なAccountRootエントリ -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} [自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)は、AMMの詳細の一部を追跡するための[AMMレジャーエントリ](amm.md)に加えて、LPトークンを発行しAMMプール内の資産を保持するためにAccountRootレジャーエントリを使用します。AMMに関連するAccountRootのアドレスは、AMMが作成される前にユーザがそのアドレスを特定し資金を提供できないように、ランダム化されています。AMMのAccountRootは、通常のアカウントとは異なり、以下のような設定で作成されます。 @@ -89,14 +87,14 @@ AccountRootオブジェクトは`Flags`フィールドに以下のフラグを | フラグ名 | 16進数値 | 10進数値 | 対応する[AccountSetのフラグ](../../transactions/types/accountset.md#accountsetのフラグ) | 説明 | |-----------------------------------|--------------|----------|-------------------------------------|-------------------------------| -| `lsfAllowTrustLineClawback` | `0x80000000` | 2147483648 | `asfAllowTrustLineClawback` | このアカウントの[Clawback](../../../../concepts/tokens/fungible-tokens/clawing-back-tokens.md)を有効にします。 _([Clawback Amendment][]が必要です。)_ | +| `lsfAllowTrustLineClawback` | `0x80000000` | 2147483648 | `asfAllowTrustLineClawback` | このアカウントの[Clawback](../../../../concepts/tokens/fungible-tokens/clawing-back-tokens.md)を有効にします。 {% amendment-disclaimer name="Clawback" /%} | | `lsfDefaultRipple` | `0x00800000` | 8388608 | `asfDefaultRipple` | このアドレスのトラストラインでデフォルトで[rippling](../../../../concepts/tokens/fungible-tokens/rippling.md)を有効にします。発行アドレスに必要です。他のアドレスでの使用は推奨されません。 | | `lsfDepositAuth` | `0x01000000` | 16777216 | `asfDepositAuth` | このアカウントは、アカウントが送信するトランザクションと、[事前承認された](../../../../concepts/accounts/depositauth.md#事前承認)アカウントからの資金だけを受領します。（[DepositAuth](../../../../concepts/accounts/depositauth.md)が有効になっています。） | | `lsfDisableMaster` | `0x00100000` | 1048576 | `asfDisableMaster` | このアカウントのトランザクションの署名にマスターキーを使用することを禁止します。 | -| `lsfDisallowIncomingCheck` | `0x08000000` | 134217728 | `asfDisallowIncomingCheck` | このアカウントを宛先とするチェックの作成をブロックします。 _([DisallowIncoming Amendment][]により追加されました。)_ | -| `lsfDisallowIncomingNFTokenOffer` | `0x04000000` | 67108864 | `asfDisallowIncomingNFTokenOffer` | このアカウントを宛先とするNFTokenオファーの作成をブロックします。 _([DisallowIncoming Amendment][]により追加されました。)_ | -| `lsfDisallowIncomingPayChan` | `0x10000000` | 268435456 | `asfDisallowIncomingPayChan` | このアカウントを宛先とするペイメントチャネルの作成をブロックします。 _([DisallowIncoming Amendment][]により追加されました。)_ | -| `lsfDisallowIncomingTrustline` | `0x20000000` | 536870912 | `asfDisallowIncomingTrustline` | このアカウントに対するトラストラインの作成をブロックします。 _([DisallowIncoming Amendment][]により追加されました。)_ | +| `lsfDisallowIncomingCheck` | `0x08000000` | 134217728 | `asfDisallowIncomingCheck` | このアカウントを宛先とするチェックの作成をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingNFTokenOffer` | `0x04000000` | 67108864 | `asfDisallowIncomingNFTokenOffer` | このアカウントを宛先とするNFTokenオファーの作成をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingPayChan` | `0x10000000` | 268435456 | `asfDisallowIncomingPayChan` | このアカウントを宛先とするペイメントチャネルの作成をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingTrustline` | `0x20000000` | 536870912 | `asfDisallowIncomingTrustline` | このアカウントに対するトラストラインの作成をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | | `lsfDisallowXRP` | `0x00080000` | 524288 | `asfDisallowXRP` | クライアントアプリケーションはこのアカウントにXRPを送金しないでください。`rippled`により強制されるものではありません。 | | `lsfGlobalFreeze` | `0x00400000` | 4194304 | `asfGlobalFreeze` | このアドレスが発行するすべての資産がフリーズされます。 | | `lsfNoFreeze` | `0x00200000` | 2097152 | `asfNoFreeze` | このアドレスは、このアドレスに接続しているトラストラインをフリーズできません。一度有効にすると、無効にできません。 | diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md index 5bfea976650..a5f5a4d276f 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md @@ -9,7 +9,7 @@ labels: # AMM [[ソース]](https://github.com/xrplf/rippled/blob/c1e4bfb08bcc9f187d794a71d653003a6148dc68/src/ripple/protocol/impl/LedgerFormats.cpp#L265-L275 "Source") -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} `AMM`レジャーエントリは、単一の[自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)インスタンスを表します。これは常に[特殊なAccountRootエントリ](accountroot.md#ammの特殊なaccountrootエントリ)と対になっています。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md index 7883d76fd3a..faca502fe53 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md @@ -10,7 +10,7 @@ labels: `MPTokenIssuanceID`.`MPToken`オブジェクトは、トークン発行者ではないアカウントが保有する複数のトークンを表します。MPTは通常の支払いやDEXトランザクションを通じて取得され、これらと同じタイプのトランザクションを使用してオプションで償還または交換することができます。MPTokenのオブジェクトキーは、スペースキー、保有者のアドレス、および`MPTokenIssuanceID`をハッシュ化することで生成されます。 -_([MPTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="MPTokensV1_1" /%} ## MPToken JSONの例 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptokenissuance.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptokenissuance.md index 1d00d6601a2..fb94e4b9019 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptokenissuance.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/mptokenissuance.md @@ -10,7 +10,7 @@ labels: `MPTokenIssuance`オブジェクトは、単一のMPT Issuanceを表し、Issuance自体に関連するデータを保持します。このIssuanceは`MPTokenIssuanceCreate`トランザクションを使用して作成され、`MPTokenIssuanceDestroy`トランザクションによって破棄することができます。 -_([MPTokensV1_1 amendment][]により追加されました。)_ +{% amendment-disclaimer name="MPTokensV1_1" /%} ## MPTokenIssuance JSONの例 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md index 225672dd82d..80131a8e3a9 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md @@ -8,7 +8,7 @@ labels: --- # NegativeUNL -_([NegativeUNL amendment][]により追加されました。)_ +{% amendment-disclaimer name="NegativeUNL" /%} `NegativeUNL`オブジェクトタイプは、[ネガティブUNL](../../../../concepts/consensus-protocol/negative-unl.md)の現在の状態、つまり現在オフラインであると考えられる信頼できるバリデーションのリストを含んでいます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md index 6dad37f62f3..725b12e38ce 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md @@ -10,7 +10,7 @@ labels: `lsfTransferable`フラグが設定されているトークンは、オファーを使って参加者間で転送することができます。`NFTokenOffer`オブジェクトは`NFToken`オブジェクトの購入、売却、または譲渡のオファーを表します。`NFToken`の所有者は`NFTokenCreateOffer`を使用して売買を行うことができます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md index 38e8f382f35..c3b18443446 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md @@ -10,7 +10,7 @@ labels: `NFTokenPage`オブジェクトは、同じアカウントが所有する[NFT](../../../../concepts/tokens/nfts/index.md)のコレクションを表します。一つのアカウントは複数の`NFTokenPage`エントリを持つことができ、それらは双方向リストを形成します。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %}のJSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md index 56213536daa..2167875bc0d 100644 --- a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md +++ b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md @@ -8,7 +8,7 @@ labels: --- # UNLModify -_([NegativeUNL amendment][]により追加されました)_ +{% amendment-disclaimer name="NegativeUNL" /%} `UNLModify`[疑似トランザクション](pseudo-transaction-types.md)は[Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md)の変更を示し、信頼できるバリデータがオフラインになったかオンラインに戻ってきたことを示します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md index bd9db8c5d60..809622c0318 100644 --- a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -17,14 +17,14 @@ labels: | コード | 値 | 説明 | |:---------------------------------- |:----|:----------------------------------------| -| `tecAMM_ACCOUNT` | 168 | 自動マーケットメーカー（AMM）アカウントではこの操作が許可されていないため、トランザクションが失敗しました。 _([AMM amendment][]により追加されました。)_ | -| `tecAMM_UNFUNDED` | 162 | 送信者が指定された資産を十分に保有していないため[AMMCreateトランザクション][]が失敗しました。 _([AMM amendment][]により追加されました。)_ | -| `tecAMM_BALANCE` | 163 | AMMまたはユーザーが指定された資産の十分な量を保有していないため[AMMDeposit][]または[AMMWithdraw][]トランザクションが失敗しました。(例えば、AMMが保有するよりも多くを引き出そうとしている場合） _([AMM amendment][]により追加されました。)_ | -| `tecAMM_EMPTY` | 166 | AMMのプールに資産がないためAMM関連のトランザクションが失敗しました。この状態では、AMMを削除するか、新しい入金でAMMに資金を供給することしかできません。 _([AMM amendment][]により追加されました。)_ | -| `tecAMM_FAILED` | 164 | AMM関連のトランザクションは失敗しました。[AMMDeposit][]または[AMMWithdraw][]の場合、これは送信者が指定された資産を十分に持っていないか、利用可能な金額では不可能な実効価格がトランザクションで要求されたことが原因である可能性があります。[AMMBid][]の場合、これは当該アカウントが落札に必要な金額を十分に持っていないか、指定された最高入札価格よりも高い金額が必要であることが原因である可能性があります。[AMMVote] の場合、このAMMのLPトークンをより多く保有している他のアカウントからの投票がすでに多すぎるのが原因である可能性があります。 _([AMM amendment][]により追加されました。)_ | -| `tecAMM_INVALID_TOKENS` | 165 | LPトークンの不足や丸め処理の問題により、AMM関連のトランザクションが失敗しました。例えば、返却されるLPトークンの額がゼロに切り捨てられる場合、「非常に少量の資産を預け入れる」という行為が失敗する可能性があります。 _([AMM amendment][]により追加されました。)_ | -| `tecAMM_NOT_EMPTY` | 167 | トランザクションは、資産プールが空のAMMで動作するように設計されていましたが、指定されたAMMは資産を保有しています。 _([AMM amendment][]により追加されました。)_ | -| `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | トランザクションは、同じアカウントが購入または売却するために作成された[非代替可能トークン(NFT)](../../../../concepts/tokens/nfts/index.md)のオファーを受け入れようとしました。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `tecAMM_ACCOUNT` | 168 | 自動マーケットメーカー（AMM）アカウントではこの操作が許可されていないため、トランザクションが失敗しました。 {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_UNFUNDED` | 162 | 送信者が指定された資産を十分に保有していないため[AMMCreateトランザクション][]が失敗しました。 {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_BALANCE` | 163 | AMMまたはユーザーが指定された資産の十分な量を保有していないため[AMMDeposit][]または[AMMWithdraw][]トランザクションが失敗しました。(例えば、AMMが保有するよりも多くを引き出そうとしている場合） {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_EMPTY` | 166 | AMMのプールに資産がないためAMM関連のトランザクションが失敗しました。この状態では、AMMを削除するか、新しい入金でAMMに資金を供給することしかできません。 {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_FAILED` | 164 | AMM関連のトランザクションは失敗しました。[AMMDeposit][]または[AMMWithdraw][]の場合、これは送信者が指定された資産を十分に持っていないか、利用可能な金額では不可能な実効価格がトランザクションで要求されたことが原因である可能性があります。[AMMBid][]の場合、これは当該アカウントが落札に必要な金額を十分に持っていないか、指定された最高入札価格よりも高い金額が必要であることが原因である可能性があります。[AMMVote] の場合、このAMMのLPトークンをより多く保有している他のアカウントからの投票がすでに多すぎるのが原因である可能性があります。 {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_INVALID_TOKENS` | 165 | LPトークンの不足や丸め処理の問題により、AMM関連のトランザクションが失敗しました。例えば、返却されるLPトークンの額がゼロに切り捨てられる場合、「非常に少量の資産を預け入れる」という行為が失敗する可能性があります。 {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_NOT_EMPTY` | 167 | トランザクションは、資産プールが空のAMMで動作するように設計されていましたが、指定されたAMMは資産を保有しています。 {% amendment-disclaimer name="AMM" /%} | +| `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | トランザクションは、同じアカウントが購入または売却するために作成された[非代替可能トークン(NFT)](../../../../concepts/tokens/nfts/index.md)のオファーを受け入れようとしました。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecCLAIM` | 100 | 不明なエラー。トランザクションコストは消却されました。 | | `tecCRYPTOCONDITION_ERROR` | 146 | この[EscrowCreate][]トランザクションまたは[EscrowFinish][]トランザクションに指定されるCrypto-conditionの形式が誤っているか、または一致しませんでした。 | | `tecDIR_FULL` | 121 | トランザクションがアカウントの所有者ディレクトリにオブジェクト（トラストライン、Check、Escrow、Payment Channelなど）を追加しようと試みましたが、このアカウントはレジャーにこれ以上のオブジェクトを所有できません。 | @@ -38,16 +38,16 @@ labels: | `tecINSUF_RESERVE_LINE` | 122 | 送信側アカウントに、新しいトラストラインを作成するのに十分なXRPがないため、トランザクションが失敗しました。（[準備金](../../../../concepts/accounts/reserves.md)をご覧ください）このエラーは、取引相手から同一通貨の送信側アカウントへのトラストラインがデフォルト以外の状態である場合に発生します。（その他のケースについては`tecNO_LINE_INSUF_RESERVE`をご覧ください。） | | `tecINSUF_RESERVE_OFFER` | 123 | 送信側アカウントに、新しいオファーを作成するのに十分なXRPがないため、トランザクションが失敗しました。（[準備金](../../../../concepts/accounts/reserves.md)をご覧ください。) | | `tecINSUFF_FEE` | 136 | 指定された[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)を支払うのに十分なXRPが送金元アカウントにないため、トランザクションが失敗しました。（この場合、送金元のXRPが指定されたトランザクションコストよりも低い場合でも、トランザクション処理によってすべて消却されます。）この結果は、このトランザクションがコンセンサスセットに含まれるのに十分なネットワークに配布された*後に*アカウントの残高が減少した場合にのみ発生します。そうでない場合、トランザクションは配布される前に[`terINSUF_FEE_B`](ter-codes.md)で失敗します。 | -| `tecINSUFFICIENT_FUNDS` | 158 | 関連するアカウントのうちの1つが必要な資産を十分に保有していません。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | -| `tecINSUFFICIENT_PAYMENT` | 161 | 指定された金額は、トランザクションに関わるすべての料金を支払うには十分ではありません。例えば、非代替性トークンを取引する場合、購入金額はブローカー手数料と販売金額の両方を支払うには不十分である可能性があります。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `tecINSUFFICIENT_FUNDS` | 158 | 関連するアカウントのうちの1つが必要な資産を十分に保有していません。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | +| `tecINSUFFICIENT_PAYMENT` | 161 | 指定された金額は、トランザクションに関わるすべての料金を支払うには十分ではありません。例えば、非代替性トークンを取引する場合、購入金額はブローカー手数料と販売金額の両方を支払うには不十分である可能性があります。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecINSUFFICIENT_RESERVE` | 141 | トランザクションによって[必要準備金](../../../../concepts/accounts/reserves.md)が増加し、送信側アカウントの残高を超える可能性があります。[SignerListSet][]、[PaymentChannelCreate][]、[PaymentChannelFund][]、および[EscrowCreate][]からこのエラーコードが返されることがあります。詳細は、[SignerListと準備金](../../ledger-data/ledger-entry-types/signerlist.md#signerlistと準備金)をご覧ください。 | | `tecINTERNAL` | 144 | 不明な内部エラーが発生し、トランザクションコストは適用されました。通常はこのエラーは返されません。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tecINVARIANT_FAILED` | 147 | このトランザクションを実行しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]により追加されました。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tecKILLED` | 150 | [OfferCreateトランザクション][]がtfFillOrKillフラグを指定しましたが、トランザクションを確定できなかったため、このトランザクションは取り消されました。_（[fix1578 Amendment][]により追加されました。）_ | -| `tecMAX_SEQUENCE_REACHED` | 153 | シーケンス番号フィールドはすでに最大値に達しています。これには`MintedNFTokens`フィールドも含まれます。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `tecMAX_SEQUENCE_REACHED` | 153 | シーケンス番号フィールドはすでに最大値に達しています。これには`MintedNFTokens`フィールドも含まれます。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNEED_MASTER_KEY` | 142 | このトランザクションはマスターキーを必要とする変更（[マスターキーの無効化または残高フリーズ能力の放棄](../types/accountset.md#accountsetのフラグ)など）を試みました。| -| `tecNFTOKEN_BUY_SELL_MISMATCH` | 155 | [NFTokenAcceptOfferトランザクション][]は、非代替性トークンの購入と売却に関する対応しないオファーをマッチングさせようとしました。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | -| `tecNFTOKEN_OFFER_TYPE_MISMATCH` | 156 | トランザクションで指定されたオファーのうち、1つまたは複数について、オファーの種類が適切ではありませんでした。（例えば、`NFTokenSellOffer`フィールドに購入オファーが指定されていました。） _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `tecNFTOKEN_BUY_SELL_MISMATCH` | 155 | [NFTokenAcceptOfferトランザクション][]は、非代替性トークンの購入と売却に関する対応しないオファーをマッチングさせようとしました。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | +| `tecNFTOKEN_OFFER_TYPE_MISMATCH` | 156 | トランザクションで指定されたオファーのうち、1つまたは複数について、オファーの種類が適切ではありませんでした。（例えば、`NFTokenSellOffer`フィールドに購入オファーが指定されていました。） {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNO_ALTERNATIVE_KEY` | 130 | トランザクションが唯一の[トランザクション承認](../../../../concepts/transactions/index.md#トランザクションの承認)メソッドを削除しようとしました。これは、レギュラーキーを削除する[SetRegularKeyトランザクション][]、SignerListを削除する[SignerListSetトランザクション][]、またはマスターキーを無効にする[AccountSetトランザクション][]である可能性があります。（`rippled` 0.30.0より前のバージョンでは、このトランザクションは`tecMASTER_DISABLED`と呼ばれていました。） | | `tecNO_AUTH` | 134 | トランザクションはトラストラインの残高を、`lsfRequireAuth`フラグが有効になっているアカウントに追加する必要がありましたが、そのトラストラインが承認されていなかったため、失敗しました。トラストラインが存在しない場合は、代わりに`tecNO_LINE`が発生します。 | | `tecNO_DST` | 124 | トランザクションの受信側のアカウントが存在しません。これには、PaymentトランザクションタイプやTrustSetトランザクションタイプがあります。（XRPを十分に受信した場合に作成される可能性があります。） | @@ -59,7 +59,7 @@ labels: | `tecNO_LINE_REDUNDANT` | 127 | トランザクションはトラストラインをデフォルト状態に設定しようと試みましたが、トラストラインが存在していなかったため、失敗しました。 | | `tecNO_PERMISSION` | 139 | 送信者にはこの操作を実行する権限がありません。たとえば[EscrowFinishトランザクション][]が`FinishAfter`時刻に達する前に保留中の支払をリリースしようとしたか、送信者が所有していないChannelで誰かが[PaymentChannelFund][]を使用しようとしたか、または[Payment][]が「DepositAuth」フラグが有効になっているアカウントに資金の送金を試みました。 | | `tecNO_REGULAR_KEY` | 131 | [AccountSetトランザクション][]がマスターキーを無効にしようとしましたが、アカウントにはマスターキー以外で[トランザクションを承認する](../../../../concepts/transactions/index.md#トランザクションの承認)方法がありません。[マルチシグ](../../../../concepts/accounts/multi-signing.md)が有効な場合、このコードは廃止予定であり、代わりに`tecNO_ALTERNATIVE_KEY`が使用されます。 | -| `tecNO_SUITABLE_NFTOKEN_PAGE` | 154 | トランザクションは、非代替性トークンの発行または取得を試みましたが、`NFToken`を受け取るアカウントには、それを保持できるディレクトリページがありません。この状況はレアケースです。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `tecNO_SUITABLE_NFTOKEN_PAGE` | 154 | トランザクションは、非代替性トークンの発行または取得を試みましたが、`NFToken`を受け取るアカウントには、それを保持できるディレクトリページがありません。この状況はレアケースです。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNO_TARGET` | 138 | トランザクションが参照するEscrowレジャーオブジェクトまたはPayChannelレジャーオブジェクトが存在していません。これらのオブジェクトは、これまでに存在したことがないか、すでに削除されています。（たとえば、別の[EscrowFinishトランザクション][]で保留中の支払がすでに実行されている場合などです。）あるいは、支払先アカウントで`asfDisallowXRP`が設定されているため、このアカウントは[PaymentChannelCreate][]トランザクションまたは[EscrowCreate][]トランザクションの宛先に指定できません。 | | `tecOVERSIZE` | 145 | サーバがこのトランザクションの適用時に大量のメタデータを作成したため、このトランザクションを処理できませんでした。 | | `tecOWNERS` | 132 | トランザクションでは、トランザクションを送信するアカウントの「所有者カウント」はゼロ以外である必要があります。このためトランザクションを正常に完了できません。たとえば、トラストラインや使用可能なオファーがあるアカウントでは、[`lsfRequireAuth`](../types/accountset.md#accountsetのフラグ)フラグを有効にできません。 | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md index 88bc75e9bb9..e8899554f16 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md @@ -74,14 +74,14 @@ AccountSetトランザクションは、[XRP Ledgerのアカウント](../../led |:----------------------------------|:------|:--------------| | `asfAccountTxnID` | 5 | このアカウントの直近のトランザクションのIDを追跡します。[AccountTxnID](../common-fields.md#accounttxnid)については必須です。 | | `asfAllowTrustLineClawback` | 16 | アカウントの発行したトークンを回収する機能を有効にします。 _（[Clawback Amendment][]により追加されました）。_　所有者ディレクトリが存在する場合はClawback機能を有効にできません。つまり、トラストラインやオファー、エスクロー、ペイメントチャネル、チェック、または署名者リストを設定する前に行う必要があります。このフラグは、有効にした後は無効にできません。| -| `asfAuthorizedNFTokenMinter` | 10 | このアカウントの代わりに、別のアカウントが非代替性トークン（NFToken）をミントすることを許可するために使用します。認可されたアカウントを[AccountRoot](../../ledger-data/ledger-entry-types/accountroot.md)オブジェクトの`NFTokenMinter`フィールドで指定します。認可されたアカウントを削除するには、このフラグを有効にして`NFTokenMinter`フィールドを省略します。 _([NonFungibleTokensV1_1 amendment][]により追加されました。)_ | +| `asfAuthorizedNFTokenMinter` | 10 | このアカウントの代わりに、別のアカウントが非代替性トークン（NFToken）をミントすることを許可するために使用します。認可されたアカウントを[AccountRoot](../../ledger-data/ledger-entry-types/accountroot.md)オブジェクトの`NFTokenMinter`フィールドで指定します。認可されたアカウントを削除するには、このフラグを有効にして`NFTokenMinter`フィールドを省略します。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `asfDefaultRipple` | 8 | このアカウントのトラストラインでの[リップリング](../../../../concepts/tokens/fungible-tokens/rippling.md)をデフォルトで有効にします。 | | `asfDepositAuth` | 9 | このアカウントに対して[Deposit Authorization](../../../../concepts/accounts/depositauth.md)を有効にします _（[DepositAuth Amendment][]により追加されました）。_ | | `asfDisableMaster` | 4 | マスターキーペアの使用を禁止します。[レギュラーキー](../../../../concepts/accounts/cryptographic-keys.md)や[署名者リスト](../../../../concepts/accounts/multi-signing.md)など、トランザクションに署名するための別の手段がアカウントで設定されている場合のみ有効にできます。 | -| `asfDisallowIncomingCheck` | 13 | チェックの着信をブロックします。_([DisallowIncoming amendment][] が必要です。)_ | -| `asfDisallowIncomingNFTokenOffer` | 12 | NFTokenOffersの着信をブロックします。_([DisallowIncoming amendment][] が必要です)_。 | -| `asfDisallowIncomingPayChan` | 14 | ペイメントチャネルの着信をブロックします。_([DisallowIncoming amendment][] が必要です)_。 | -| `asfDisallowIncomingTrustline` | 15 | トラストラインの着信をブロックします。_([DisallowIncoming amendment][] が必要です)_。 | +| `asfDisallowIncomingCheck` | 13 | チェックの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingNFTokenOffer` | 12 | NFTokenOffersの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingPayChan` | 14 | ペイメントチャネルの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingTrustline` | 15 | トラストラインの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | | `asfDisallowXRP` | 3 | XRPがこのアカウントに送信されないようにします（勧告的なもので、XRP Ledgerのプロトコルでは強制されません）。 | | `asfGlobalFreeze` | 7 | このアカウントによって発行されたすべての資産を[フリーズ](../../../../concepts/tokens/fungible-tokens/freezes.md)します。 | | `asfNoFreeze` | 6 | [個々のトラストラインのフリーズまたはGlobal Freezeの無効化](../../../../concepts/tokens/fungible-tokens/freezes.md)の機能を永続的に放棄します。このフラグは、有効にした後は無効にできません。 | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md b/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md index a289deddecc..d2ec7c87a61 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md @@ -9,7 +9,7 @@ labels: # AMMBid [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMBid.cpp "Source") -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} [自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)のオークションスロットに入札することができます。落札されると、競り落とされるか24時間が経過するまで、割引料金でAMMと取引することができます。24時間が経過する前に競り落とされた場合、残り時間に応じて落札価格の一部が払い戻されます。AMMの取引手数料が0の場合、入札は可能ですが、入札スロットは取引手数料が変更されるまでメリットをもたらしません。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammclawback.md b/@l10n/ja/docs/references/protocol/transactions/types/ammclawback.md index c7ab1d26b63..0c0a1d7d66d 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammclawback.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammclawback.md @@ -14,7 +14,7 @@ labels: Clawbackはデフォルトで無効です。Clawbackを使用するには、[AccountSetトランザクション][]を送信して、**Allow Trust Line Clawback**設定を有効にする必要があります。すでにトークンが発行済みである発行者はClawbackを有効にできません。**Allow Trust Line Clawback**を有効にするには、トラストライン、オファー、エスクロー、ペイメントチャネル、チェック、署名者リストを設定する前に、所有者ディレクトリを完全に空にする必要があります。Clawbackを有効にした後は、元に戻すことはできません。つまり発行者アカウントは、トラストラインの発行済みトークンを回収できる権利を永続的に得ます。 -_([AMMClawback amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMMClawback" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md index 588bc35e6ae..30f66737b10 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md @@ -9,7 +9,7 @@ labels: # AMMCreate [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} 資産（[代替可能トークン](../../../../concepts/tokens/index.md)または[XRP](../../../../introduction/what-is-xrp.md)）のペアを取引するための新しい[自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)インスタンスを作成します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md b/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md index b8e63529e20..0d440014e46 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md @@ -9,7 +9,7 @@ labels: # AMMDelete [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} 自動で削除しきれなかった空の[自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)インスタンスを削除します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md b/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md index db70878999d..1222a027199 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md @@ -19,7 +19,7 @@ labels: - AMMのプールにある資産の一方または両方を保有する権限がない {% /admonition %} -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md b/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md index 9dc8c01e664..b5ef1127695 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md @@ -11,7 +11,7 @@ labels: [自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)インスタンスの取引手数料を投票します。最大8つのアカウントが、保有するAMMのLPトークンの量に比例して投票することができます。投票を行うごとには、投票の加重平均に基づいてAMMの取引手数料が再計算されます。 -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md b/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md index 85295e08096..9ceeeae7c80 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md @@ -11,7 +11,7 @@ labels: AMMの流動性プロバイダトークン（LPトークン）を返却することで、[自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)インスタンスから資産を引き出します。 -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md index 1aaf32ec5f7..e14c1850eed 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md @@ -42,7 +42,7 @@ _（[Checks Amendment][]が必要です）_ ## エラーケース -- `Destination`アカウントがCheckの着信をブロックしている場合、トランザクションは結果コード`tecNO_PERMISSION`で失敗します。 _([DisallowIncoming amendment][] が必要です。)_ +- `Destination`アカウントがCheckの着信をブロックしている場合、トランザクションは結果コード`tecNO_PERMISSION`で失敗します。 {% amendment-disclaimer name="DisallowIncoming" /%} - `Destination`がトランザクションの送信者である場合、トランザクションは結果コード`temREDUNDANT`で失敗します。 - `Destination`[アカウント](../../../../concepts/accounts/index.md)がレジャーに存在していない場合、トランザクションは結果コード`tecNO_DST`で失敗します。 - `Destination`アカウントでRequireDestフラグが有効であるが、トランザクションに`DestinationTag`フィールドが含まれていない場合、トランザクションは結果コード`tecDST_TAG_NEEDED`で失敗します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/clawback.md b/@l10n/ja/docs/references/protocol/transactions/types/clawback.md index eb0155734d8..98c29947b78 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/clawback.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/clawback.md @@ -1,6 +1,4 @@ --- -html: clawback.html -parent: transaction-types.html seo: description: 発行したトークンを取り戻します。 labels: @@ -10,12 +8,12 @@ labels: [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Clawback.cpp "ソース") -{% partial file="/@l10n/ja/docs/_snippets/clawback-disclaimer.md" /%} - あなたのアカウントが発行したトークンを回収します。 Clawback機能はデフォルトで無効になっています。使用するには、[AccountSetトランザクション][]を送信して**Allow Trust Line Clawback**設定を有効にする必要があります。既存のトークンを持つ発行者はClawback機能を有効にできません。つまり、トラストライン、オファー、エスクロー、ペイメントチャネル、チェック、または署名者リストを設定する前に行う必要があります。Clawback機能を有効にした後、元に戻すことはできません：アカウントは永久にトラストラインで発行された資産を回収する権限を得ます。 +{% amendment-disclaimer name="Clawback" /%} + ## {% $frontmatter.seo.title %} JSONの例 ```json diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md index 319e01eec9b..0813a7624a5 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -12,7 +12,7 @@ labels: * 1つのオファーを受け入れます。これは _ダイレクト_ モードと呼ばれます。 * 2つの異なるオファー(`NFToken`の購入オファーと同じ`NFToken`に対するの売却オファー)をアトミックに受け入れます。これは _ブローカー_ モードと呼ばれます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## NFTokenAcceptOffer JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenburn.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenburn.md index 43481d0367c..00c2ffa16d7 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenburn.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenburn.md @@ -14,7 +14,7 @@ NFTokenBurnトランザクションは、`NFToken`オブジェクトを保持し この操作に成功すると、対応する`NFToken`が削除されます。この操作によって`NFToken`を保持している`NFTokenPage`が空になるか、統合されて`NFTokenPage`が削除されると、所有者準備金が1つ減ります。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md index dde11565ec2..a5a3e423926 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -11,7 +11,7 @@ labels: `NFTokenCancelOffer`トランザクションは、`NFTokenCreateOffer`を使用して作成した既存のトークンへのオファーをキャンセルするために使用できます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md index f131a071eb3..c5ec6561af8 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -13,7 +13,7 @@ labels: 成功した場合、トランザクションは[NFTokenOfferオブジェクト][]を作成します。各オファーは、オファーを提示したアカウントの[所有者準備金](../../../../concepts/accounts/reserves.md)に関連づけて1つのオブジェクトとしてカウントされます。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 @@ -66,7 +66,7 @@ NFTokenCreateOfferタイプのトランザクションは、以下のように[` | `tecNO_ENTRY` | `NFToken`フィールドで指定したアカウントは所有していません。 | | `tecNO_ISSUER` | `Amount`フィールドで指定した発行者が存在しません。 | | `tecNO_LINE` | `Amount`フィールドはトークンですが、`NFToken`の発行者はそのトークンのトラストラインを持っておらず、`NFToken`は[`lsfTrustLine`フラグ](../../data-types/nftoken.md#nftoken-フラグ)が有効ではありません。 | -| `tecNO_PERMISSION` | `Destination`アカウントが着信する NFTokenOffer をブロックします。 _([DisallowIncoming amendment][] が必要です。)_ +| `tecNO_PERMISSION` | `Destination`アカウントが着信する NFTokenOffer をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | `tecUNFUNDED_OFFER` | 購入オファーの場合、送信者は`Amount`フィールドで指定された通貨を利用可能です。もし`Amount`がXRPである場合、これは準備不足によるものかもしれません。もし`Amount`がトークンである場合、これは[フリーズ](../../../../concepts/tokens/fungible-tokens/freezes.md)されている可能性があります。 | | `tefNFTOKEN_IS_NOT_TRANSFERABLE` | `NFToken`は[`lsfTransferable`フラグ](../../data-types/nftoken.md#nftoken-flags)が無効になっており、このトランザクションでは`NFToken`を発行者に転送したり発行者から転送したりすることはできません。 | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md index ae42980ba62..59769b201e5 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md @@ -9,7 +9,7 @@ labels: `NFTokenMint`トランザクションは非代替性トークンを作成し、`NFTokenMinter`に紐付く[NFTokenPageオブジェクト][]に[NFToken][]オブジェクトとして追加します。このトランザクションは`NFTokenMinter`にとって、不変と定義されているトークンフィールド(例えば`Flags`)を設定することができる唯一の方法です。 -_([NonFungibleTokensV1_1 amendment][]により追加されました)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md index baf0ab2cd08..e48c39ae5e6 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -41,6 +41,6 @@ _[PayChan Amendment][]により追加されました。_ | `CancelAfter` | 数値 | UInt32 | _（省略可）_ このChannelの有効期限（[Rippleエポック以降の経過秒数][]）。この時刻の経過後にトランザクションがこのChannelを変更しようとすると、このChannelは閉鎖し、Channelは変更されません。この値は変更できません。Channelはこの時刻よりも早い時点で閉鎖できますが、この時刻の経過後にもオープンしたままにすることはできません。 | | `DestinationTag` | 数値 | UInt32 | _（省略可）_ このPayment Channelの宛先（宛先アドレスのホスティングされている受取人など） を詳しく指定するための任意のタグ。 | -`Destination` アカウントがペイメントチャネルの着信をブロックしている場合、トランザクションは結果コード`tecNO_PERMISSION` 失敗します。_([DisallowIncoming amendment][] が必要です)_。 +`Destination` アカウントがペイメントチャネルの着信をブロックしている場合、トランザクションは結果コード`tecNO_PERMISSION` 失敗します。{% amendment-disclaimer name="DisallowIncoming" /%} {% raw-partial file="/@l10n/ja/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/trustset.md b/@l10n/ja/docs/references/protocol/transactions/types/trustset.md index 64fb4833ed5..930c52b0a10 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/trustset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/trustset.md @@ -44,7 +44,7 @@ labels: | `QualityIn` | 数値 | UInt32 | _（省略可）_ このトラストラインの受入額を、1,000,000,000単位当たりのこの数値の割合で評価。値`0`は、残高を額面価格で扱うことを示す省略表現です。 | | `QualityOut` | 数値 | UInt32 | _（省略可）_ このトラストラインの払出額を、1,000,000,000単位当たりのこの数値の割合で評価。値`0`は、残高を額面価格で扱うことを示す省略表現です。 | -`LimitAmount.issuer`で指定されたアカウントがトラストラインの着信をブロックしている場合、結果コード`tecNO_PERMISSION`でトランザクションが失敗します。 _([DisallowIncoming amendment][] が必要です)_ +`LimitAmount.issuer`で指定されたアカウントがトラストラインの着信をブロックしている場合、結果コード`tecNO_PERMISSION`でトランザクションが失敗します。 {% amendment-disclaimer name="DisallowIncoming" /%} ## TrustSetのフラグ diff --git a/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md b/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md index 08d33811fc0..52d2067df0d 100644 --- a/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md +++ b/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md @@ -206,7 +206,7 @@ Clawbackは、ステーブルコインの配布を開始する前に選択でき ### AMMへのリスト -_([AMM amendment][]により追加されました。)_ +{% amendment-disclaimer name="AMM" /%} 自動マーケットメイカー(AMM)は、XRP Ledgerの分散型取引所で流動性を提供するスマートコントラクトです。各AMMは2つの資産のプールを保有し、計算式で設定された取引レートでユーザがそれらの間でスワップを行うことを可能にします。 diff --git a/docs/_snippets/clawback-disclaimer.md b/docs/_snippets/clawback-disclaimer.md deleted file mode 100644 index 0037aac4295..00000000000 --- a/docs/_snippets/clawback-disclaimer.md +++ /dev/null @@ -1 +0,0 @@ -_Requires the [Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039d-clawback)._ diff --git a/docs/concepts/accounts/deleting-accounts.md b/docs/concepts/accounts/deleting-accounts.md index 3415119f5e2..1df77e562c3 100644 --- a/docs/concepts/accounts/deleting-accounts.md +++ b/docs/concepts/accounts/deleting-accounts.md @@ -1,6 +1,4 @@ --- -html: deleting-accounts.html -parent: accounts.html seo: description: About deleting an XRP Ledger account. labels: @@ -31,7 +29,7 @@ The following [ledger entry types](../../references/protocol/ledger-data/ledger- - `PayChannel` - `RippleState` (trust line) - `Check` -- `PermissionedDomain` _(Requires the [PermissionedDomains amendment][] {% not-enabled /%})_ +- `PermissionedDomain` {% amendment-disclaimer name="PermissionedDomains" /%} Any other types of ledger entries that an account owns are automatically deleted along with the account. diff --git a/docs/concepts/accounts/depositauth.md b/docs/concepts/accounts/depositauth.md index f6ce9e3f855..f73b37174c1 100644 --- a/docs/concepts/accounts/depositauth.md +++ b/docs/concepts/accounts/depositauth.md @@ -1,6 +1,4 @@ --- -html: depositauth.html -parent: accounts.html seo: description: The DepositAuth setting lets an account block incoming payments by default. labels: @@ -9,8 +7,6 @@ labels: --- # Deposit Authorization -_(Added by the [DepositAuth amendment][].)_ - Deposit Authorization is an optional [account](index.md) setting in the XRP Ledger. If enabled, Deposit Authorization blocks all transfers from strangers, including transfers of XRP and [tokens](../tokens/index.md). An account with Deposit Authorization can only receive value in two ways: - From accounts it has [preauthorized](#preauthorization). @@ -18,6 +14,8 @@ Deposit Authorization is an optional [account](index.md) setting in the XRP Ledg By default, new accounts have DepositAuth disabled and can receive XRP from anyone. +{% amendment-disclaimer name="DepositAuth" /%} + ## Background Financial services regulations and licenses may require that a business or entity must know the sender of all transactions it receives. This presents a challenge on a decentralized system like the XRP Ledger where participants are identified by pseudonyms which can be freely generated and the default behavior is for any address to be able to pay any other. @@ -26,7 +24,7 @@ The Deposit Authorization flag introduces an option for those using the XRP Ledg When you have Deposit Authorization enabled, you can receive money from [Checks](/resources/known-amendments.md#checks), [Escrow](../payment-types/escrow.md), and [Payment Channels](/resources/known-amendments.md#paychan). In these transactions' "two-step" model, first the source sends a transaction to authorize sending funds, then the destination sends a transaction to authorize receiving those funds. -To receive money from [Payment transactions][] when you have Deposit Authorization enabled, you must [preauthorize](#preauthorization) the senders of those Payments. _(Added by the [DepositPreauth amendment][].)_ +To receive money from [Payment transactions][] when you have Deposit Authorization enabled, you must [preauthorize](#preauthorization) the senders of those Payments. ## Recommended Usage @@ -41,15 +39,15 @@ To get the full effect of Deposit Authorization, Ripple recommends also doing th An account with Deposit Authorization enabled: - **Cannot** be the destination of [Payment transactions][], with **the following exceptions**: - - If the destination has [preauthorized](#preauthorization) the sender of the Payment. _(Added by the [DepositPreauth amendment][])_ + - If the destination has [preauthorized](#preauthorization) the sender of the Payment. - If the account's XRP balance is equal to or below the minimum account [reserve requirement](reserves.md), it can be the destination of an XRP Payment whose `Amount` is equal or less than the minimum account reserve (currently {% $env.PUBLIC_BASE_RESERVE %}). This is to prevent an account from becoming "stuck" by being unable to send transactions but also unable to receive XRP. The account's owner reserve does not matter for this case. - Can receive XRP from [PaymentChannelClaim transactions][] **only in the following cases**: - The sender of the PaymentChannelClaim transaction is the destination of the payment channel. - - The destination of the PaymentChannelClaim transaction has [preauthorized](#preauthorization) the sender of the PaymentChannelClaim. _(Added by the [DepositPreauth amendment][])_ + - The destination of the PaymentChannelClaim transaction has [preauthorized](#preauthorization) the sender of the PaymentChannelClaim. - Can receive XRP from [EscrowFinish transactions][] **only in the following cases**: - The sender of the EscrowFinish transaction is the destination of the escrow. - - The destination of the EscrowFinish transaction has [preauthorized](#preauthorization) the sender of the EscrowFinish. _(Added by the [DepositPreauth amendment][])_ -- **Can** receive XRP or tokens by sending a [CheckCash][] transaction. _(Added by the [Checks amendment][].)_ + - The destination of the EscrowFinish transaction has [preauthorized](#preauthorization) the sender of the EscrowFinish. +- **Can** receive XRP or tokens by sending a [CheckCash][] transaction. - **Can** receive XRP or tokens by sending [OfferCreate transactions][]. - If the account sends an OfferCreate transaction that is not fully executed immediately, it **can** receive the rest of the ordered XRP or token later when the offer is consumed by other accounts' [Payment][] and [OfferCreate][] transactions. - If the account has created any trust lines without the [No Ripple flag](../tokens/fungible-tokens/rippling.md) enabled, or has enabled the Default Ripple flag and issued any currency, the account **can** receive the tokens of those trust lines in [Payment transactions][] as a result of rippling. It cannot be the destination of those transactions. @@ -76,8 +74,6 @@ If the result of the `Flags` value bitwise-AND the `lsfDepositAuth` flag value ( ## Preauthorization -_(Added by the [DepositPreauth amendment][].)_ - Accounts with DepositAuth enabled can _preauthorize_ certain senders, to allow payments from those senders to succeed even with DepositAuth enabled. This allows specific senders to send funds directly without the receiver taking action on each transaction individually. Preauthorization is not required to use DepositAuth, but can make certain operations more convenient. Preauthorization is currency-agnostic. You cannot preauthorize accounts for specific currencies only. @@ -94,6 +90,9 @@ After the DepositPreauth transaction has been processed, the authorized account Preauthorization has no effect on the other ways to send money to an account with DepositAuth enabled. See [Precise Semantics](#precise-semantics) for the exact rules. +{% amendment-disclaimer name="DepositPreauth" /%} + + ### Checking for Authorization You can use the [deposit_authorized method][] to see if an account is authorized to deposit to another account. This method checks two things: @@ -111,9 +110,6 @@ You can use the [deposit_authorized method][] to see if an account is authorized - The `DisallowXRP` flag indicates that an account should not receive XRP. This is a softer protection than Deposit Authorization, and is not enforced by the XRP Ledger. (Client applications should honor this flag or at least warn about it.) - The `RequireDest` flag indicates that an account can only receive currency amounts if the sending transaction specifies a [Destination Tag](../transactions/source-and-destination-tags.md). This protects users from forgetting to indicate the purpose of a payment, but does not protect recipients from unknown senders, who can make up arbitrary destination tags. - [Partial Payments](../payment-types/partial-payments.md) provide a way for accounts to return unwanted payments while subtracting [transfer fees](../tokens/fungible-tokens/transfer-fees.md) and exchange rates from the amount delivered instead of adding them to the amount sent. - - -[DepositPreauth amendment]: /resources/known-amendments.md#depositpreauth {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/accounts/multi-signing.md b/docs/concepts/accounts/multi-signing.md index a4f9f4504bc..f4e00fa7b3c 100644 --- a/docs/concepts/accounts/multi-signing.md +++ b/docs/concepts/accounts/multi-signing.md @@ -38,7 +38,7 @@ The quorum value of a list is the minimum weight total required to authorize a t You can also add up to 256 bits of arbitrary data to each signer's entry in the list. This data is not required or used by the network, but can be used by smart contracts or other applications to identify or confirm other data about the signers. -_(Added by the [ExpandedSignerList amendment][].)_ +{% amendment-disclaimer name="ExpandedSignerList" /%} ### Examples Using Signer Weight and Quorum diff --git a/docs/concepts/accounts/permission-delegation.md b/docs/concepts/accounts/permission-delegation.md index 61c4cf7db27..df63fc5a517 100644 --- a/docs/concepts/accounts/permission-delegation.md +++ b/docs/concepts/accounts/permission-delegation.md @@ -10,7 +10,7 @@ status: not_enabled Permission delegation is the function of granting various permissions to another account to send permissions on behalf of your account. You can use permission delegation to enable flexible security paradigms such as role-based access control, instead of or alongside techniques such as [multi-signing](./multi-signing.md). -_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_ + {% amendment-disclaimer name="PermissionDelegation" /%} ## Background: The Need for Permission Delegation diff --git a/docs/concepts/accounts/tickets.md b/docs/concepts/accounts/tickets.md index fc86ebe84a3..4f01c28d7b6 100644 --- a/docs/concepts/accounts/tickets.md +++ b/docs/concepts/accounts/tickets.md @@ -9,10 +9,10 @@ labels: --- # Tickets -_(Added by the [TicketBatch amendment][].)_ - A Ticket in the XRP Ledger is a way of setting aside a [sequence number][Sequence Number] for a transaction without sending it right away. Tickets allow transactions to be sent outside of the normal sequence order. One use case for this is to allow for [multi-signed transactions](multi-signing.md) where it may take a while to collect the necessary signatures: while collecting signatures for a transaction that uses a Ticket, you can still send other transactions. +{% amendment-disclaimer name="TicketBatch" /%} + ## Background [Transactions](../transactions/index.md) have sequence numbers so that any given transaction can execute no more than once. Sequence numbers also make sure any given transaction is unique: if you send the exact same amount of money to the same person multiple times, the Sequence Number is one detail that is guaranteed to be different each time. Finally, Sequence Numbers provide an elegant way to put transactions in a consistent order, even if some of them arrive out of order when sent throughout the network. diff --git a/docs/concepts/consensus-protocol/negative-unl.md b/docs/concepts/consensus-protocol/negative-unl.md index 2ce382fc3fb..30decaabc16 100644 --- a/docs/concepts/consensus-protocol/negative-unl.md +++ b/docs/concepts/consensus-protocol/negative-unl.md @@ -1,19 +1,17 @@ --- -html: negative-unl.html -parent: consensus.html seo: description: Understand how Negative UNL improves the ledger's resilience during partial outages. labels: - - Blockchain + - Blockchain --- # Negative UNL -_Added by the [NegativeUNL Amendment](/resources/known-amendments.md#negativeunl)._ - The _Negative UNL_ is a feature of the XRP Ledger [consensus protocol](index.md) that improves _liveness_, the network's ability to make forward progress during a partial outage. Using the Negative UNL, servers adjust their effective UNLs based on which validators are currently online and operational, so that a new [ledger version](../ledgers/index.md) can be declared _validated_ even if several trusted validators are offline. The Negative UNL has no impact on how the network processes transactions or what transactions' outcomes are, except that it improves the network's ability to declare outcomes final during some types of partial outages. +{% amendment-disclaimer name="NegativeUNL" /%} + ## Background Each server in the XRP Ledger protocol independently decides a ledger version is validated when a quorum of its trusted validators agree. A server's trusted validators are defined by that server's UNL (Unique Node List), a list of validators it trusts not to collude. By default, servers are configured to trust any validator on at least one of two lists, one UNL published by the XRP Ledger Foundation and one UNL published by Ripple. diff --git a/docs/concepts/decentralized-storage/credentials.md b/docs/concepts/decentralized-storage/credentials.md index dfb6791a440..0bc862424ca 100644 --- a/docs/concepts/decentralized-storage/credentials.md +++ b/docs/concepts/decentralized-storage/credentials.md @@ -1,7 +1,6 @@ --- seo: description: Create and manage credentials on the blockchain, which can provide authorization for payments or other features, while respecting privacy and decentralization. -status: not_enabled --- # Credentials diff --git a/docs/concepts/decentralized-storage/decentralized-identifiers.md b/docs/concepts/decentralized-storage/decentralized-identifiers.md index 2a194698f3d..8e3939d94b8 100644 --- a/docs/concepts/decentralized-storage/decentralized-identifiers.md +++ b/docs/concepts/decentralized-storage/decentralized-identifiers.md @@ -8,7 +8,7 @@ labels: --- # Decentralized Identifiers -_(Requires the [DID amendment][])_ +{% amendment-disclaimer name="DID" /%} A Decentralized Identifier (DID) is a new type of identifier defined by the World Wide Web Consortium (W3C) that enables verifiable, digital identities. DIDs are fully under the control of the DID owner, independent from any centralized registry, identity provider, or certificate authority. diff --git a/docs/concepts/decentralized-storage/price-oracles.md b/docs/concepts/decentralized-storage/price-oracles.md index 93261d14769..32a90c6c2c8 100644 --- a/docs/concepts/decentralized-storage/price-oracles.md +++ b/docs/concepts/decentralized-storage/price-oracles.md @@ -1,19 +1,21 @@ +--- +seo: + description: Price oracles gather real-world market prices and record them in the blockchain so that other tools and technology can access this data directly. +--- # Price Oracles -_(Requires the [PriceOracle amendment][])_ +Price oracles gather real-world market prices and record them in the blockchain so that other tools and technology can access this data directly. -Blockchains can't inherently interact with and "know" what's happening off the network, but many of its use cases in decentralized finance require this information. - -Price oracles solve this problem. An oracle is a service or technology that gathers real-world information, such as market prices, exchange rates, or interest rates, and relays it to the blockchain. Like blockchains, most oracles are also decentralized and validate data through multiple nodes. +Blockchains can't inherently interact with and "know" what's happening off the network, but many of its use cases in decentralized finance require this information. Price oracles solve this problem by putting the data on-chain where decentralized apps can find it. Like blockchains, most oracles are also decentralized and validate data through multiple nodes. {% admonition type="info" name="Note" %} - -Generally speaking, oracles aren't limited to only providing financial information. They can provide any type of info, such as what sports team won a game, or even the weather. The XRP Ledger's Price Oracle feature, however, is designed specifically for reporting the prices of assets. - +Generally speaking, oracles aren't limited to only providing financial information like asset prices, exchange rates, or interest rates. They can provide any type of info, such as what sports team won a game, or even the weather. The XRP Ledger's Price Oracle feature, however, is designed specifically for reporting the prices of assets. {% /admonition %} +{% amendment-disclaimer name="PriceOracle" /%} + -## How Oracles Works +## How Oracles Work Most oracle blockchain interactions work like this: diff --git a/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md b/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md index 5f5c9c9fe43..daca6683541 100644 --- a/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md +++ b/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md @@ -9,7 +9,7 @@ labels: --- # Automated Market Makers -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} Automated Market Makers (AMMs) provide liquidity in the XRP Ledger's decentralized exchange (DEX). Each AMM holds a pool of two assets. You can swap between the two assets at an exchange rate set by a mathematical formula. diff --git a/docs/concepts/tokens/decentralized-exchange/permissioned-domains.md b/docs/concepts/tokens/decentralized-exchange/permissioned-domains.md index 621c303c750..1f694429b58 100644 --- a/docs/concepts/tokens/decentralized-exchange/permissioned-domains.md +++ b/docs/concepts/tokens/decentralized-exchange/permissioned-domains.md @@ -2,8 +2,9 @@ seo: description: Learn how Permissioned Domains on the XRP Ledger enable controlled, secure blockchain environments. Explore their role in decentralized exchanges (DEXes) and lending protocols. labels: - - Compliance - - Permissioned Domains + - Compliance + - Permissioned Domains +status: not_enabled --- # Permissioned Domains diff --git a/docs/concepts/tokens/fungible-tokens/deep-freeze.md b/docs/concepts/tokens/fungible-tokens/deep-freeze.md index 554393cbfa4..a486fc3b01e 100644 --- a/docs/concepts/tokens/fungible-tokens/deep-freeze.md +++ b/docs/concepts/tokens/fungible-tokens/deep-freeze.md @@ -12,7 +12,7 @@ Deep Freeze lets token issuers on the XRP Ledger prevent token misuse by frozen Deep Freeze impacts trust lines that interact with payments, offers, DEX, and AMM. Issuers can block sending and receiving of funds for holders in deep freeze. -_(Requires the [DeepFreeze amendment][] )_ +{% amendment-disclaimer name="DeepFreeze" /%} ## Deep Freeze Mechanism diff --git a/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md b/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md index 540b64f6c12..fcbd1354fd0 100644 --- a/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md +++ b/docs/concepts/tokens/fungible-tokens/stablecoins/settings.md @@ -80,12 +80,11 @@ See [Freezing Tokens](../freezes.md). ### Clawback Flags -_(Requires the [Clawback amendment](/resources/known-amendments.md#clawback))_ - Clawback allows you to retrieve, or _clawback_, stablecoins from a trust line under specific circumstances. This gives you added ability to respond to challenges such as lost account access or malicious activity. See [Clawback](../../../../references/protocol/transactions/types/clawback.md). +{% amendment-disclaimer name="Clawback" /%} ### Fixed Supply diff --git a/docs/concepts/tokens/nfts/dynamic-nfts.md b/docs/concepts/tokens/nfts/dynamic-nfts.md index 8db541619b5..fa09f551bc7 100644 --- a/docs/concepts/tokens/nfts/dynamic-nfts.md +++ b/docs/concepts/tokens/nfts/dynamic-nfts.md @@ -4,29 +4,16 @@ seo: labels: - Non-fungible Tokens, NFTs --- - # Dynamic Non-Fungible Tokens (dNFTs) -Standard NFTs are immutable. Some use cases would benefit from the capability to update the referenced data object after the initial minting of an NFT. For example, a concert ticket for a postponed event could be updated with an alternate date, or a virtual trading card for an athlete could be periodically updated with current statistics. Dynamic Non-Fungible Tokens (dNFTs) provide the flexibility required for these use cases. +Standard NFTs are immutable. In some use cases, you need to update the referenced data object after the initial minting of an NFT. For example, a concert ticket for a postponed event could be updated with an alternate date, or a virtual trading card for an athlete could be periodically updated with current statistics. Dynamic Non-Fungible Tokens (dNFTs) provide the flexibility required for these use cases. ## Creating a dNFT -When minting a new NFT, set the `tfMutable` flag (`0x00000010`) to enable the ability to update the NFT's `URI` field. +When minting a new NFT, enable the `tfMutable` flag (`0x00000010`) to make the NFT mutable. ## Modifying a dNFT -Use the `NFTokenModify` transaction to update the URI field of a dNFT. Provide the `Account` of the issuer or an authorized minter, the `Owner` of the dNFT (if different than the `Account` address), the `NFTokenID`, and the `URI` to the new object data. - -### Sample NFTokenModify Transaction +The issuer, or their authorized minter, can modify a dNFT at any time, by sending a [NFTokenModify transaction][]. Only the `URI` field of the NFT can be changed this way. -```json -{ - "TransactionType": "NFTokenModify", - "Account": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", - "Owner": "rogue5HnPRSszD9CWGSUz8UGHMVwSSKF6", - "Fee": "10", - "Sequence": 33, - "NFTokenID": "0008C350C182B4F213B82CCFA4C6F59AD76F0AFCFBDF04D5A048C0A300000007", - "URI": "697066733A2F2F62616679626569636D6E73347A736F6C686C6976346C746D6E356B697062776373637134616C70736D6C6179696970666B73746B736D3472746B652F5665742E706E67", - } -``` +{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/tokens/nfts/index.md b/docs/concepts/tokens/nfts/index.md index 47f895658b2..525254f8a2b 100644 --- a/docs/concepts/tokens/nfts/index.md +++ b/docs/concepts/tokens/nfts/index.md @@ -11,7 +11,7 @@ labels: The XRP Ledger natively supports non-fungible tokens (NFTs, or “nifties” in the vernacular). Non-fungible tokens serve to encode ownership of unique physical, non-physical, or purely digital goods, such as works of art or in-game items. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} To represent digital assets similar to these, use the XRP Ledger's Non-Fungible Tokens feature (sometimes referred to by its standards draft number, [XLS-20](https://github.com/XRPLF/XRPL-Standards/discussions/46)). diff --git a/docs/concepts/tokens/nfts/trading.md b/docs/concepts/tokens/nfts/trading.md index e6806eedbc6..193f0f7d6de 100644 --- a/docs/concepts/tokens/nfts/trading.md +++ b/docs/concepts/tokens/nfts/trading.md @@ -11,7 +11,7 @@ labels: You can transfer NFTs between accounts on the XRP Ledger. You can offer to buy or sell an NFT, or accept offers from other accounts to buy an NFT you own. You can even give away an NFT by offering to sell it at a price of 0. All offers are created using [NFTokenCreateOffer transaction][]. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Reserve Requirements diff --git a/docs/concepts/xrpl-sidechains/cross-chain-bridges.md b/docs/concepts/xrpl-sidechains/cross-chain-bridges.md index b39c73b2040..c3eb001602a 100644 --- a/docs/concepts/xrpl-sidechains/cross-chain-bridges.md +++ b/docs/concepts/xrpl-sidechains/cross-chain-bridges.md @@ -10,7 +10,7 @@ labels: --- # Cross-Chain Bridges -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} Cross-chain bridges enable you to move XRP and tokens between the XRP Ledger and other blockchains. When referring to the blockchains connected by a bridge, one is the locking chain and the other the issuing chain. diff --git a/docs/concepts/xrpl-sidechains/index.md b/docs/concepts/xrpl-sidechains/index.md index e2072a64ef4..7ad05608439 100644 --- a/docs/concepts/xrpl-sidechains/index.md +++ b/docs/concepts/xrpl-sidechains/index.md @@ -9,7 +9,7 @@ labels: --- # XRPL Sidechains -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} A sidechain is an independent ledger with its own consensus algorithm, transaction types, rules, and nodes. It acts as its own blockchain, running parallel to the mainchain (XRP Ledger), enabling value to move between the two without compromising the speed, efficiency, and throughput of the mainchain. diff --git a/docs/concepts/xrpl-sidechains/witness-servers.md b/docs/concepts/xrpl-sidechains/witness-servers.md index a712af9f1ef..70be8d01bb0 100644 --- a/docs/concepts/xrpl-sidechains/witness-servers.md +++ b/docs/concepts/xrpl-sidechains/witness-servers.md @@ -11,7 +11,7 @@ labels: # Witness Servers [[Source]](https://github.com/seelabs/xbridge_witness "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} A _witness server_ acts as a neutral witness for transactions between a locking chain and an issuing chain. It listens to the door accounts on both sides of a bridge and signs attestations that confirm a transaction occurred. They are essentially acting as an oracle to “prove” that value was locked or burned on a source account, which allows the recipient to then claim (via minting or unlocking) the equivalent funds on the destination account. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md index e09a6cf1665..52ef0f89d03 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md @@ -9,7 +9,7 @@ labels: # account_channels [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source") -_(Added by the [PayChan amendment][].)_ +{% amendment-disclaimer name="PayChan" /%} The `account_channels` method returns information about an account's Payment Channels. This includes only channels where the specified account is the channel's source, not the destination. (A channel's "source" and "owner" are the same.) All information retrieved is relative to a particular version of the ledger. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md index db656adea23..e1bf1bd9d5c 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md @@ -216,10 +216,10 @@ The `account_flags` field contains the following nested fields: | `defaultRipple` | Boolean | If `true`, the account allows [rippling](../../../../concepts/tokens/fungible-tokens/rippling.md) on its trust lines by default. | | `depositAuth` | Boolean | If `true`, the account is using [Deposit Authorization](../../../../concepts/accounts/depositauth.md) and does not accept any payments from unknown parties. | | `disableMasterKey` | Boolean | If `true`, the account's [master key pair](../../../../concepts/accounts/cryptographic-keys.md) is disabled. | -| `disallowIncomingCheck` | Boolean | If `true`, the account does not allow others to send [Checks](../../../../concepts/payment-types/checks.md) to it. _(Requires the [DisallowIncoming amendment][])_ | -| `disallowIncomingNFTokenOffer` | Boolean | If `true`, the account does not allow others to make [NFT buy or sell offers](../../../../concepts/tokens/nfts/trading.md) to it. _(Requires the [DisallowIncoming amendment][])_ | -| `disallowIncomingPayChan` | Boolean | If `true`, the account does not allow others to make [Payment Channels](../../../../concepts/payment-types/payment-channels.md) to it. _(Requires the [DisallowIncoming amendment][])_ | -| `disallowIncomingTrustline` | Boolean | If `true`, the account does not allow others to make [trust lines](../../../../concepts/tokens/fungible-tokens/index.md) to it. _(Requires the [DisallowIncoming amendment][])_ | +| `disallowIncomingCheck` | Boolean | If `true`, the account does not allow others to send [Checks](../../../../concepts/payment-types/checks.md) to it. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `disallowIncomingNFTokenOffer` | Boolean | If `true`, the account does not allow others to make [NFT buy or sell offers](../../../../concepts/tokens/nfts/trading.md) to it. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `disallowIncomingPayChan` | Boolean | If `true`, the account does not allow others to make [Payment Channels](../../../../concepts/payment-types/payment-channels.md) to it. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `disallowIncomingTrustline` | Boolean | If `true`, the account does not allow others to make [trust lines](../../../../concepts/tokens/fungible-tokens/index.md) to it. {% amendment-disclaimer name="DisallowIncoming" /%} | | `disallowIncomingXRP` | Boolean | If `true`, the account does not want to receive XRP from others. (This is advisory, and not enforced at a protocol level.) | | `globalFreeze` | Boolean | If `true`, all tokens issued by the account are currently frozen. | | `noFreeze` | Boolean | If `true`, the account has permanently given up the abilities to freeze individual trust lines or end a global freeze. See [No Freeze](../../../../concepts/tokens/fungible-tokens/freezes.md#no-freeze) for details. | diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md index 33870f0257a..c1464a7b591 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md @@ -11,7 +11,7 @@ labels: The `account_nfts` method returns a list of `NFToken` objects for the specified account. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders.md b/docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders.md index 9364e0dafa5..cc775f2a87e 100644 --- a/docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders.md +++ b/docs/references/http-websocket-apis/public-api-methods/clio-methods/mpt_holders.md @@ -12,7 +12,7 @@ stautus: not_enabled [[Source]](https://github.com/XRPLF/clio/blob/develop/src/rpc/handlers/MPTHolders.cpp "Source") -_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="MPTokensV1" /%} For a given `MPTokenIssuanceID` and ledger sequence, `mpt_holders` returns all holders of that [MPT](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) 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`. {% badge href="https://github.com/XRPLF/clio/releases/tag/2.3.0" %}New in: Clio v2.3.0{% /badge %} diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index 4896d77123e..209d2847ab9 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -164,7 +164,7 @@ rippled json ledger_entry '{ "account_root": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 ### Get AMM Entry -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} Retrieve an Automated Market-Maker (AMM) object from the ledger. This is similar to [amm_info method][], but the `ledger_entry` version returns only the ledger entry as stored. @@ -231,7 +231,7 @@ rippled json ledger_entry '{ "amm": { "asset": { "currency": "XRP" }, "asset2": ### Get Bridge Entry -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} Retrieve a [Bridge entry](../../../protocol/ledger-data/ledger-entry-types/bridge.md), which represents a single cross-chain bridge that connects the XRP Ledger with another blockchain. @@ -467,7 +467,7 @@ rippled json ledger_entry '{ "offer": { "account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJY ### Get Oracle Entry -_(Requires the [PriceOracle amendment][])_ +{% amendment-disclaimer name="PriceOracle" /%} Retrieve an [Oracle entry](../../../protocol/ledger-data/ledger-entry-types/oracle.md), which represents a single price oracle that can store token prices. @@ -792,7 +792,7 @@ rippled json ledger_entry '{ "deposit_preauth": { "owner": "rf1BiGeXwwQoi8Z2ueFY ### Get Ticket Entry -Retrieve a [Ticket entry](../../../protocol/ledger-data/ledger-entry-types/ticket.md), which represents a [sequence number][] set aside for future use. _(Added by the [TicketBatch amendment][])_ +Retrieve a [Ticket entry](../../../protocol/ledger-data/ledger-entry-types/ticket.md), which represents a [sequence number][] set aside for future use. {% amendment-disclaimer name="TicketBatch" /%} | Field | Type | Description | |:--------------------|:---------------------|:----------------------| diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md index 0916b98bd3e..70aa9b392c8 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md @@ -13,7 +13,7 @@ labels: The {% code-page-name /%} method gets information about an [Automated Market Maker (AMM)](/docs/concepts/tokens/decentralized-exchange/automated-market-makers) instance. -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} ### Request Format diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md index 1c60cdae1e2..bb2118faf08 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md @@ -71,7 +71,7 @@ The request includes the following parameters: |:---------------|:-----------------|:----------|-------------| | `taker_gets` | Object | Yes | The asset the account taking the offer would receive, as a [currency without an amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | | `taker_pays` | Object | Yes | The asset the account taking the offer would pay, as a [currency without an amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | -| `domain` | [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, return offers from the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) instead of using the open DEX. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `domain` | [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, return offers from the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) instead of using the open DEX. {% amendment-disclaimer name="PermissionedDEX" /%} | | `ledger_hash` | [Hash][] | No | The unique hash of the ledger version to use. (See [Specifying Ledgers][]) | | `ledger_index` | [Ledger Index][] | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) | | `limit` | Number | No | The maximum number of offers to return. The response may include fewer results. | diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md index f984b88ca0f..2e0d971ce39 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md @@ -6,7 +6,7 @@ labels: --- # get_aggregate_price -_(Requires the [PriceOracle amendment][])_ +{% amendment-disclaimer name="PriceOracle" /%} [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/GetAggregatePrice.cpp "Source") diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md index a7dcf8f37cb..9c76231efbb 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md @@ -11,7 +11,7 @@ labels: The `nft_buy_offers` method returns a list of buy offers for a given [NFToken][] object. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md index a73786b8046..f84a15e7885 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md @@ -11,7 +11,7 @@ labels: The `nft_sell_offers` method returns a list of sell offers for a given [NFToken][] object. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md index bd8ecce7648..c572fbc25f9 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md @@ -61,7 +61,7 @@ The request includes the following parameters: | `source_account` | String - [Address][] | Yes | The account to find a path from. (In other words, the account that would be sending a payment.) | | `destination_account` | String - [Address][] | Yes | The account to find a path to. (In other words, the account that would receive a payment.) | | `destination_amount` | [Currency Amount][] | Yes | How much the destination account would receive. **Special case:** You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for tokens). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). | -| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, only return paths that use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, only return paths that use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). {% amendment-disclaimer name="PermissionedDEX" /%} | | `paths` | Array | No | Array of arrays of objects, representing [payment paths](../../../../concepts/tokens/fungible-tokens/paths.md) to check. | `send_max` | [Currency Amount][] | No | Maximum amount that would be spent. Not compatible with `source_currencies`. | You can use this to keep updated on changes to particular paths you already know about, or to check the overall cost to make a payment along a certain path. | diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md index 1dc0bf439c5..059fcfa81be 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md @@ -90,7 +90,7 @@ The request includes the following parameters: | `source_account` | String - [Address][] | Yes | The account that would send funds | | `destination_account` | String - [Address][] | Yes | The account that would receive funds | | `destination_amount` | [Currency Amount][] | Yes | How much the destination account would receive. **Special case:** You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for tokens). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). | -| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, only return paths that use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, only return paths that use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). {% amendment-disclaimer name="PermissionedDEX" /%} | | `ledger_hash` | String - [Hash][] | No | The unique hash of the ledger version to use. (See [Specifying Ledgers][]) | | `ledger_index` | [Ledger Index][] | No | The ledger index of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) | | `send_max` | [Currency Amount][] | No | Maximum amount that would be spent. Cannot be used with `source_currencies`. | diff --git a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md index f057876f24d..a57281a94bb 100644 --- a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md +++ b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md @@ -1,6 +1,4 @@ --- -html: channel_authorize.html -parent: payment-channel-methods.html seo: description: Sign a claim for money from a payment channel. labels: @@ -9,10 +7,10 @@ labels: # channel_authorize [[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") -_(Added by the [PayChan amendment][] to be enabled.)_ - The `channel_authorize` method creates a signature that can be used to redeem a specific amount of XRP or fungible tokens from a payment channel. +{% amendment-disclaimer name="PayChan" /%} + ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md index 9ec605ec349..7538c14bbbe 100644 --- a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md +++ b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md @@ -9,10 +9,10 @@ labels: # channel_verify [[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") -_(Added by the [PayChan amendment][] to be enabled.)_ - The `channel_verify` method checks the validity of a signature that can be used to redeem a specific amount of XRP or fungible tokens from a payment channel. +{% amendment-disclaimer name="PayChan" /%} + ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index 46eb7ba360a..e5ebdb8ee77 100644 --- a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md +++ b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md @@ -103,7 +103,7 @@ Each member of the `books` array, if provided, is an object with the following f | `taker_gets` | Object - Currency | Yes | Specification of which currency the account taking the offer would receive, as a [currency object with no amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | | `taker_pays` | Object - Currency | Yes | Specification of which currency the account taking the offer would pay, as a [currency object with no amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | | `both` | Boolean | No | If `true`, return both sides of the order book. The default is `false`. | -| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, subscribe to the order books for the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) instead of the open DEX. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `domain` | String - [Hash][] | No | The ledger entry ID of a permissioned domain. If provided, subscribe to the order books for the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) instead of the open DEX. {% amendment-disclaimer name="PermissionedDEX" /%} | | `snapshot` | Boolean | No | If `true`, return the current state of the order book once when you subscribe before sending updates. The default is `false`. | | `taker` | String - [Address][] | No | The acount to use as a perspective for viewing offers. This affects the funding status and fees of [offers](../../../../concepts/tokens/decentralized-exchange/offers.md). | diff --git a/docs/references/protocol/data-types/nftoken.md b/docs/references/protocol/data-types/nftoken.md index 8c5d78deffc..1441a8b82a5 100644 --- a/docs/references/protocol/data-types/nftoken.md +++ b/docs/references/protocol/data-types/nftoken.md @@ -10,7 +10,7 @@ labels: The `NFToken` object represents a single non-fungible token (NFT). It is not stored on its own, but is contained in a [NFTokenPage object][] alongside other `NFToken` objects. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/data-types/permission-values.md b/docs/references/protocol/data-types/permission-values.md index 8f78370a74b..2838d0e7c6e 100644 --- a/docs/references/protocol/data-types/permission-values.md +++ b/docs/references/protocol/data-types/permission-values.md @@ -3,6 +3,7 @@ seo: description: Format for permissions that can be granted to other accounts. label: - Permissions +status: not_enabled --- # Permission Values @@ -11,7 +12,7 @@ label: - **Transaction Type Permissions** - Permission to send transactions with the specified [transaction type](../transactions/types/index.md). - **Granular Permissions** - Permission to send transactions with a specific subset of functionality. -_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="PermissionDelegation" /%} ## Numeric and String Values diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index c86fd4c0ee1..dda47f7849d 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -39,30 +39,30 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e |:------------------------------|:----------|:------------------|:----------|:-------------| | `Account` | String | AccountID | Yes | The identifying (classic) address of this [account](../../../../concepts/accounts/index.md). | | `AccountTxnID` | String | UInt256 | No | The identifying hash of the transaction most recently sent by this account. This field must be enabled to use the [`AccountTxnID` transaction field](../../transactions/common-fields.md#accounttxnid). To enable it, send an [AccountSet transaction with the `asfAccountTxnID` flag enabled](../../transactions/types/accountset.md#accountset-flags). | -| `AMMID` | String | UInt256 | No | _(Added by the [AMM amendment][])_ The ledger entry ID of the corresponding AMM ledger entry. Set during account creation; cannot be modified. If present, indicates that this is a special AMM AccountRoot; always omitted on non-AMM accounts. | +| `AMMID` | String | UInt256 | No | {% amendment-disclaimer name="AMM" /%} The ledger entry ID of the corresponding AMM ledger entry. Set during account creation; cannot be modified. If present, indicates that this is a special AMM AccountRoot; always omitted on non-AMM accounts. | | `Balance` | String | Amount | No | The account's current [XRP balance in drops][XRP, in drops], represented as a string. | | `BurnedNFTokens` | Number | UInt32 | No | How many total of this account's issued [non-fungible tokens](../../../../concepts/tokens/nfts/index.md) have been burned. This number is always equal or less than `MintedNFTokens`. | | `Domain` | String | Blob | No | A domain associated with this account. In JSON, this is the hexadecimal for the ASCII representation of the domain. [Cannot be more than 256 bytes in length.](https://github.com/xrplf/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | | `EmailHash` | String | UInt128 | No | The md5 hash of an email address. Clients can use this to look up an avatar through services such as [Gravatar](https://en.gravatar.com/). | -| `FirstNFTokenSequence` | Number | UInt32 | No | The account's [Sequence Number][] at the time it minted its first [non-fungible-token](../../../../concepts/tokens/nfts/index.md). _(Added by the [fixNFTokenRemint amendment][])_ | +| `FirstNFTokenSequence` | Number | UInt32 | No | The account's [Sequence Number][] at the time it minted its first [non-fungible-token](../../../../concepts/tokens/nfts/index.md). {% amendment-disclaimer name="fixNFTokenRemint" /%} | | `LedgerEntryType` | String | UInt16 | Yes | The value `0x0061`, mapped to the string `AccountRoot`, indicates that this is an AccountRoot object. | | `MessageKey` | String | Blob | No | A public key that may be used to send encrypted messages to this account. In JSON, uses hexadecimal. Must be exactly 33 bytes, with the first byte indicating the key type: `0x02` or `0x03` for secp256k1 keys, `0xED` for Ed25519 keys. | -| `MintedNFTokens` | Number | UInt32 | No | How many total [non-fungible tokens](../../../../concepts/tokens/nfts/index.md) have been minted by and on behalf of this account. _(Added by the [NonFungibleTokensV1_1 amendment][])_ | -| `NFTokenMinter` | String | AccountID | No | Another account that can mint [non-fungible tokens](../../../../concepts/tokens/nfts/index.md) on behalf of this account. _(Added by the [NonFungibleTokensV1_1 amendment][])_ | +| `MintedNFTokens` | Number | UInt32 | No | How many total [non-fungible tokens](../../../../concepts/tokens/nfts/index.md) have been minted by and on behalf of this account. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | +| `NFTokenMinter` | String | AccountID | No | Another account that can mint [non-fungible tokens](../../../../concepts/tokens/nfts/index.md) on behalf of this account. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `OwnerCount` | Number | UInt32 | Yes | The number of objects this account owns in the ledger, which contributes to its owner reserve. | | `PreviousTxnID` | String | UInt256 | Yes | The identifying hash of the transaction that most recently modified this object. | | `PreviousTxnLgrSeq` | Number | UInt32 | Yes |The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this object. | | `RegularKey` | String | AccountID | No | The address of a [key pair](../../../../concepts/accounts/cryptographic-keys.md) that can be used to sign transactions for this account instead of the master key. Use a [SetRegularKey transaction][] to change this value. | | `Sequence` | Number | UInt32 | Yes | The [sequence number](../../data-types/basic-data-types.md#account-sequence) of the next valid transaction for this account. | -| `TicketCount` | Number | UInt32 | No | How many [Tickets](../../../../concepts/accounts/tickets.md) this account owns in the ledger. This is updated automatically to ensure that the account stays within the hard limit of 250 Tickets at a time. This field is omitted if the account has zero Tickets. _(Added by the [TicketBatch amendment][].)_ | -| `TickSize` | Number | UInt8 | No | How many significant digits to use for exchange rates of Offers involving currencies issued by this address. Valid values are `3` to `15`, inclusive. _(Added by the [TickSize amendment][].)_ | +| `TicketCount` | Number | UInt32 | No | How many [Tickets](../../../../concepts/accounts/tickets.md) this account owns in the ledger. This is updated automatically to ensure that the account stays within the hard limit of 250 Tickets at a time. This field is omitted if the account has zero Tickets. {% amendment-disclaimer name="TicketBatch" /%} | +| `TickSize` | Number | UInt8 | No | How many significant digits to use for exchange rates of Offers involving currencies issued by this address. Valid values are `3` to `15`, inclusive. {% amendment-disclaimer name="TickSize" /%} | | `TransferRate` | Number | UInt32 | No | A [transfer fee](../../../../concepts/tokens/fungible-tokens/transfer-fees.md) to charge other users for sending currency issued by this account to each other. | | `WalletLocator` | String | UInt256 | No | An arbitrary 256-bit value that users can set. | | `WalletSize` | Number | UInt32 | No | Unused. (The code supports this field but there is no way to set it.) | ## Special AMM AccountRoot Entries -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} Automated Market Makers use an AccountRoot ledger entry to issue their LP Tokens and hold the assets in the AMM pool, and an [AMM ledger entry](amm.md) for tracking some of the details of the AMM. The address of an AMM's AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoot objects are created with the following settings: @@ -87,14 +87,14 @@ AccountRoot objects can have the following flags combined in the `Flags` field: | Flag Name | Hex Value | Decimal Value | Corresponding [AccountSet Flag](../../transactions/types/accountset.md#accountset-flags) | Description | |-----------------------------------|--------------|-------------------|-----------------------------------|----| -| `lsfAllowTrustLineClawback` | `0x80000000` | 2147483648 | `asfAllowTrustLineClawback` | Enable [Clawback](../../../../concepts/tokens/fungible-tokens/clawing-back-tokens.md) for this account. _(Requires the [Clawback amendment][].)_ | +| `lsfAllowTrustLineClawback` | `0x80000000` | 2147483648 | `asfAllowTrustLineClawback` | Enable [Clawback](../../../../concepts/tokens/fungible-tokens/clawing-back-tokens.md) for this account. {% amendment-disclaimer name="Clawback" /%} | | `lsfDefaultRipple` | `0x00800000` | 8388608 | `asfDefaultRipple` | Enable [rippling](../../../../concepts/tokens/fungible-tokens/rippling.md) on this addresses's trust lines by default. Required for issuing addresses; discouraged for others. | -| `lsfDepositAuth` | `0x01000000` | 16777216 | `asfDepositAuth` | This account has [DepositAuth](../../../../concepts/accounts/depositauth.md) enabled, meaning it can only receive funds from transactions it sends, and from [preauthorized](../../../../concepts/accounts/depositauth.md#preauthorization) accounts. _(Added by the [DepositAuth amendment][])_ | +| `lsfDepositAuth` | `0x01000000` | 16777216 | `asfDepositAuth` | This account has [DepositAuth](../../../../concepts/accounts/depositauth.md) enabled, meaning it can only receive funds from transactions it sends, and from [preauthorized](../../../../concepts/accounts/depositauth.md#preauthorization) accounts. {% amendment-disclaimer name="DepositAuth" /%} | | `lsfDisableMaster` | `0x00100000` | 1048576 | `asfDisableMaster` | Disallows use of the master key to sign transactions for this account. | -| `lsfDisallowIncomingCheck` | `0x08000000` | 134217728 | `asfDisallowIncomingCheck` | This account blocks incoming Checks. _(Added by the [DisallowIncoming amendment][].)_ | -| `lsfDisallowIncomingNFTokenOffer` | `0x04000000` | 67108864 | `asfDisallowIncomingNFTokenOffer` | This account blocks incoming NFTokenOffers. _(Added by the [DisallowIncoming amendment][].)_ | -| `lsfDisallowIncomingPayChan` | `0x10000000` | 268435456 | `asfDisallowIncomingPayChan` | This account blocks incoming Payment Channels. _(Added by the [DisallowIncoming amendment][].)_ | -| `lsfDisallowIncomingTrustline` | `0x20000000` | 536870912 | `asfDisallowIncomingTrustline` | This account blocks incoming trust lines. _(Added by the [DisallowIncoming amendment][].)_ | +| `lsfDisallowIncomingCheck` | `0x08000000` | 134217728 | `asfDisallowIncomingCheck` | This account blocks incoming Checks. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingNFTokenOffer` | `0x04000000` | 67108864 | `asfDisallowIncomingNFTokenOffer` | This account blocks incoming NFTokenOffers. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingPayChan` | `0x10000000` | 268435456 | `asfDisallowIncomingPayChan` | This account blocks incoming Payment Channels. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `lsfDisallowIncomingTrustline` | `0x20000000` | 536870912 | `asfDisallowIncomingTrustline` | This account blocks incoming trust lines. {% amendment-disclaimer name="DisallowIncoming" /%} | | `lsfDisallowXRP` | `0x00080000` | 524288 | `asfDisallowXRP` | Client applications should not send XRP to this account. (Advisory; not enforced by the protocol.) | | `lsfGlobalFreeze` | `0x00400000` | 4194304 | `asfGlobalFreeze` | All assets issued by this account are frozen. | | `lsfNoFreeze` | `0x00200000` | 2097152 | `asfNoFreeze` | This account cannot freeze trust lines connected to it. Once enabled, cannot be disabled. | diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md b/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md index 2071868623d..1f3255764b4 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md @@ -52,8 +52,8 @@ In addition to the [common fields](../common-fields.md), the {% code-page-name / | `Flags` | Number | UInt32 | Yes | A bit-map of boolean flags enabled for this object. Currently, the protocol defines no flags for `Amendments` objects. The value is always `0`. | | `LedgerEntryType` | String | UInt16 | Yes | The value `0x0066`, mapped to the string `Amendments`, indicates that this object describes the status of amendments to the XRP Ledger. | | `Majorities` | Array | Array | No | Array of objects describing the status of amendments that have majority support but are not yet enabled. If omitted, there are no pending amendments with majority support. | -| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | Each member of the `Majorities` field, if it is present, is an object with one field, `Majority`, whose contents are a nested object with the following fields: diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/amm.md b/docs/references/protocol/ledger-data/ledger-entry-types/amm.md index 138be015c06..5cc864dde08 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/amm.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/amm.md @@ -9,7 +9,7 @@ labels: An `AMM` ledger entry describes a single [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance. This is always paired with a [special AccountRoot entry](accountroot.md#special-amm-accountroot-entries). You can create an AMM by sending an [AMMCreate transaction][]. -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} ## Example AMM JSON @@ -68,8 +68,8 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e | `Account` | String - [Address][] | AccountID | Yes | The address of the [special account](accountroot.md#special-amm-accountroot-entries) that holds this AMM's assets. | | `AuctionSlot` | Object | Object | No | Details of the current owner of the auction slot, as an [Auction Slot object](#auction-slot-object). | | `LPTokenBalance` | [Currency Amount][] | Amount | Yes | The total outstanding balance of liquidity provider tokens from this AMM instance. The holders of these tokens can vote on the AMM's trading fee in proportion to their holdings, or redeem the tokens for a share of the AMM's assets which grows with the trading fees collected. | -| `PreviousTxnID` | String - [Hash][] | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String - [Hash][] | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | | `TradingFee` | Number | UInt16 | Yes | The percentage fee to be charged for trades against this AMM instance, in units of 1/100,000. The maximum value is 1000, for a 1% fee. | | `VoteSlots` | Array | Array | No | A list of vote objects, representing votes on the pool's trading fee. | diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md b/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md index f7b8beda142..0d2457df1af 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md @@ -10,7 +10,7 @@ status: not_enabled The `Bridge` ledger entry represents a single cross-chain bridge that connects the XRP Ledger with another blockchain, such as its sidechain, and enables value in the form of XRP and other tokens (IOUs) to move efficiently between the two blockchains. You can create a bridge by sending an [XChainCreateBridge transaction][]. -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} ## Example Bridge JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/check.md b/docs/references/protocol/ledger-data/ledger-entry-types/check.md index afe79352dba..1dcee15977e 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/check.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/check.md @@ -9,7 +9,7 @@ labels: A `Check` entry describes a [check](../../../../concepts/payment-types/checks.md), similar to a paper personal check, which can be cashed by its destination to get money from its sender. You can create a check by sending a [CheckCreate transaction][]. -_(Added by the [Checks amendment][].)_ +{% amendment-disclaimer name="Checks" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/credential.md b/docs/references/protocol/ledger-data/ledger-entry-types/credential.md index c4415c40bcf..098a246f123 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/credential.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/credential.md @@ -7,7 +7,7 @@ status: not_enabled A `Credential` entry represents a [credential](../../../../concepts/decentralized-storage/credentials.md), which contains an attestation about a _subject_ account from a _credential issuer_ account. The meaning of the attestation is defined by the issuer. -_(Requires the [Credentials amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="Credentials" /%} ## Example Credential JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/delegate.md b/docs/references/protocol/ledger-data/ledger-entry-types/delegate.md index ea0972566d6..88db81e1748 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/delegate.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/delegate.md @@ -11,7 +11,7 @@ status: not_enabled A `Delegate` ledger entry stores a set of permissions that an account has delegated to another account. You create a `Delegate` entry by sending a [DelegateSet transaction][]. -_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="PermissionDelegation" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md b/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md index 70d28486e2e..bb1eb56c8b6 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md @@ -101,7 +101,6 @@ In this case, the ID is the [SHA-512Half][] of the following values, concatenate * The AccountID in the `Authorize` field ### Credential Preauthorization -_(Requires the [Credentials amendment][]. {% not-enabled /%})_ In this case, the ID is the [SHA-512Half][] of the following values, concatenated in order: @@ -109,6 +108,8 @@ In this case, the ID is the [SHA-512Half][] of the following values, concatenate * The AccountID of the owner of this object (the sender of the [DepositPreauth transaction][] that created this object; in other words, the one that granted the preauthorization) * The contents of the `AuthorizeCredentials` field. +{% amendment-disclaimer name="Credentials" /%} + ## See Also - **Transactions** diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/did.md b/docs/references/protocol/ledger-data/ledger-entry-types/did.md index a1e332e423a..5949293784e 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/did.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/did.md @@ -9,7 +9,7 @@ labels: A `DID` ledger entry holds references to, or data associated with, a single [Decentralized Identifier (DID)](../../../../concepts/decentralized-storage/decentralized-identifiers.md). You can create or modify a DID by sending a [DIDSet transaction][]. -_(Added by the [DID amendment][])_ +{% amendment-disclaimer name="DID" /%} ## Example DID JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md b/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md index 445165156ef..cc0098e22ea 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md @@ -97,7 +97,7 @@ All types of directories are automatically updated by the protocol as necessary. | Name | JSON Type | [Internal Type][] | Required? | Description | |:--------------------|:----------|:------------------|:----------|:------------| -| `DomainID` | String | UInt256 | No | (Offer directories only) The ledger entry ID of a permissioned domain. If present, this order book belongs to the corresponding [Permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). Otherwise, this order book is part of the open DEX. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `DomainID` | String | UInt256 | No | (Offer directories only) The ledger entry ID of a permissioned domain. If present, this order book belongs to the corresponding [Permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). Otherwise, this order book is part of the open DEX. {% amendment-disclaimer name="PermissionedDEX" /%} | | `ExchangeRate` | String | UInt64 | No | (Offer directories only) **DEPRECATED**. Do not use. | | `Flags` | Number | UInt32 | Yes | A bit-map of boolean flags enabled for this object. Currently, the protocol defines no flags for `DirectoryNode` objects. The value is always `0`. | | `Indexes` | Array | Vector256 | Yes | The contents of this directory: an array of IDs of other objects. | @@ -106,8 +106,8 @@ All types of directories are automatically updated by the protocol as necessary. | `LedgerEntryType` | String | UInt16 | Yes | The value `0x0064`, mapped to the string `DirectoryNode`, indicates that this object is part of a directory. | | `NFTokenID` | String | UInt256 | No | (NFT offer directories only) ID of the NFT in a buy or sell offer. | | `Owner` | String | AccountID | No | (Owner directories only) The address of the account that owns the objects in this directory. | -| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | | `RootIndex` | String | UInt256 | Yes | The ID of root object for this directory. | | `TakerGetsCurrency` | String | UInt160 | No | (Offer directories only) The currency code of the `TakerGets` amount from the offers in this directory. | | `TakerGetsIssuer` | String | UInt160 | No | (Offer directories only) The issuer of the `TakerGets` amount from the offers in this directory. | @@ -137,7 +137,7 @@ Owner directories and offer directories for fungible tokens do not use flags; th There are three different formulas for creating the ID of a DirectoryNode, depending on which of the following the DirectoryNode represents: * The first page (also called the root) of an Owner or NFT Offer directory -* The first page of an Offer directory, with variants for the open DEX and permissioned DEX _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ +* The first page of an Offer directory, with variants for the open DEX and permissioned DEX {% amendment-disclaimer name="PermissionedDEX" /%} * Later pages of any type The first page of an Owner directory or NFT Offer directory has an ID that is the [SHA-512Half][] of the following values, concatenated in order: diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md b/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md index a6aca8706b1..f0663d19e5b 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md @@ -9,7 +9,7 @@ labels: An `Escrow` ledger entry represents an [escrow](../../../../concepts/payment-types/escrow.md), which holds XRP until specific conditions are met. You can create an escrow by sending an [EscrowCreate transaction][]. -_(Added by the [Escrow amendment][].)_ +{% amendment-disclaimer name="Escrow" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md b/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md index acd00fb6854..ec08f202d62 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md @@ -55,8 +55,8 @@ The fields of the `FeeSettings` ledger entry depend on whether the [XRPFees amen | `BaseFeeDrops` | String | Amount | Yes | The [transaction cost](../../../../concepts/transactions/transaction-cost.md) of the "reference transaction" in drops of XRP. | | `ReserveBaseDrops` | String | Amount | Yes | The [base reserve](../../../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve) for an account in the XRP Ledger, as drops of XRP. | | `ReserveIncrementDrops` | String | Amount | Yes | The incremental [owner reserve](../../../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve) for owning objects, as drops of XRP. | -| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | {% /tab %} {% tab label="Legacy Format" %} @@ -66,8 +66,8 @@ The fields of the `FeeSettings` ledger entry depend on whether the [XRPFees amen | `ReferenceFeeUnits` | Number | UInt32 | Yes | The `BaseFee` translated into "fee units". | | `ReserveBase` | Number | UInt32 | Yes | The [base reserve](../../../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve) for an account in the XRP Ledger, as drops of XRP. | | `ReserveIncrement` | Number | UInt32 | Yes | The incremental [owner reserve](../../../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve) for owning objects, as drops of XRP. | -| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | {% admonition type="danger" name="Warning" %}The JSON format for this ledger entry type is unusual. The `BaseFee`, `ReserveBase`, and `ReserveIncrement` indicate drops of XRP but ***not*** in the usual format for [specifying XRP][Currency Amount].{% /admonition %} diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md b/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md index 6bf2e647a80..df84be00b57 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md @@ -33,7 +33,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e | `Account` | String - [Address][] | AccountID | Yes | The owner (holder) of these MPTs. | | `MPTokenIssuanceID` | String - Hexadecimal | UInt192 | Yes | The `MPTokenIssuance` identifier. | | `MPTAmount` | String - Number | UInt64 | Yes | The amount of tokens currently held by the owner. The minimum is 0 and the maximum is 263-1. | -| `LockedAmount` | String - Number | UInt64 | No | The amount of tokens currently locked up (for example, in escrow or payment channels). _(Requires the [TokenEscrow amendment][] {% not-enabled /%}.)_ | +| `LockedAmount` | String - Number | UInt64 | No | The amount of tokens currently locked up (for example, in escrow). {% amendment-disclaimer name="TokenEscrow" /%} | | `PreviousTxnID` | String - [Hash][] | UInt256 | Yes | The identifying hash of the transaction that most recently modified this entry. | | `PreviousTxnLgrSeq` | Number | UInt32 | Yes | The sequence of the ledger that contains the transaction that most recently modified this object. | | `OwnerNode` | String | UInt64 | Yes | A hint indicating which page of the owner directory links to this entry, in case the directory consists of multiple pages. | diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md index 6ad068e2599..2110d24ab54 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md @@ -7,7 +7,7 @@ labels: # NegativeUNL [[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L85-L91 "Source") -_(Added by the [NegativeUNL amendment][].)_ +{% amendment-disclaimer name="NegativeUNL" /%} The `NegativeUNL` ledger entry type contains the current status of the [Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md), a list of trusted validators currently believed to be offline. @@ -41,8 +41,8 @@ In addition to the [common fields](../common-fields.md), the {% code-page-name / |:----------------------|:----------|:------------------|:----------|:---------------------| | `DisabledValidators` | Array | Array | No | A list of `DisabledValidator` objects (see below), each representing a trusted validator that is currently disabled. | | `LedgerEntryType` | String | UInt16 | Yes | The value `0x004E`, mapped to the string `NegativeUNL`, indicates that this entry is the Negative UNL. | -| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | -| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. _(Added by the [fixPreviousTxnID amendment][].)_ | +| `PreviousTxnID` | String | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | Number | UInt32 | No | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} | | `ValidatorToDisable` | String | Blob | No | The public key of a trusted validator that is scheduled to be disabled in the next flag ledger. | | `ValidatorToReEnable` | String | Blob | No | The public key of a trusted validator in the Negative UNL that is scheduled to be re-enabled in the next flag ledger. | diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md index fb4b57045e8..802fd5cc27f 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md @@ -9,7 +9,7 @@ labels: An `NFTokenOffer` entry represents an offer to buy, sell or transfer an [NFT](../../../../concepts/tokens/nfts/index.md). You can create an NFT buy or sell offer by sending an [NFTokenCreateOffer transaction][]. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md index 4be17ab6a7d..dfd50d830c4 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md @@ -9,7 +9,7 @@ labels: An `NFTokenPage` entry represents a collection of [NFTs](../../../../concepts/tokens/nfts/index.md) owned by the same account. An account can have multiple `NFTokenPage` entries, which form a doubly linked list. NFT directories are automatically updated when an account mints, burns, buys, or sells NFTs. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/offer.md b/docs/references/protocol/ledger-data/ledger-entry-types/offer.md index 88e09e6f23d..3b1dad803ea 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/offer.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/offer.md @@ -42,10 +42,10 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e | Name | JSON Type | [Internal Type][] | Required? | Description | |:--------------------|:---------------------|:------------------|:----------|:------------| | `Account` | String - [Address][] | AccountID | Yes | The account that owns this offer. | -| `AdditionalBooks` | Array | Array | No | A list of additional offer directories that link to this offer. This field is only present if this is a hybrid offer in a [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). The array always contains exactly 1 entry. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `AdditionalBooks` | Array | Array | No | A list of additional offer directories that link to this offer. This field is only present if this is a hybrid offer in a [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). The array always contains exactly 1 entry. {% amendment-disclaimer name="PermissionedDEX" /%} | | `BookDirectory` | String - [Hash][] | UInt256 | Yes | The ID of the [offer directory](directorynode.md) that links to this offer. | | `BookNode` | String | UInt64 | Yes | A hint indicating which page of the offer directory links to this entry, in case the directory consists of multiple pages. | -| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If present, this offer belongs to the corresponding [Permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If present, this offer belongs to the corresponding [Permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md). {% amendment-disclaimer name="PermissionedDEX" /%} | | `Expiration` | Number | UInt32 | No | Indicates the time after which this offer is considered unfunded. See [Specifying Time][] for details. | | `LedgerEntryType` | String | UInt16 | Yes | The value `0x006F`, mapped to the string `Offer`, indicates that this is an offer entry. | | `OwnerNode` | String | UInt64 | Yes | A hint indicating which page of the owner directory links to this entry, in case the directory consists of multiple pages. | @@ -63,7 +63,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e |--------------|--------------|---------------|-------------|------------------------| | `lsfPassive` | `0x00010000` | 65536 | `tfPassive` | The offer was placed as passive. This has no effect after the offer is placed into the ledger. | | `lsfSell` | `0x00020000` | 131072 | `tfSell` | The offer was placed as a sell offer. This has no effect after the offer is placed in the ledger, because `tfSell` only matters if you get a better rate than you asked for, which can only happen when the offer is initially placed. | -| `lsfHybrid` | `0x00040000` | 262144 | `tfHybrid` | The offer was placed as a hybrid offer, which means it is listed in a [permissioned DEX](/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md) and the open DEX. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `lsfHybrid` | `0x00040000` | 262144 | `tfHybrid` | The offer was placed as a hybrid offer, which means it is listed in a [permissioned DEX](/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md) and the open DEX. {% amendment-disclaimer name="PermissionedDEX" /%} | ## {% $frontmatter.seo.title %} Reserve diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md b/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md index f1ad4788be4..ce456700aac 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md @@ -9,7 +9,7 @@ labels: An `Oracle` ledger entry holds data associated with a single [price oracle](../../../../concepts/decentralized-storage/price-oracles.md), which can store information on up to 10 asset pairs. You can create or modify a price oracle with an [OracleSet transaction][]. -_(Added by the [PriceOracle amendment][])_ +{% amendment-disclaimer name="PriceOracle" /%} ## Example Oracle JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md b/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md index 123ea3e6b02..5b0d1260417 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md @@ -9,7 +9,7 @@ labels: A `PayChannel` entry represents a [payment channel](../../../../concepts/payment-types/payment-channels.md). You can create a payment channel with a [PaymentChannelCreate transaction][]. -_(Added by the [PayChan amendment][].)_ +{% amendment-disclaimer name="PayChan" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md b/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md index 86e017078c4..9a9d482ead8 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md @@ -11,7 +11,7 @@ status: not_enabled A `PermissionedDomain` ledger entry describes a single [permissioned domain][] instance. You can create a permissioned domain by sending a [PermissionedDomainSet transaction][]. -_(Requires the [PermissionedDomains amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="PermissionedDomains" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md index 9c27354fe99..de2c832b003 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md @@ -9,7 +9,7 @@ labels: A `SignerList` entry represents a list of parties that, as a group, are authorized to sign a transaction in place of an individual account by [multi-signing](../../../../concepts/accounts/multi-signing.md). You can create, replace, or remove a signer list using a [SignerListSet transaction][]. -_(Added by the [MultiSign amendment][].)_ +{% amendment-disclaimer name="MultiSign" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -70,13 +70,13 @@ Each member of the `SignerEntries` field is an object that describes that signer |:----------------|:----------|:--------------|:-------------------------------| | `Account` | String | AccountID | An XRP Ledger address whose signature contributes to the multi-signature. It does not need to be a funded address in the ledger. | | `SignerWeight` | Number | UInt16 | The weight of a signature from this signer. A multi-signature is only valid if the sum weight of the signatures provided meets or exceeds the signer list's `SignerQuorum` value. | -| `WalletLocator` | String | UInt256 | _(Optional)_ Arbitrary hexadecimal data. This can be used to identify the signer or for other, related purposes. _(Added by the [ExpandedSignerList amendment][].)_ | +| `WalletLocator` | String | UInt256 | _(Optional)_ Arbitrary hexadecimal data. This can be used to identify the signer or for other, related purposes. {% amendment-disclaimer name="ExpandedSignerList" /%} | When processing a multi-signed transaction, the server looks up the `Account` values with respect to the ledger at the time of transaction execution. If the address _does not_ correspond to a funded [AccountRoot ledger entry](accountroot.md), then only the [master private key](../../../../concepts/accounts/cryptographic-keys.md) associated with that address can be used to produce a valid signature. If the account _does_ exist in the ledger, then it depends on the state of that account. If the account has a Regular Key configured, the Regular Key can be used. The account's master key can only be used if it is not disabled. A multi-signature cannot be used as part of another multi-signature. ## {% $frontmatter.seo.title %} Flags -_(Added by the [MultiSignReserve amendment][].)_ +{% amendment-disclaimer name="MultiSignReserve" /%} SignerList entries can have the following value in the `Flags` field: diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md index 5f8b3ea3042..e5ae20f65e6 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md @@ -9,7 +9,7 @@ labels: A `Ticket` entry type represents a [Ticket](../../../../concepts/accounts/tickets.md), which tracks an account [sequence number][Sequence Number] that has been set aside for future use. You can create new tickets with a [TicketCreate transaction][]. -_(Added by the [TicketBatch amendment][].)_ +{% amendment-disclaimer name="TicketBatch" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md index c825a829f8e..01d3bc812bb 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md @@ -14,7 +14,7 @@ The `XChainOwnedClaimID` entry must be acquired on the destination chain before You can create a new `XChainOwnedClaimID` by sending an [XChainCreateClaimID transaction][]. An `XChainOwnedClaimID` is destroyed when the funds are successfully claimed on the destination chain. -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainOwnedClaimID JSON diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md index 27631b93283..afa8ed17c57 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md @@ -14,7 +14,7 @@ You can create a new `XChainOwnedCreateAccountClaimID` entry by sending an [XCha An `XChainOwnedCreateAccountClaimID` ledger entry is destroyed when all the attestations have been received and the funds have transferred to the new account. -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainOwnedCreateAccountClaimID JSON diff --git a/docs/references/protocol/transactions/common-fields.md b/docs/references/protocol/transactions/common-fields.md index aa8dece2a66..1afa546ae1b 100644 --- a/docs/references/protocol/transactions/common-fields.md +++ b/docs/references/protocol/transactions/common-fields.md @@ -13,9 +13,9 @@ Every transaction has the same set of common fields, plus additional fields base | `Account` | String - [Address][] | AccountID | Yes | The [account](../../../concepts/accounts/index.md) that initiated the transaction. | | `TransactionType` | String | UInt16 | Yes | The type of transaction. Valid [transaction types](types/index.md) include: `Payment`, `OfferCreate`, `TrustSet`, and many others. | | `Fee` | String - Number | Amount | Yes; [auto-fillable][] | Integer amount of XRP, in drops, to be destroyed as a cost for sending this transaction. Some transaction types have different minimum requirements. See [Transaction Cost][] for details. | -| `Sequence` | Number | UInt32 | Yes; [auto-fillable][] | The [sequence number](../data-types/basic-data-types.md#account-sequence) of the account sending the transaction. A transaction is only valid if the `Sequence` number is exactly 1 greater than the previous transaction from the same account. The special case `0` means the transaction is using a [Ticket](../../../concepts/accounts/tickets.md) instead _(Added by the [TicketBatch amendment][].)_. | +| `Sequence` | Number | UInt32 | Yes; [auto-fillable][] | The [sequence number](../data-types/basic-data-types.md#account-sequence) of the account sending the transaction. A transaction is only valid if the `Sequence` number is exactly 1 greater than the previous transaction from the same account. The special case `0` means the transaction is using a [Ticket](../../../concepts/accounts/tickets.md) instead {% amendment-disclaimer name="TicketBatch" /%}. | | [`AccountTxnID`](#accounttxnid) | String - [Hash][] | UInt256 | No | Hash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash. | -| [`Delegate`](#delegate) | String - [Address][] | AccountID | No | A delegate account that is sending the transaction on behalf of the `Account`. _(Requires the [PermissionDelegation amendment][] {% not-enabled /%})_ | +| [`Delegate`](#delegate) | String - [Address][] | AccountID | No | A delegate account that is sending the transaction on behalf of the `Account`. {% amendment-disclaimer name="PermissionDelegation" /%} | | [`Flags`](#flags-field) | Number | UInt32 | No | Set of bit-flags for this transaction. | | `LastLedgerSequence` | Number | UInt32 | No; [auto-fillable][] | Highest ledger index this transaction can appear in. Specifying this field places a strict upper limit on how long the transaction can wait to be validated or rejected. See [Reliable Transaction Submission](../../../concepts/transactions/reliable-transaction-submission.md) for more details. | | [`Memos`](#memos-field) | Array of Objects | Array | No | Additional arbitrary information attached to this transaction. | @@ -67,7 +67,7 @@ If the `Delegate` field is provided, this transaction is being sent by a differe Sending a transaction this way is only possible if the delegating account has granted the appropriate transaction permissions to the delegate account. For more information, see [Permission Delegation](/docs/concepts/accounts/permission-delegation.md). -_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="PermissionDelegation" /%} ## Flags Field diff --git a/docs/references/protocol/transactions/metadata.md b/docs/references/protocol/transactions/metadata.md index 6ba3dda528e..34e882d5227 100644 --- a/docs/references/protocol/transactions/metadata.md +++ b/docs/references/protocol/transactions/metadata.md @@ -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 [MPTokensV1 amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="MPTokensV1" /%} ### 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`. diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md index 4f92cec549c..8f11ec84591 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md @@ -9,7 +9,7 @@ labels: # UNLModify [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") -_(Added by the [NegativeUNL amendment][].)_ +{% amendment-disclaimer name="NegativeUNL" /%} A `UNLModify` [pseudo-transaction](pseudo-transaction-types.md) marks a change to the [Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md), indicating that a trusted validator has gone offline or come back online. diff --git a/docs/references/protocol/transactions/transaction-results/tec-codes.md b/docs/references/protocol/transactions/transaction-results/tec-codes.md index 38073cabdeb..eb030b1cf90 100644 --- a/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -17,20 +17,20 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti | Code | Value | Explanation | |:---------------------------|:------|:----------------------------------------| -| `tecAMM_ACCOUNT` | 168 | The transaction failed because the operation is not allowed on Automated Market Maker (AMM) accounts. _(Added by the [AMM amendment][])_ | -| `tecAMM_UNFUNDED` | 162 | The [AMMCreate transaction][] failed because the sender does not have enough of the specified assets to fund it. _(Added by the [AMM amendment][])_ | -| `tecAMM_BALANCE` | 163 | The [AMMDeposit][] or [AMMWithdraw][] transaction failed because either the AMM or the user does not hold enough of one of the specified assets. (For example, you tried to withdraw more than the AMM holds.) _(Added by the [AMM amendment][])_ | -| `tecAMM_EMPTY` | 166 | The AMM-related transaction failed because the AMM has no assets in its pool. In this state, you can only delete the AMM or fund it with a new deposit. _(Added by the [AMM amendment][])_ | -| `tecAMM_FAILED` | 164 | The AMM-related transaction failed. For [AMMDeposit][] or [AMMWithdraw][] this could be because the sender does not have enough of the specified assets, or the transaction requested an effective price that isn't possible with the available amounts. For [AMMBid][] this could be because the account does not have enough to win the bid or needs more than their specified maximum bid. For [AMMVote][], this could be because there are already too many votes from other accounts that hold more of this AMM's LP Tokens. _(Added by the [AMM amendment][])_ | -| `tecAMM_INVALID_TOKENS` | 165 | The AMM-related transaction failed due to insufficient LP Tokens or problems with rounding; for example, depositing a very small amount of assets could fail if the amount of LP Tokens to be returned rounds down to zero. _(Added by the [AMM amendment][])_ | -| `tecAMM_NOT_EMPTY` | 167 | The transaction was meant to operate on an AMM with empty asset pools, but the specified AMM currently holds assets. _(Added by the [AMM amendment][])_ | -| `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | The transaction tried to accept an offer that was placed by the same account to buy or sell a [non-fungible token](../../../../concepts/tokens/nfts/index.md). _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecAMM_ACCOUNT` | 168 | The transaction failed because the operation is not allowed on Automated Market Maker (AMM) accounts. {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_UNFUNDED` | 162 | The [AMMCreate transaction][] failed because the sender does not have enough of the specified assets to fund it. {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_BALANCE` | 163 | The [AMMDeposit][] or [AMMWithdraw][] transaction failed because either the AMM or the user does not hold enough of one of the specified assets. (For example, you tried to withdraw more than the AMM holds.) {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_EMPTY` | 166 | The AMM-related transaction failed because the AMM has no assets in its pool. In this state, you can only delete the AMM or fund it with a new deposit. {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_FAILED` | 164 | The AMM-related transaction failed. For [AMMDeposit][] or [AMMWithdraw][] this could be because the sender does not have enough of the specified assets, or the transaction requested an effective price that isn't possible with the available amounts. For [AMMBid][] this could be because the account does not have enough to win the bid or needs more than their specified maximum bid. For [AMMVote][], this could be because there are already too many votes from other accounts that hold more of this AMM's LP Tokens. {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_INVALID_TOKENS` | 165 | The AMM-related transaction failed due to insufficient LP Tokens or problems with rounding; for example, depositing a very small amount of assets could fail if the amount of LP Tokens to be returned rounds down to zero. {% amendment-disclaimer name="AMM" /%} | +| `tecAMM_NOT_EMPTY` | 167 | The transaction was meant to operate on an AMM with empty asset pools, but the specified AMM currently holds assets. {% amendment-disclaimer name="AMM" /%} | +| `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | The transaction tried to accept an offer that was placed by the same account to buy or sell a [non-fungible token](../../../../concepts/tokens/nfts/index.md). {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecCLAIM` | 100 | Unspecified failure, with transaction cost destroyed. | | `tecCRYPTOCONDITION_ERROR` | 146 | This [EscrowCreate][] or [EscrowFinish][] transaction contained a malformed or mismatched crypto-condition. | | `tecDIR_FULL` | 121 | The transaction tried to add an object (such as a trust line, Check, Escrow, or Payment Channel) to an account's owner directory, but that account cannot own any more objects in the ledger. | | `tecDUPLICATE` | 149 | The transaction tried to create an object (such as a [DepositPreauth][] authorization) that already exists. | | `tecDST_TAG_NEEDED` | 143 | The [Payment transaction][] omitted a [destination tag](../../../../concepts/transactions/source-and-destination-tags.md), but the destination account has the `lsfRequireDestTag` flag enabled. | -| `tecEMPTY_DID` | 187 | The transaction tried to create a [DID entry][] with no contents. A DID must not be empty. _(Added by the [DID amendment][] {% not-enabled /%})_ | +| `tecEMPTY_DID` | 187 | The transaction tried to create a [DID entry][] with no contents. A DID must not be empty. {% amendment-disclaimer name="DID" /%} | | `tecEXPIRED` | 148 | The transaction tried to create an object (such as an Offer or a Check) whose provided Expiration time has already passed. | | `tecFAILED_PROCESSING` | 105 | An unspecified error occurred when processing the transaction. | | `tecFROZEN` | 137 | The [OfferCreate transaction][] failed because one or both of the assets involved are subject to a [global freeze](../../../../concepts/tokens/fungible-tokens/freezes.md). | @@ -38,17 +38,17 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti | `tecINSUF_RESERVE_LINE` | 122 | The transaction failed because the sending account does not have enough XRP to create a new trust line. (See: [Reserves](../../../../concepts/accounts/reserves.md)) This error occurs when the counterparty already has a trust line in a non-default state to the sending account for the same currency. (See `tecNO_LINE_INSUF_RESERVE` for the other case.) | | `tecINSUF_RESERVE_OFFER` | 123 | The transaction failed because the sending account does not have enough XRP to create a new Offer. (See: [Reserves](../../../../concepts/accounts/reserves.md)) | | `tecINSUFF_FEE` | 136 | The transaction failed because the sending account does not have enough XRP to pay the [transaction cost](../../../../concepts/transactions/transaction-cost.md) that it specified. (In this case, the transaction processing destroys all of the sender's XRP even though that amount is lower than the specified transaction cost.) This result only occurs if the account's balance decreases _after_ this transaction has been distributed to enough of the network to be included in a consensus set. Otherwise, the transaction fails with [`terINSUF_FEE_B`](ter-codes.md) before being distributed. | -| `tecINSUFFICIENT_FUNDS` | 158 | One of the accounts involved does not hold enough of a necessary asset. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | -| `tecINSUFFICIENT_PAYMENT` | 161 | The amount specified is not enough to pay all fees involved in the transaction. For example, when trading a non-fungible token, the buy amount may not be enough to pay both the broker fee and the sell amount. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecINSUFFICIENT_FUNDS` | 158 | One of the accounts involved does not hold enough of a necessary asset. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | +| `tecINSUFFICIENT_PAYMENT` | 161 | The amount specified is not enough to pay all fees involved in the transaction. For example, when trading a non-fungible token, the buy amount may not be enough to pay both the broker fee and the sell amount. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecINSUFFICIENT_RESERVE` | 141 | The transaction would increase the [reserve requirement](../../../../concepts/accounts/reserves.md) higher than the sending account's balance. [SignerListSet][], [PaymentChannelCreate][], [PaymentChannelFund][], and [EscrowCreate][] can return this error code. See [Signer Lists and Reserves](../../ledger-data/ledger-entry-types/signerlist.md#signer-lists-and-reserves) for more information. | | `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | -| `tecINVALID_UPDATE_TIME` | 188 | The [OracleSet transaction][] failed because the `LastUpdateTime` is invalid. This can occur when the time is more than 300 seconds before or after the ledger close time, or when updating an existing oracle, the new `LastUpdateTime` is not greater than the previous value. _(Added by the [PriceOracle amendment][])_ | -| `tecINVARIANT_FAILED` | 147 | An invariant check failed when trying to execute this transaction. Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | -| `tecKILLED` | 150 | The [OfferCreate transaction][] specified the `tfFillOrKill` flag and could not be filled, so it was killed. _(Added by the [fix1578 amendment][].)_ | -| `tecMAX_SEQUENCE_REACHED` | 153 | A sequence number field is already at its maximum. This includes the `MintedNFTokens` field. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecINVALID_UPDATE_TIME` | 188 | The [OracleSet transaction][] failed because the `LastUpdateTime` is invalid. This can occur when the time is more than 300 seconds before or after the ledger close time, or when updating an existing oracle, the new `LastUpdateTime` is not greater than the previous value. {% amendment-disclaimer name="PriceOracle" /%} | +| `tecINVARIANT_FAILED` | 147 | An invariant check failed when trying to execute this transaction. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). {% amendment-disclaimer name="EnforceInvariants" /%} | +| `tecKILLED` | 150 | The [OfferCreate transaction][] specified the `tfFillOrKill` flag and could not be filled, so it was killed. {% amendment-disclaimer name="fix1578" /%} | +| `tecMAX_SEQUENCE_REACHED` | 153 | A sequence number field is already at its maximum. This includes the `MintedNFTokens` field. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNEED_MASTER_KEY` | 142 | This transaction tried to cause changes that require the master key, such as [disabling the master key or giving up the ability to freeze balances](../types/accountset.md#accountset-flags). | -| `tecNFTOKEN_BUY_SELL_MISMATCH` | 155 | The [NFTokenAcceptOffer transaction][] attempted to match incompatible offers to buy and sell a non-fungible token. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | -| `tecNFTOKEN_OFFER_TYPE_MISMATCH` | 156 | One or more of the offers specified in the transaction was not the right type of offer. (For example, a buy offer was specified in the `NFTokenSellOffer` field.) _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecNFTOKEN_BUY_SELL_MISMATCH` | 155 | The [NFTokenAcceptOffer transaction][] attempted to match incompatible offers to buy and sell a non-fungible token. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | +| `tecNFTOKEN_OFFER_TYPE_MISMATCH` | 156 | One or more of the offers specified in the transaction was not the right type of offer. (For example, a buy offer was specified in the `NFTokenSellOffer` field.) {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNO_ALTERNATIVE_KEY` | 130 | The transaction tried to remove the only available method of [authorizing transactions](../../../../concepts/transactions/index.md#authorizing-transactions). This could be a [SetRegularKey transaction][] to remove the regular key, a [SignerListSet transaction][] to delete a SignerList, or an [AccountSet transaction][] to disable the master key. (Prior to `rippled` 0.30.0, this was called `tecMASTER_DISABLED`.) | | `tecNO_AUTH` | 134 | The transaction failed because it needs to add a balance on a trust line to an account with the `lsfRequireAuth` flag enabled, and that trust line has not been authorized. If the trust line does not exist at all, `tecNO_LINE` occurs instead. | | `tecNO_DST` | 124 | The account on the receiving end of the transaction does not exist. This includes Payment and TrustSet transaction types. (It could be created if it received enough XRP.) | @@ -60,9 +60,9 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti | `tecNO_LINE_REDUNDANT` | 127 | The transaction failed because it tried to set a trust line to its default state, but the trust line did not exist. | | `tecNO_PERMISSION` | 139 | The sender does not have permission to do this operation. For example, the [EscrowFinish transaction][] tried to release a held payment before its `FinishAfter` time, someone tried to use [PaymentChannelFund][] on a channel the sender does not own, or a [Payment][] tried to deliver funds to an account with the "DepositAuth" flag enabled. | | `tecNO_REGULAR_KEY` | 131 | The [AccountSet transaction][] tried to disable the master key, but the account does not have another way to [authorize transactions](../../../../concepts/transactions/index.md#authorizing-transactions). If [multi-signing](../../../../concepts/accounts/multi-signing.md) is enabled, this code is deprecated and `tecNO_ALTERNATIVE_KEY` is used instead. | -| `tecNO_SUITABLE_NFTOKEN_PAGE` | 154 | The transaction tried to mint or acquire a non-fungible token but the account receiving the `NFToken` does not have a directory page that can hold it. This situation is rare. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecNO_SUITABLE_NFTOKEN_PAGE` | 154 | The transaction tried to mint or acquire a non-fungible token but the account receiving the `NFToken` does not have a directory page that can hold it. This situation is rare. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNO_TARGET` | 138 | The transaction referenced an Escrow or PayChannel ledger object that doesn't exist, either because it never existed or it has already been deleted. (For example, another [EscrowFinish transaction][] has already executed the held payment.) Alternatively, the destination account has `asfDisallowXRP` set so it cannot be the destination of this [PaymentChannelCreate][] or [EscrowCreate][] transaction. | -| `tecOBJECT_NOT_FOUND` | 160 | One of the objects specified by this transaction did not exist in the ledger. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tecOBJECT_NOT_FOUND` | 160 | One of the objects specified by this transaction did not exist in the ledger. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecOVERSIZE` | 145 | This transaction could not be processed, because the server created an excessively large amount of [metadata](../metadata.md) when it tried to apply the transaction. | | `tecOWNERS` | 132 | The transaction cannot succeed because the sender already owns objects in the ledger. For example, an account cannot enable the [`lsfRequireAuth`](../types/accountset.md#accountset-flags) flag if it has any trust lines or available offers. | | `tecPATH_DRY` | 128 | The transaction failed because the provided [paths](../../../../concepts/tokens/fungible-tokens/paths.md) did not have enough liquidity to send anything at all. This could mean that the source and destination accounts are not linked by [trust lines](../../../../concepts/tokens/fungible-tokens/index.md). | diff --git a/docs/references/protocol/transactions/transaction-results/tef-codes.md b/docs/references/protocol/transactions/transaction-results/tef-codes.md index 1ac27f43f44..38b228334c7 100644 --- a/docs/references/protocol/transactions/transaction-results/tef-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tef-codes.md @@ -1,6 +1,4 @@ --- -html: tef-codes.html -parent: transaction-results.html seo: description: tef codes indicate that the transaction failed and was not included in a ledger, but the transaction could have succeeded in some theoretical ledger. labels: @@ -26,10 +24,10 @@ These codes indicate that the transaction failed and was not included in a ledge | `tefEXCEPTION` | While processing the transaction, the server entered an unexpected state. This may be caused by unexpected inputs, for example if the binary data for the transaction is grossly malformed. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues) to get it fixed. | | `tefFAILURE` | Unspecified failure in applying the transaction. | | `tefINTERNAL` | When trying to apply the transaction, the server entered an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues) to get it fixed. | -| `tefINVARIANT_FAILED` | An invariant check failed when trying to claim the [transaction cost](../../../../concepts/transactions/transaction-cost.md). Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | +| `tefINVARIANT_FAILED` | An invariant check failed when trying to claim the [transaction cost](../../../../concepts/transactions/transaction-cost.md). If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). {% amendment-disclaimer name="EnfroceInvariants" /%} | | `tefMASTER_DISABLED` | The transaction was signed with the account's master key, but the account has the `lsfDisableMaster` field set. | | `tefMAX_LEDGER` | The transaction included a [`LastLedgerSequence`](../../../../concepts/transactions/reliable-transaction-submission.md#lastledgersequence) parameter, but the current ledger's sequence number is already higher than the specified value. | -| `tefNFTOKEN_IS_NOT_TRANSFERABLE` | The transaction attempted to send a [non-fungible token](../../../../concepts/tokens/nfts/index.md) to another account, but the `NFToken` has the `lsfTransferable` flag disabled and the transfer would not be to or from the issuer. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `tefNFTOKEN_IS_NOT_TRANSFERABLE` | The transaction attempted to send a [non-fungible token](../../../../concepts/tokens/nfts/index.md) to another account, but the `NFToken` has the `lsfTransferable` flag disabled and the transfer would not be to or from the issuer. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tefNO_AUTH_REQUIRED` | The [TrustSet transaction][] tried to mark a trust line as authorized, but the `lsfRequireAuth` flag is not enabled for the corresponding account, so authorization is not necessary. | | `tefNO_TICKET` | The transaction attempted to use a [Ticket](../../../../concepts/accounts/tickets.md), but the specified `TicketSequence` number does not exist in the ledger, and cannot be created in the future because it is earlier than the sender's current sequence number. | | `tefNOT_MULTI_SIGNING` | The transaction was [multi-signed](../../../../concepts/accounts/multi-signing.md), but the sending account has no SignerList defined. | diff --git a/docs/references/protocol/transactions/transaction-results/tem-codes.md b/docs/references/protocol/transactions/transaction-results/tem-codes.md index 9e61b7815f2..93d9bbedf84 100644 --- a/docs/references/protocol/transactions/transaction-results/tem-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tem-codes.md @@ -1,10 +1,8 @@ --- -html: tem-codes.html -parent: transaction-results.html seo: description: tem codes indicate that the transaction was malformed, and cannot succeed according to the XRP Ledger protocol. labels: - - Transaction Sending + - Transaction Sending --- # tem Codes @@ -14,7 +12,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco | Code | Explanation | |:------------------------------|:----------------------------------------------| -| `temBAD_AMM_TOKENS` | The transaction incorrectly specified one or more assets. For example, the asset's issuer does not match the corresponding asset in the AMM's pool, or the transaction specified the same asset twice. _(Added by the [AMM amendment][])_ | +| `temBAD_AMM_TOKENS` | The transaction incorrectly specified one or more assets. For example, the asset's issuer does not match the corresponding asset in the AMM's pool, or the transaction specified the same asset twice. {% amendment-disclaimer name="AMM" /%} | | `temBAD_AMOUNT` | An amount specified by the transaction (for example the destination `Amount` or `SendMax` values of a [Payment][]) was invalid, possibly because it was a negative number. | | `temBAD_AUTH_MASTER` | The key used to sign this transaction does not match the master key for the account sending it, and the account does not have a [Regular Key](../../../../concepts/accounts/cryptographic-keys.md) set. | | `temBAD_CURRENCY` | The transaction improperly specified a currency field. See [Specifying Currency Amounts][Currency Amount] for the correct format. | @@ -22,7 +20,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco | `temBAD_FEE` | The transaction improperly specified its `Fee` value, for example by listing a non-XRP currency or some negative amount of XRP. | | `temBAD_ISSUER` | The transaction improperly specified the `issuer` field of some currency included in the request. | | `temBAD_LIMIT` | The [TrustSet transaction][] improperly specified the `LimitAmount` value of a trust line. | -| `temBAD_NFTOKEN_TRANSFER_FEE` | The [NFTokenMint transaction][] improperly specified the `TransferFee` field of the transaction. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `temBAD_NFTOKEN_TRANSFER_FEE` | The [NFTokenMint transaction][] improperly specified the `TransferFee` field of the transaction. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `temBAD_OFFER` | The [OfferCreate transaction][] specifies an invalid offer, such as offering to trade XRP for itself, or offering a negative amount. | | `temBAD_PATH` | The [Payment transaction][] specifies one or more [Paths](../../../../concepts/tokens/fungible-tokens/paths.md) improperly, for example including an issuer for XRP, or specifying an account differently. | | `temBAD_PATH_LOOP` | One of the [Paths](../../../../concepts/tokens/fungible-tokens/paths.md) in the [Payment transaction][] was flagged as a loop, so it cannot be processed in a bounded amount of time. | @@ -45,7 +43,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco | `temREDUNDANT` | The transaction would do nothing; for example, it is sending a payment directly to the sending account, or creating an offer to buy and sell the same currency from the same issuer. | | `temREDUNDANT_SEND_MAX` | {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.28.0" %}Removed in: rippled 0.28.0{% /badge %} | | `temRIPPLE_EMPTY` | The [Payment transaction][] includes an empty `Paths` field, but paths are necessary to complete this payment. | -| `temSEQ_AND_TICKET` | The transaction contains both a `TicketSequence` field and a non-zero `Sequence` value. A transaction cannot include both. _(Added by the [TicketBatch amendment][].)_ | +| `temSEQ_AND_TICKET` | The transaction contains both a `TicketSequence` field and a non-zero `Sequence` value. A transaction cannot include both. {% amendment-disclaimer name="TicketBatch" /%} | | `temBAD_WEIGHT` | The [SignerListSet transaction][] includes a `SignerWeight` that is invalid, for example a zero or negative value. | | `temBAD_SIGNER` | The [SignerListSet transaction][] includes a signer who is invalid. For example, there may be duplicate entries, or the owner of the SignerList may also be a member. | | `temBAD_QUORUM` | The [SignerListSet transaction][] has an invalid `SignerQuorum` value. Either the value is not greater than zero, or it is more than the sum of all signers in the list. | diff --git a/docs/references/protocol/transactions/transaction-results/ter-codes.md b/docs/references/protocol/transactions/transaction-results/ter-codes.md index 02851e70c36..450433e54d9 100644 --- a/docs/references/protocol/transactions/transaction-results/ter-codes.md +++ b/docs/references/protocol/transactions/transaction-results/ter-codes.md @@ -20,7 +20,7 @@ Transactions with `ter` codes have not been applied to the current ledger and ha | `terINSUF_FEE_B` | The account sending the transaction does not have enough XRP to pay the `Fee` specified in the transaction. | | `terLAST` | Used internally only. This code should never be returned. | | `terNO_ACCOUNT` | The address sending the transaction is not funded in the ledger (yet). | -| `terNO_AMM` | The AMM-related transaction specifies an asset pair that does not currently have an AMM instance. _(Added by the [AMM amendment][])_ | +| `terNO_AMM` | The AMM-related transaction specifies an asset pair that does not currently have an AMM instance. {% amendment-disclaimer name="AMM" /%} | | `terNO_AUTH` | The transaction would involve adding currency issued by an account with `lsfRequireAuth` enabled to a trust line that is not authorized. For example, you placed an offer to buy a currency you aren't authorized to hold. | | `terNO_LINE` | Used internally only. This code should never be returned. | | `terNO_RIPPLE` | The transaction can't succeed because of [rippling settings](/docs/concepts/tokens/fungible-tokens/rippling/). For example, the transaction tried to create an AMM even though the issuer of at least one of the tokens has not enabled the Default Ripple flag. | diff --git a/docs/references/protocol/transactions/types/accountdelete.md b/docs/references/protocol/transactions/types/accountdelete.md index 4bba21456fc..11ed6d6fa4e 100644 --- a/docs/references/protocol/transactions/types/accountdelete.md +++ b/docs/references/protocol/transactions/types/accountdelete.md @@ -5,12 +5,11 @@ labels: - Accounts --- # AccountDelete - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") An AccountDelete transaction deletes an [account](../../ledger-data/ledger-entry-types/accountroot.md) and any objects it owns in the XRP Ledger, if possible, sending the account's remaining XRP to a specified destination account. See [Deleting Accounts](../../../../concepts/accounts/deleting-accounts.md) for the requirements to delete an account. -_(Added by the [DeletableAccounts amendment][].)_ +{% amendment-disclaimer name="DeletableAccounts" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/accountset.md b/docs/references/protocol/transactions/types/accountset.md index 5eff632559f..f4fce041db8 100644 --- a/docs/references/protocol/transactions/types/accountset.md +++ b/docs/references/protocol/transactions/types/accountset.md @@ -5,10 +5,9 @@ labels: - Accounts --- # AccountSet - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetAccount.cpp "Source") -An AccountSet transaction modifies the properties of an [account in the XRP Ledger](../../ledger-data/ledger-entry-types/accountroot.md). +Modify the settings or properties of an [account in the XRP Ledger](../../../../concepts/accounts/index.md). ## Example {% $frontmatter.seo.title %} JSON @@ -34,10 +33,10 @@ An AccountSet transaction modifies the properties of an [account in the XRP Ledg | [`Domain`](#domain) | String | Blob | The domain that owns this account, as a string of hex representing the ASCII for the domain in lowercase. [Cannot be more than 256 bytes in length.](https://github.com/XRPLF/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | | `EmailHash` | String | UInt128 | An arbitrary 128-bit value. Conventionally, clients treat this as the md5 hash of an email address to use for displaying a [Gravatar](http://en.gravatar.com/site/implement/hash/) image. | | `MessageKey` | String | Blob | Public key for sending encrypted messages to this account. To set the key, it must be exactly 33 bytes, with the first byte indicating the key type: `0x02` or `0x03` for secp256k1 keys, `0xED` for Ed25519 keys. To remove the key, use an empty value. | -| `NFTokenMinter` | String - [Address][] | AccountID | Another account that can [mint NFTokens for you](../../../../tutorials/javascript/nfts/assign-an-authorized-minter.md). _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `NFTokenMinter` | String - [Address][] | AccountID | Another account that can [mint NFTokens for you](../../../../tutorials/javascript/nfts/assign-an-authorized-minter.md). {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | [`SetFlag`](#accountset-flags) | Number | UInt32 | Integer flag to enable for this account. | | [`TransferRate`](#transferrate) | Number | UInt32 | The fee to charge when users transfer this account's tokens, represented as billionths of a unit. Cannot be more than `2000000000` or less than `1000000000`, except for the special case `0` meaning no fee. | -| [`TickSize`](../../../../concepts/tokens/decentralized-exchange/ticksize.md) | Number | UInt8 | _(Optional)_ Tick size to use for offers involving a currency issued by this address. The exchange rates of those offers is rounded to this many significant digits. Valid values are `3` to `15` inclusive, or `0` to disable. _(Added by the [TickSize amendment][])_ | +| [`TickSize`](../../../../concepts/tokens/decentralized-exchange/ticksize.md) | Number | UInt8 | _(Optional)_ Tick size to use for offers involving a currency issued by this address. The exchange rates of those offers is rounded to this many significant digits. Valid values are `3` to `15` inclusive, or `0` to disable. {% amendment-disclaimer name="TickSize" /%} | | `WalletLocator` | String | UInt256 | An arbitrary 256-bit value. If specified, the value is stored as part of the account but has no inherent meaning or requirements. | | `WalletSize` | Number | UInt32 | Not used. This field is valid in AccountSet transactions but does nothing. | @@ -74,14 +73,14 @@ The available AccountSet flags are: |:----------------------------------|:--------------|:--------------| | `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. | -| `asfAuthorizedNFTokenMinter` | 10 | Enable to allow another account to mint non-fungible tokens (NFTokens) on this account's behalf. Specify the authorized account in the `NFTokenMinter` field of the [AccountRoot](../../ledger-data/ledger-entry-types/accountroot.md) object. To remove an authorized minter, enable this flag and omit the `NFTokenMinter` field. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | +| `asfAuthorizedNFTokenMinter` | 10 | Enable to allow another account to mint non-fungible tokens (NFTokens) on this account's behalf. Specify the authorized account in the `NFTokenMinter` field of the [AccountRoot](../../ledger-data/ledger-entry-types/accountroot.md) object. To remove an authorized minter, enable this flag and omit the `NFTokenMinter` field. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `asfDefaultRipple` | 8 | Enable [rippling](../../../../concepts/tokens/fungible-tokens/rippling.md) on this account's trust lines by default. | -| `asfDepositAuth` | 9 | Enable [Deposit Authorization](../../../../concepts/accounts/depositauth.md) on this account. _(Added by the [DepositAuth amendment][].)_ | +| `asfDepositAuth` | 9 | Enable [Deposit Authorization](../../../../concepts/accounts/depositauth.md) on this account. {% amendment-disclaimer name="DepositAuth" /%} | | `asfDisableMaster` | 4 | Disallow use of the master key pair. Can only be enabled if the account has configured another way to sign transactions, such as a [Regular Key](../../../../concepts/accounts/cryptographic-keys.md) or a [Signer List](../../../../concepts/accounts/multi-signing.md). | -| `asfDisallowIncomingCheck` | 13 | Block incoming Checks. _(Requires the [DisallowIncoming amendment][].)_ | -| `asfDisallowIncomingNFTokenOffer` | 12 | Block incoming NFTokenOffers. _(Requires the [DisallowIncoming amendment][].)_ | -| `asfDisallowIncomingPayChan` | 14 | Block incoming Payment Channels. _(Requires the [DisallowIncoming amendment][].)_ | -| `asfDisallowIncomingTrustline` | 15 | Block incoming trust lines. _(Requires the [DisallowIncoming amendment][].)_ | +| `asfDisallowIncomingCheck` | 13 | Block incoming Checks. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingNFTokenOffer` | 12 | Block incoming NFTokenOffers. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingPayChan` | 14 | Block incoming Payment Channels. {% amendment-disclaimer name="DisallowIncoming" /%} | +| `asfDisallowIncomingTrustline` | 15 | Block incoming trust lines. {% amendment-disclaimer name="DisallowIncoming" /%} | | `asfDisallowXRP` | 3 | XRP should not be sent to this account. (Advisory; not enforced by the XRP Ledger protocol.) | | `asfGlobalFreeze` | 7 | [Freeze](../../../../concepts/tokens/fungible-tokens/freezes.md) all assets issued by this account. | | `asfNoFreeze` | 6 | Permanently give up the ability to [freeze individual trust lines or disable Global Freeze](../../../../concepts/tokens/fungible-tokens/freezes.md). This flag can never be disabled after being enabled. | diff --git a/docs/references/protocol/transactions/types/ammbid.md b/docs/references/protocol/transactions/types/ammbid.md index 723a0aa625f..01bde0e97d6 100644 --- a/docs/references/protocol/transactions/types/ammbid.md +++ b/docs/references/protocol/transactions/types/ammbid.md @@ -11,7 +11,7 @@ Bid on an [Automated Market Maker](../../../../concepts/tokens/decentralized-exc You bid using the AMM's LP Tokens; the amount of a winning bid is returned to the AMM, decreasing the outstanding balance of LP Tokens. -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammclawback.md b/docs/references/protocol/transactions/types/ammclawback.md index 43c63f4d827..fecfb8c0b5e 100644 --- a/docs/references/protocol/transactions/types/ammclawback.md +++ b/docs/references/protocol/transactions/types/ammclawback.md @@ -2,8 +2,8 @@ seo: description: Claw back tokens from a holder who has deposited your issued tokens into an Automated Market Maker pool. labels: - - AMM - - Tokens + - AMM + - Tokens --- # AMMClawback @@ -13,7 +13,7 @@ Claw back tokens from a holder who has deposited your issued tokens into an AMM Clawback is disabled by default. To use clawback, you must send an [AccountSet transaction][] to enable the **Allow Trust Line Clawback** setting. An issuer with any existing tokens cannot enable clawback. You can only enable **Allow Trust Line Clawback** if you have a completely empty owner directory, meaning you must do so before you set up any trust lines, offers, escrows, payment channels, checks, or signer lists. After you enable clawback, it cannot reverted: the account permanently gains the ability to claw back issued assets on trust lines. -_(Added by the [AMMClawback amendment][].)_ +{% amendment-disclaimer name="AMMClawback" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammcreate.md b/docs/references/protocol/transactions/types/ammcreate.md index 42aa0e48a0c..947e8757348 100644 --- a/docs/references/protocol/transactions/types/ammcreate.md +++ b/docs/references/protocol/transactions/types/ammcreate.md @@ -2,7 +2,7 @@ seo: description: Create a new Automated Market Maker for trading a given pair of assets. labels: - - AMM + - AMM --- # AMMCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") @@ -13,7 +13,7 @@ Creates both an [AMM entry][] and a [special AccountRoot entry](../../ledger-dat {% admonition type="warning" name="Caution" %}When you create the AMM, you should fund it with (approximately) equal-value amounts of each asset. Otherwise, other users can profit at your expense by trading with this AMM ([performing arbitrage](https://www.machow.ski/posts/an_introduction_to_automated_market_makers/#price-arbitrage)). The currency risk that liquidity providers take on increases with the volatility (potential for imbalance) of the asset pair. The higher the trading fee, the more it offsets this risk, so it's best to set the trading fee based on the volatility of the asset pair.{% /admonition %} -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammdelete.md b/docs/references/protocol/transactions/types/ammdelete.md index dd95d3cb7ae..facfdce9225 100644 --- a/docs/references/protocol/transactions/types/ammdelete.md +++ b/docs/references/protocol/transactions/types/ammdelete.md @@ -2,7 +2,7 @@ seo: description: Delete an Automated Market Maker with an empty asset pool. labels: - - AMM + - AMM --- # AMMDelete [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") @@ -11,7 +11,7 @@ Delete an empty [Automated Market Maker](../../../../concepts/tokens/decentraliz Normally, an [AMMWithdraw transaction][] automatically deletes an AMM and all associated ledger entries when it withdraws all the assets from the AMM's pool. However, if there are too many trust lines to the AMM account to remove in one transaction, it may stop before fully removing the AMM. Similarly, an AMMDelete transaction removes up to a maximum of 512 trust lines; it may take several AMMDelete transactions to delete all the trust lines and the associated AMM. In all cases, only the last such transaction deletes the AMM and AccountRoot ledger entries. -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammdeposit.md b/docs/references/protocol/transactions/types/ammdeposit.md index c9580979a04..dfed229c1f1 100644 --- a/docs/references/protocol/transactions/types/ammdeposit.md +++ b/docs/references/protocol/transactions/types/ammdeposit.md @@ -2,7 +2,7 @@ seo: description: Deposit funds into an Automated Market Maker in exchange for LPTokens. labels: - - AMM + - AMM --- # AMMDeposit [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDeposit.cpp "Source") @@ -17,7 +17,7 @@ You can't deposit either asset into an AMM if: - You aren't authorized to hold at least one of the pooled assets. {% /admonition %} -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammvote.md b/docs/references/protocol/transactions/types/ammvote.md index ad8a2a74a1c..ac0d0fe5c55 100644 --- a/docs/references/protocol/transactions/types/ammvote.md +++ b/docs/references/protocol/transactions/types/ammvote.md @@ -2,14 +2,14 @@ seo: description: Vote on the trading fee for an Automated Market Maker. labels: - - AMM + - AMM --- # AMMVote [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMVote.cpp "Source") Vote on the trading fee for an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) instance. Up to 8 accounts can vote in proportion to the amount of the AMM's LP Tokens they hold. Each new vote re-calculates the AMM's trading fee based on a weighted average of the votes. -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ammwithdraw.md b/docs/references/protocol/transactions/types/ammwithdraw.md index 54740adb6eb..ed0a73585cf 100644 --- a/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/docs/references/protocol/transactions/types/ammwithdraw.md @@ -2,14 +2,14 @@ seo: description: Return LPTokens to an Automated Market Maker in exchange for a share of the assets the pool holds. labels: - - AMM + - AMM --- # AMMWithdraw [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMWithdraw.cpp "Source") Withdraw assets from an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance by returning the AMM's liquidity provider tokens (LP Tokens). -_(Added by the [AMM amendment][].)_ +{% amendment-disclaimer name="AMM" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/batch.md b/docs/references/protocol/transactions/types/batch.md index 25f1d3d65e2..02b5eab9f8f 100644 --- a/docs/references/protocol/transactions/types/batch.md +++ b/docs/references/protocol/transactions/types/batch.md @@ -8,9 +8,9 @@ status: not_enabled # Batch [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Batch.cpp "Source") -The `Batch` transaction submits up to eight transactions as a single unit. `Batch` transactions are executed atomically in one of four modes: All or Nothing, Only One, Until Failure, and Independent. +Submit up to eight transactions as a single [batch](../../../../concepts/transactions/batch-transactions.md). The transactions in the batch are executed atomically in one of four modes: All or Nothing, Only One, Until Failure, or Independent. -_(Requires the [Batch amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="Batch" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/checkcancel.md b/docs/references/protocol/transactions/types/checkcancel.md index b9f6017c93f..b55fd84ff07 100644 --- a/docs/references/protocol/transactions/types/checkcancel.md +++ b/docs/references/protocol/transactions/types/checkcancel.md @@ -7,9 +7,9 @@ labels: # CheckCancel [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") -Cancels an unredeemed Check, removing it from the ledger without sending any money. The source or the destination of the check can cancel a Check at any time using this transaction type. If the Check has expired, any address can cancel it. +Cancels an unredeemed [check](../../../../concepts/payment-types/checks.md), removing it from the ledger without sending any money. The source or the destination of the check can cancel a check at any time. If the check has expired, any address can cancel it. -_(Added by the [Checks amendment][].)_ +{% amendment-disclaimer name="Checks" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/checkcash.md b/docs/references/protocol/transactions/types/checkcash.md index 22369c466ec..4d045e77e41 100644 --- a/docs/references/protocol/transactions/types/checkcash.md +++ b/docs/references/protocol/transactions/types/checkcash.md @@ -7,11 +7,11 @@ labels: # CheckCash [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CashCheck.cpp "Source") -Attempts to redeem a Check object in the ledger to receive up to the amount authorized by the corresponding [CheckCreate transaction][]. Only the `Destination` address of a Check can cash it with a CheckCash transaction. Cashing a check this way is similar to executing a [Payment][] initiated by the destination. +Attempts to redeem a [check](../../../../concepts/payment-types/checks.md) to receive up to the amount authorized by the corresponding [CheckCreate transaction][]. Only the `Destination` address of a check can cash it with a CheckCash transaction. Cashing a check this way is similar to executing a [Payment][] initiated by the destination. -Since the funds for a check are not guaranteed, redeeming a Check can fail because the sender does not have a high enough balance or because there is not enough liquidity to deliver the funds. If this happens, the Check remains in the ledger and the destination can try to cash it again later, or for a different amount. +Since the funds for a check are not guaranteed, redeeming a check can fail because the sender does not have a high enough balance or because there is not enough liquidity to deliver the funds. If this happens, the check remains in the ledger and the destination can try to cash it again later, or for a different amount. -_(Added by the [Checks amendment][].)_ +{% amendment-disclaimer name="Checks" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/checkcreate.md b/docs/references/protocol/transactions/types/checkcreate.md index 901211418ba..9c2faa2c231 100644 --- a/docs/references/protocol/transactions/types/checkcreate.md +++ b/docs/references/protocol/transactions/types/checkcreate.md @@ -7,9 +7,9 @@ labels: # CheckCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") -Create a Check object in the ledger, which is a deferred payment that can be cashed by its intended destination. The sender of this transaction is the sender of the Check. +Create an on-ledger [check](../../../../concepts/payment-types/checks.md), which is a deferred payment that can be cashed by its intended destination. The sender of this transaction is the sender of the check. -_(Added by the [Checks amendment][].)_ +{% amendment-disclaimer name="Checks" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -40,7 +40,7 @@ _(Added by the [Checks amendment][].)_ ## Error Cases -- If the `Destination` account is blocking incoming Checks, the transaction fails with the result code `tecNO_PERMISSION`. _(Requires the [DisallowIncoming amendment][])_ +- If the `Destination` account is blocking incoming Checks, the transaction fails with the result code `tecNO_PERMISSION`. {% amendment-disclaimer name="DisallowIncoming" /%} - If the `Destination` is the sender of the transaction, the transaction fails with the result code `temREDUNDANT`. - If the `Destination` [account](../../../../concepts/accounts/index.md) does not exist in the ledger, the transaction fails with the result code `tecNO_DST`. - If the `Destination` account has the `RequireDest` flag enabled but the transaction does not include a `DestinationTag` field, the transaction fails with the result code `tecDST_TAG_NEEDED`. diff --git a/docs/references/protocol/transactions/types/clawback.md b/docs/references/protocol/transactions/types/clawback.md index c28ae0aa6f9..d730fda234e 100644 --- a/docs/references/protocol/transactions/types/clawback.md +++ b/docs/references/protocol/transactions/types/clawback.md @@ -7,11 +7,9 @@ labels: # Clawback [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Clawback.cpp "Source") -Claw back tokens issued by your account. +[Claw back tokens](../../../../concepts/tokens/fungible-tokens/clawing-back-tokens.md) issued by your account. Issuers can only claw back [trust line tokens](../../../../concepts/tokens/fungible-tokens/trust-line-tokens.md) if they enabled the **Allow Trust Line Clawback** setting before issuing any tokens. Issuers can claw back [MPTs](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) if the corresponding MPT Issuance has clawback enabled. -Clawback is disabled by default. To use clawback, you must send an [AccountSet transaction][] to enable the **Allow Trust Line Clawback** setting. An issuer with any existing tokens cannot enable Clawback. You can only enable **Allow Trust Line Clawback** if you have a completely empty owner directory, meaning you must do so before you set up any trust lines, offers, escrows, payment channels, checks, or signer lists. After you enable Clawback, it cannot reverted: the account permanently gains the ability to claw back issued assets on trust lines. - -_(Added by the [Clawback amendment][].)_ +{% amendment-disclaimer name="Clawback" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -29,16 +27,12 @@ _(Added by the [Clawback amendment][].)_ {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} -| Field | JSON Type | [Internal Type][] | Description | -|:-------------------|:----------|:------------------|:------------------| -| `Amount` | [Currency Amount][] | Amount | 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 [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 %} - -{% admonition type="info" name="Note" %}To claw back funds from an MPT holder, the issuer must have specified that the MPT allows clawback by setting the `tfMPTCanClawback` flag when creating the MPT using the `MPTokenIssuanceCreate` transaction. Assuming an MPT was created with this flag set, clawbacks are allowed using the `Clawback` transaction.{% /admonition %} - +| Field | JSON Type | [Internal Type][] | Required? | Description | +|:-------------------|:----------|:------------------|:----------|-------------| +| `Amount` | [Currency Amount][] | Amount | Yes | The amount to claw back. The quantity in the `value` sub-field must not be zero. If this is more than the current balance, the transaction claws back the entire balance. When clawing back trust line tokens, the `issuer` sub-field indicates the token holder to claw back tokens from.| +| `Holder` | String | AccountID | No | The holder to claw back tokens from, if clawing back MPTs. The holder must have a non-zero balance of the MPT issuance indicated in the `Amount` field. {% amendment-disclaimer name="MPTokensV1" /%} | +When clawing back trust line tokens, you must omit the `Holder` field. When clawing back MPTs, you must provide the `Holder` field. ## Error Cases @@ -46,10 +40,10 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} | Error Code | Description | |:-----------|:------------| -| `temDISABLED` | Occurs if the [Clawback amendment](/resources/known-amendments.md#clawback) is not enabled. | -| `temBAD_AMOUNT` | Occurs if the holder's balance is 0. It is not an error if the amount exceeds the holder's balance; in that case, the maximum available balance is clawed back. Also occurs if the counterparty listed in `Amount` is the same as the `Account` issuing this transaction. | -| `tecAMM_ACCOUNT` | This operation is not allowed with an AMM account. Use [`AMMClawback`](./ammclawback.md) instead. | -| `tecNO_LINE` | Occurs there is no trust line with the counterparty or that trust line's balance is 0. | -| `tecNO_PERMISSION` | Occurs if you attempt to set `lsfAllowTrustlineClawback` while `lsfNoFreeze` is set. Also occurs, conversely, if you try to set `lsfNoFreeze` while `lsfAllowTrustLineClawback` is set. | +| `temDISABLED` | The [Clawback amendment][] is not enabled. | +| `temBAD_AMOUNT` | The amount of tokens specified to claw back is invalid or zero, or the specified holder is the issuer. | +| `tecAMM_ACCOUNT` | The specified holder is an Automated Market Maker (AMM). To claw back tokens from an AMM, use [`AMMClawback`](./ammclawback.md) instead. | +| `tecNO_LINE` | There is no trust line with the counterparty or that trust line's balance is 0. | +| `tecNO_PERMISSION` | The sender of this transaction does not have the ability to claw back the specified tokens. | {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/references/protocol/transactions/types/credentialaccept.md b/docs/references/protocol/transactions/types/credentialaccept.md index eb01f498da6..e6f4ec07ba0 100644 --- a/docs/references/protocol/transactions/types/credentialaccept.md +++ b/docs/references/protocol/transactions/types/credentialaccept.md @@ -1,13 +1,13 @@ --- seo: description: Accept a credential provisionally issued to your account. -status: not_enabled --- # CredentialAccept +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Credentials.cpp "Source") -A CredentialAccept transaction accepts a credential, which makes the credential valid. Only the subject of the credential can do this. +Accept a [credential](../../../../concepts/decentralized-storage/credentials.md), which makes the credential valid. Only the subject of the credential can do this. -_(Requires the [Credentials amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="Credentials" /%} ## Example CredentialAccept JSON @@ -46,7 +46,7 @@ The combination of `Account`, `Issuer`, and `CredentialType` must match a `Crede | `tecNO_ENTRY` | The credential uniquely identified by the `Account`, `Issuer`, and `CredentialType` fields of the transaction does not exist in the ledger. | | `temDISABLED` | The related amendment is not enabled. | | `temINVALID_ACCOUNT_ID` | The provided `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). | -| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. _(Requires the [fixInvalidTxFlags amendment][] {% not-enabled /%})_ | +| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. {% amendment-disclaimer name="fixInvalidTxFlags" /%} | ## See Also diff --git a/docs/references/protocol/transactions/types/credentialcreate.md b/docs/references/protocol/transactions/types/credentialcreate.md index e570dcbb118..1025fe3c170 100644 --- a/docs/references/protocol/transactions/types/credentialcreate.md +++ b/docs/references/protocol/transactions/types/credentialcreate.md @@ -1,13 +1,13 @@ --- seo: description: Provisionally issue a credential to a subject account. -status: not_enabled --- # CredentialCreate +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Credentials.cpp "Source") -A CredentialCreate transaction creates a credential in the ledger. The issuer of the credential uses this transaction to provisionally issue a credential. The credential is not valid until the subject of the credential accepts it with a [CredentialAccept transaction][]. +Provisionally issue a [credential](../../../../concepts/decentralized-storage/credentials.md) in the ledger. The credential is not valid until the subject of the credential accepts it with a [CredentialAccept transaction][]. -_(Requires the [Credentials amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="Credentials" /%} ## Example CredentialCreate JSON @@ -48,7 +48,7 @@ Besides errors that can occur for all transactions, CredentialCreate transaction | `tecNO_TARGET` | The account specified in the `Subject` field is not a funded account in the ledger. | | `temDISABLED` | The related amendment is not enabled. | | `temINVALID_ACCOUNT_ID` | The provided `Subject` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). | -| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. _(Requires the [fixInvalidTxFlags amendment][] {% not-enabled /%})_ | +| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. {% amendment-disclaimer name="fixInvalidTxFlags" /%} | ## See Also diff --git a/docs/references/protocol/transactions/types/credentialdelete.md b/docs/references/protocol/transactions/types/credentialdelete.md index bc04e4ca4e4..7c244816da5 100644 --- a/docs/references/protocol/transactions/types/credentialdelete.md +++ b/docs/references/protocol/transactions/types/credentialdelete.md @@ -1,13 +1,13 @@ --- seo: description: Remove a credential from the ledger, effectively revoking it. -status: not_enabled --- # CredentialDelete +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Credentials.cpp "Source") -A CredentialDelete transaction removes a credential from the ledger, effectively revoking it. Users may also want to delete an unwanted credential to reduce their [reserve requirement](../../../../concepts/accounts/reserves.md). +Remove a [credential](../../../../concepts/decentralized-storage/credentials.md) from the ledger, effectively revoking it. Users may also want to delete an unwanted credential to reduce their [reserve requirement](../../../../concepts/accounts/reserves.md). -_(Requires the [Credentials amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="Credentials" /%} ## Example CredentialDelete JSON @@ -47,7 +47,7 @@ This transaction looks for a [Credential ledger entry](../../ledger-data/ledger- | `temINVALID_ACCOUNT_ID` | A provided `Subject` or `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). | | `tecNO_PERMISSION` | The sender is neither the issuer nor subject of the credential, and the credential is not expired. | | `tecNO_ENTRY` | The specified credential does not exist in the ledger. | -| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. _(Requires the [fixInvalidTxFlags amendment][] {% not-enabled /%})_ | +| `temINVALID_FLAG` | The transaction includes a [Flag](../common-fields.md#flags-field) that does not exist, or includes a contradictory combination of flags. {% amendment-disclaimer name="fixInvalidTxFlags" /%} | ## See Also diff --git a/docs/references/protocol/transactions/types/delegateset.md b/docs/references/protocol/transactions/types/delegateset.md index 0e0caae4d60..7c06f55f0a7 100644 --- a/docs/references/protocol/transactions/types/delegateset.md +++ b/docs/references/protocol/transactions/types/delegateset.md @@ -12,7 +12,7 @@ status: not_enabled [Delegate permissions](/docs/concepts/accounts/permission-delegation) to another account to send transactions on your behalf. This transaction type can grant, change, or revoke permissions; it creates, modifies, or deletes a [Delegate ledger entry][] accordingly. -_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="PermissionDelegation" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/depositpreauth.md b/docs/references/protocol/transactions/types/depositpreauth.md index 90743d9278b..86e9dfd2081 100644 --- a/docs/references/protocol/transactions/types/depositpreauth.md +++ b/docs/references/protocol/transactions/types/depositpreauth.md @@ -7,11 +7,11 @@ labels: # DepositPreauth [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") -A DepositPreauth transaction grants preauthorization to deliver payments to your account. This is only useful if you are using (or plan to use) [Deposit Authorization](../../../../concepts/accounts/depositauth.md). +Grant preauthorization to send payments to your account. This is only useful if you are using (or plan to use) [Deposit Authorization](../../../../concepts/accounts/depositauth.md). {% admonition type="success" name="Tip" %}You can use this transaction before you enable Deposit Authorization. This may be useful to ensure a smooth transition from not requiring deposit authorization to requiring it.{% /admonition %} -_(Added by the [DepositPreauth amendment][].)_ +{% amendment-disclaimer name="DepositPreauth" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -57,9 +57,9 @@ _(Added by the [DepositPreauth amendment][].)_ | Field | JSON Type | [Internal Type][] | Required? | Description | |:-------------------------|:---------------------|:------------------|:----------|:------------| | `Authorize` | String - [Address][] | AccountID | No | An account to preauthorize. | -| `AuthorizeCredentials` | Array | Array | No | A set of credentials to authorize. _(Requires the [Credentials amendment][]. {% not-enabled /%})_ | +| `AuthorizeCredentials` | Array | Array | No | A set of credentials to authorize. {% amendment-disclaimer name="Credentials" /%} | | `Unauthorize` | String | AccountID | No | An account whose preauthorization should be revoked. | -| `UnauthorizeCredentials` | Array | Array | No | A set of credentials whose preauthorization should be revoked. _(Requires the [Credentials amendment][]. {% not-enabled /%})_ | +| `UnauthorizeCredentials` | Array | Array | No | A set of credentials whose preauthorization should be revoked. {% amendment-disclaimer name="Credentials" /%} | You must provide **exactly one** of `Authorize`, `AuthorizeCredentials`, `Unauthorize`, or `UnauthorizeCredentials`. diff --git a/docs/references/protocol/transactions/types/diddelete.md b/docs/references/protocol/transactions/types/diddelete.md index 3642120b701..0daf4057c86 100644 --- a/docs/references/protocol/transactions/types/diddelete.md +++ b/docs/references/protocol/transactions/types/diddelete.md @@ -2,17 +2,16 @@ seo: description: Delete a Decentralized Identifier. labels: - - DID + - DID --- # DIDDelete - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "Source") -Delete the [DID ledger entry](../../ledger-data/ledger-entry-types/did.md) associated with the specified `Account` field. +Delete the sender's [decentralized identifier (DID)](../../../../concepts/decentralized-storage/decentralized-identifiers.md). {% admonition type="info" name="Note" %}This transaction only uses the [common fields][].{% /admonition %} -_(Added by the [DID amendment][].)_ +{% amendment-disclaimer name="DID" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/didset.md b/docs/references/protocol/transactions/types/didset.md index beefaec6c21..3b181b8ad46 100644 --- a/docs/references/protocol/transactions/types/didset.md +++ b/docs/references/protocol/transactions/types/didset.md @@ -2,15 +2,14 @@ seo: description: Create or update a Decentralized Identifier. labels: - - DID + - DID --- # DIDSet - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "Source") -Creates a new [DID ledger entry](../../ledger-data/ledger-entry-types/did.md) or updates the fields of an existing one. +Create or update a [decentralized identifier (DID)](../../../../concepts/decentralized-storage/decentralized-identifiers.md). -_(Added by the [DID amendment][].)_ +{% amendment-disclaimer name="DID" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/escrowcancel.md b/docs/references/protocol/transactions/types/escrowcancel.md index 410ec8dada6..996e766ad52 100644 --- a/docs/references/protocol/transactions/types/escrowcancel.md +++ b/docs/references/protocol/transactions/types/escrowcancel.md @@ -2,15 +2,14 @@ seo: description: Cancel an expired escrow, returning the funds to the sender. labels: - - Escrow + - Escrow --- # EscrowCancel - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") -Return escrowed XRP to the sender. +Return funds from an expired [escrow](../../../../concepts/payment-types/escrow.md) to it sender. -_(Added by the [Escrow amendment][].)_ +{% amendment-disclaimer name="Escrow" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/escrowcreate.md b/docs/references/protocol/transactions/types/escrowcreate.md index ba5b5d2c793..f8f1b888dcc 100644 --- a/docs/references/protocol/transactions/types/escrowcreate.md +++ b/docs/references/protocol/transactions/types/escrowcreate.md @@ -2,15 +2,14 @@ seo: description: Escrow funds, which can be released to the destination after a specific time or condition. labels: - - Escrow + - Escrow --- # EscrowCreate - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") -Sequester XRP until the escrow process either finishes or is canceled. +Set aside funds in an [escrow](../../../../concepts/payment-types/escrow.md) that delivers them to a predetermined recipient when certain conditions are met. If the escrow has an expiration, the funds can also be returned to the sender after it expires. -_(Added by the [Escrow amendment][].)_ +{% amendment-disclaimer name="Escrow" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/escrowfinish.md b/docs/references/protocol/transactions/types/escrowfinish.md index 6e18b18a5c2..04dea5d2119 100644 --- a/docs/references/protocol/transactions/types/escrowfinish.md +++ b/docs/references/protocol/transactions/types/escrowfinish.md @@ -2,15 +2,14 @@ seo: description: Deliver escrowed funds to the intended recipient. labels: - - Escrow + - Escrow --- # EscrowFinish - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") -Deliver XRP from an escrow (held payment) to the recipient. +Deliver XRP from an [escrow](../../../../concepts/payment-types/escrow.md) to the recipient. -_(Added by the [Escrow amendment][].)_ +{% amendment-disclaimer name="Escrow" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/ledgerstatefix.md b/docs/references/protocol/transactions/types/ledgerstatefix.md index 07bf92c2bf5..90a17ae0ba5 100644 --- a/docs/references/protocol/transactions/types/ledgerstatefix.md +++ b/docs/references/protocol/transactions/types/ledgerstatefix.md @@ -2,15 +2,15 @@ seo: description: Repair corruptions to the XRP ledger's state data. labels: - - Utilities - - Troubleshooting + - Utilities + - Troubleshooting --- # LedgerStateFix [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/LedgerStateFix.cpp "Source") -`LedgerStateFix` is a general purpose transaction used to fix specific issues affecting the XRP ledger. You submit the transaction with the `LedgerFixType` value set to indicate the particular error state to correct. +Repair a specific corruption affecting on-ledger data. This transaction type has a different mode for each type of error state or corruption it can fix. -_(Added by the [fixNFTokenPageLinks amendment][].)_ +{% amendment-disclaimer name="fixNFTokenPageLinks" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/mptokenauthorize.md b/docs/references/protocol/transactions/types/mptokenauthorize.md index 8809137dcad..da3d5832386 100644 --- a/docs/references/protocol/transactions/types/mptokenauthorize.md +++ b/docs/references/protocol/transactions/types/mptokenauthorize.md @@ -2,14 +2,12 @@ seo: description: Set up your account to receive a specific MPT as a holder; or authorize a holder as an MPT issuer. labels: - - Multi-purpose Tokens, MPTs -status: not_enabled + - Multi-purpose Tokens, MPTs --- - # MPTokenAuthorize [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "Source") -An MPTokenAuthorize transaction controls whether an account can hold a given [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md). It has several uses: +Control whether an account can hold a given [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md). This transaction has several uses: - An account indicates their willingness to hold an MPT. This creates a new [MPToken entry][] with an initial zero balance owned by that account. This is a prerequisite to receive that type of MPT in a payment. - 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. diff --git a/docs/references/protocol/transactions/types/mptokenissuancecreate.md b/docs/references/protocol/transactions/types/mptokenissuancecreate.md index 73d6ff02e4e..ba2ac29867e 100644 --- a/docs/references/protocol/transactions/types/mptokenissuancecreate.md +++ b/docs/references/protocol/transactions/types/mptokenissuancecreate.md @@ -1,19 +1,15 @@ --- seo: - description: Define the properties of a new Multi-Purpose Token (MPT). + description: Define the properties of a new Multi-Purpose Token (MPT). labels: - - Multi-purpose Tokens, MPTs -status: not_enabled + - Multi-purpose Tokens, MPTs --- - # MPTokenIssuanceCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "Source") -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). - -If the transaction is successful, the newly created token is owned by the account (the creator account) that executed the transaction. +Creates a new [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) issuance, which defines the properties of those MPTs. This is a prerequisite to actually issuing the tokens. -Whenever your query returns an `MPTokenIssuance` transaction response, there will always be an `mpt_issuance_id` field on the Transaction Metadata page. +If the transaction is successful, it creates an [MPTokenIssuance entry][] where the sender of the transaction is the MPT's issuer. {% amendment-disclaimer name="MPTokensV1" /%} diff --git a/docs/references/protocol/transactions/types/mptokenissuancedestroy.md b/docs/references/protocol/transactions/types/mptokenissuancedestroy.md index 17854094ada..db6a328c670 100644 --- a/docs/references/protocol/transactions/types/mptokenissuancedestroy.md +++ b/docs/references/protocol/transactions/types/mptokenissuancedestroy.md @@ -2,15 +2,12 @@ seo: description: Delete a Multi-Purpose Token definition. labels: - - Multi-purpose Tokens, MPTs -status: not_enabled + - Multi-purpose Tokens, MPTs --- # MPTokenIssuanceDestroy [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "Source") -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). - -If this operation succeeds, the corresponding `MPTokenIssuance` is removed and the owner’s reserve requirement is reduced by one. This operation must fail if there are any holders of the MPT in question. +Delete a [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) issuance. Only the issuer can delete an MPT issuance, and only if there are no holders of the MPT. {% amendment-disclaimer name="MPTokensV1" /%} @@ -24,7 +21,6 @@ If this operation succeeds, the corresponding `MPTokenIssuance` is removed and t } ``` - {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} diff --git a/docs/references/protocol/transactions/types/mptokenissuanceset.md b/docs/references/protocol/transactions/types/mptokenissuanceset.md index 7439ec12752..a4cc822c1d2 100644 --- a/docs/references/protocol/transactions/types/mptokenissuanceset.md +++ b/docs/references/protocol/transactions/types/mptokenissuanceset.md @@ -2,13 +2,12 @@ seo: description: Set mutable properties of a Multi-Purpose Token definition. labels: - - Multi-purpose Tokens, MPTs -status: not_enabled + - Multi-purpose Tokens, MPTs --- # MPTokenIssuanceSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "Source") -Use this transaction to update a mutable property for a Multi-purpose Token. The transaction flags determine which change(s) to apply. +Update a mutable property of a [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md) issuance, including locking (freezing) or unlocking the tokens globally or for an individual holder. {% amendment-disclaimer name="MPTokensV1" /%} diff --git a/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/docs/references/protocol/transactions/types/nftokenacceptoffer.md index 76844651ca1..abb16beb733 100644 --- a/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -7,12 +7,12 @@ labels: # NFTokenAcceptOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "Source") -The `NFTokenAcceptOffer` transaction is used to accept offers to buy or sell an NFT. It has two possible modes: +Accept an offer to buy or sell a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). This transaction has two modes: * In _direct_ mode, a buyer can accept a sell offer directly, or a seller can accept a buy offer directly. * In _brokered_ mode, a third party (the _broker_) can match two distinct offers, one buying and one selling. If the buy price is higher than the sell price, the broker can claim the difference as a fee for themself. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example NFTokenAcceptOffer JSON diff --git a/docs/references/protocol/transactions/types/nftokenburn.md b/docs/references/protocol/transactions/types/nftokenburn.md index 17c4263283e..a1afb208cc0 100644 --- a/docs/references/protocol/transactions/types/nftokenburn.md +++ b/docs/references/protocol/transactions/types/nftokenburn.md @@ -7,13 +7,11 @@ labels: # NFTokenBurn [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenBurn.cpp "Source") -The `NFTokenBurn` transaction is used to remove a `NFToken` object from the `NFTokenPage` in which it is being held, effectively removing the token from the ledger (_burning_ it). +Burn (destroy) a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). The NFT's current holder can always burn it, and if the token's "Burnable" flag is enabled, the issuer and their authorized minter (if they have one) can also burn the NFT. -The sender of this transaction must be the owner of the `NFToken` to burn; or, if the `NFToken` has the `lsfBurnable` flag enabled, can be the issuer or the issuer's authorized `NFTokenMinter` account instead. +If the transaction succeeds, it removes the corresponding [NFToken][] object from the [NFTokenPage entry][] that was storing it. This can cause the pages of an NFT directory to be consolidated. -If this operation succeeds, the corresponding `NFToken` is removed. If this operation empties the `NFTokenPage` holding the `NFToken` or results in consolidation, thus removing a `NFTokenPage`, the owner’s reserve requirement is reduced by one. - -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/nftokencanceloffer.md b/docs/references/protocol/transactions/types/nftokencanceloffer.md index 34e88fe5a2c..345331a1a02 100644 --- a/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -7,9 +7,9 @@ labels: # NFTokenCancelOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCancelOffer.cpp "Source") -The `NFTokenCancelOffer` transaction can be used to cancel existing token offers created using `NFTokenCreateOffer`. +Cancel an offer to buy or sell a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/nftokencreateoffer.md b/docs/references/protocol/transactions/types/nftokencreateoffer.md index 42504d04927..c374ee803a8 100644 --- a/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -7,11 +7,11 @@ labels: # NFTokenCreateOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "Source") -Creates either a new _Sell_ offer for an `NFToken` owned by the account executing the transaction, or a new _Buy_ offer for an `NFToken` owned by another account. +Create a new offer to either buy or sell a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). You can only offer to sell NFTs you own or buy NFTs you don't own. -If successful, the transaction creates a [NFTokenOffer object][]. Each offer counts as one object towards the [owner reserve](../../../../concepts/accounts/reserves.md) of the account that placed the offer. +If successful, the transaction creates a [NFTokenOffer object][]. To complete the sale and change ownership of the NFT, the offer must be accepted using an [NFTokenAcceptOffer transaction][]. -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -64,7 +64,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} | `tecNO_ENTRY` | The `NFToken` is not owned by the expected account. | | `tecNO_ISSUER` | The issuer specified in the `Amount` field does not exist. | | `tecNO_LINE` | The `Amount` field is denominated in fungible tokens, but the `NFToken`'s issuer does not have a trust line for those tokens and the `NFToken` does not have the [`lsfTrustLine` flag](../../data-types/nftoken.md#nftoken-flags) enabled. | -| `tecNO_PERMISSION` | The `Destination` account blocks incoming NFTokenOffers. _(Requires the [DisallowIncoming amendment][] )_ +| `tecNO_PERMISSION` | The `Destination` account blocks incoming NFTokenOffers. {% amendment-disclaimer name="DisallowIncoming" /%} | `tecUNFUNDED_OFFER` | For a buy offer, the sender does have the funds specified in the `Amount` field available. If the `Amount` is XRP, this could be due to the reserve requirement; if the `Amount` is denominated in fungible tokens, this could be because they are [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md). | | `tefNFTOKEN_IS_NOT_TRANSFERABLE` | The `NFToken` has the [`lsfTransferable` flag](../../data-types/nftoken.md#nftoken-flags) disabled and this transaction would not transfer the `NFToken` to or from the issuer. | diff --git a/docs/references/protocol/transactions/types/nftokenmint.md b/docs/references/protocol/transactions/types/nftokenmint.md index ab975403ea7..7b710b1d077 100644 --- a/docs/references/protocol/transactions/types/nftokenmint.md +++ b/docs/references/protocol/transactions/types/nftokenmint.md @@ -7,9 +7,11 @@ labels: # NFTokenMint [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") -The `NFTokenMint` transaction creates a non-fungible token and adds it to the relevant [NFTokenPage object][] of the `NFTokenMinter` as an [NFToken][] object. This transaction is the only opportunity the `NFTokenMinter` has to specify any token fields that are defined as immutable (for example, the `TokenFlags`). +Create a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). This is the only opportunity the minter has to specify any token fields and flags that are immutable. This transaction can be sent by the NFT's issuer or by an [authorized minter](../../../../concepts/tokens/nfts/authorizing-another-minter.md). -_(Added by the [NonFungibleTokensV1_1 amendment][].)_ +If successful, the transaction adds an [NFToken][] object to one of the minter's [NFTokenPage ledger entries][NFTokenPage entry]. + +{% amendment-disclaimer name="NonFungibleTokensV1_1" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/nftokenmodify.md b/docs/references/protocol/transactions/types/nftokenmodify.md index d742e8c8d56..afa56b5618c 100644 --- a/docs/references/protocol/transactions/types/nftokenmodify.md +++ b/docs/references/protocol/transactions/types/nftokenmodify.md @@ -2,14 +2,14 @@ seo: description: Modify a dynamic NFT. labels: - - Non-fungible Tokens, NFTs + - Non-fungible Tokens, NFTs --- # NFTokenModify [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenModify.cpp "Source") -`NFTokenModify` is used to change the `URI` field of an NFT to point to a different URI in order to update the supporting data for the NFT. The NFT must have been minted with the `tfMutable` flag set. See [Dynamic Non-Fungible Tokens](../../../../concepts/tokens/nfts/dynamic-nfts.md). +Change the `URI` field of a [dynamic NFT](../../../../concepts/tokens/nfts/dynamic-nfts.md) to update the supporting data for the NFT. Only the issuer, or their authorized minter, can modify an NFT, and only if it was minted with the **Mutable** flag enabled. -_(Requires the [DynamicNFT amendment][] {% not-enabled /%}.)_ +{% amendment-disclaimer name="DynamicNFT" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/offercancel.md b/docs/references/protocol/transactions/types/offercancel.md index 69cfd36de13..795d14e105c 100644 --- a/docs/references/protocol/transactions/types/offercancel.md +++ b/docs/references/protocol/transactions/types/offercancel.md @@ -1,6 +1,6 @@ --- seo: - description: Withdraw an offer to trade in the decentralized exchange. + description: Cancel an offer to trade in the decentralized exchange. labels: - Decentralized Exchange --- @@ -8,7 +8,7 @@ labels: [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") -An OfferCancel transaction removes an Offer object from the XRP Ledger. +Cancel an [offer](../../../../concepts/tokens/decentralized-exchange/offers.md) in the decentralized exchange. ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/offercreate.md b/docs/references/protocol/transactions/types/offercreate.md index 70f5f0e087d..1f4dba6cfdd 100644 --- a/docs/references/protocol/transactions/types/offercreate.md +++ b/docs/references/protocol/transactions/types/offercreate.md @@ -5,10 +5,9 @@ labels: - Decentralized Exchange --- # OfferCreate - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateOffer.cpp "Source") -An OfferCreate transaction places an [Offer](../../../../concepts/tokens/decentralized-exchange/offers.md) in the [decentralized exchange](../../../../concepts/tokens/decentralized-exchange/index.md). +Place an [offer](../../../../concepts/tokens/decentralized-exchange/offers.md) to trade in the [decentralized exchange](../../../../concepts/tokens/decentralized-exchange/index.md). ## Example {% $frontmatter.seo.title %} JSON @@ -36,7 +35,7 @@ An OfferCreate transaction places an [Offer](../../../../concepts/tokens/decentr | Field | JSON Type | [Internal Type][] | Required? | Description | |:-----------------|:--------------------|:------------------|:----------|-------------| -| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If provided, restrict this offer to the [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) of that domain. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If provided, restrict this offer to the [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) of that domain. {% amendment-disclaimer name="PermissionedDEX" /%} | | [`Expiration`](../../../../concepts/tokens/decentralized-exchange/offers.md#offer-expiration) | Number | UInt32 | No | Time after which the Offer is no longer active, in [seconds since the Ripple Epoch][]. | | `OfferSequence` | Number | UInt32 | No | An Offer to delete first, specified in the same way as [OfferCancel][]. | | `TakerGets` | [Currency Amount][] | Amount | Yes | The amount and type of currency being sold. | @@ -52,7 +51,7 @@ Transactions of the OfferCreate type support additional values in the [`Flags` f | `tfImmediateOrCancel` | `0x00020000` | 131072 | Treat the offer as an [Immediate or Cancel order](http://en.wikipedia.org/wiki/Immediate_or_cancel) and do not place an [Offer entry][] into the order books. The transaction trades as much as it can by consuming existing offers when it's processed. | | `tfFillOrKill` | `0x00040000` | 262144 | Treat the offer as a [Fill or Kill order](http://en.wikipedia.org/wiki/Fill_or_kill), do not place an [Offer entry][] into the order books, and cancel the offer if it cannot be fully filled at the time of execution. By default, this means that the owner must receive the full `TakerPays` amount; if the `tfSell` flag is enabled, the owner must be able to spend the entire `TakerGets` amount instead. | | `tfSell` | `0x00080000` | 524288 | Exchange the entire `TakerGets` amount, even if it means obtaining more than the `TakerPays` amount in exchange. | -| `tfHybrid` | `0x00100000` | 1048576 | Make this a hybrid offer that can use both a permissioned DEX and the open DEX. The `DomainID` field must be provided when using this flag. | +| `tfHybrid` | `0x00100000` | 1048576 | Make this a hybrid offer that can use both a permissioned DEX and the open DEX. The `DomainID` field must be provided when using this flag. {% amendment-disclaimer name="PermissionedDEX" /%} | ## Error Cases @@ -67,7 +66,7 @@ Transactions of the OfferCreate type support additional values in the [`Flags` f | `tecNO_AUTH` | The transaction involves a token whose issuer uses [Authorized Trust Lines](../../../../concepts/tokens/fungible-tokens/authorized-trust-lines.md) and the the trust line that would receive the tokens exists but has not been authorized. | | `tecNO_ISSUER` | The transaction specifies a token whose `issuer` value is not a funded account in the ledger. | | `tecNO_LINE` | The transaction involves a token whose issuer uses [Authorized Trust Lines](../../../../concepts/tokens/fungible-tokens/authorized-trust-lines.md) and the necessary trust line does not exist. | -| `tecNO_PERMISSION` | The transaction uses a `DomainID` but the sender is not a member of that domain. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `tecNO_PERMISSION` | The transaction uses a `DomainID` but the sender is not a member of that domain. {% amendment-disclaimer name="PermissionedDEX" /%} | | `tecUNFUNDED_OFFER` | The owner does not hold a positive amount of the `TakerGets` currency. (Exception: if `TakerGets` specifies a token that the owner issues, the transaction can succeed.) | | `temBAD_CURRENCY` | The transaction specifies a fungible token incorrectly, such as a fungible token with the currency code "XRP". | | `temBAD_EXPIRATION` | The transaction contains an `Expiration` field that is not validly formatted. | diff --git a/docs/references/protocol/transactions/types/oracledelete.md b/docs/references/protocol/transactions/types/oracledelete.md index 8f6e6dedbf8..2f81726906d 100644 --- a/docs/references/protocol/transactions/types/oracledelete.md +++ b/docs/references/protocol/transactions/types/oracledelete.md @@ -5,13 +5,11 @@ labels: - Oracle --- # OracleDelete -_(Requires the [PriceOracle amendment][])_ - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteOracle.cpp "Source") -Delete an `Oracle` ledger entry. +Delete a [price oracle](../../../../concepts/decentralized-storage/price-oracles.md). Only the owner of the price oracle can send this transaction. -_(Added by the [PriceOracle amendment][].)_ +{% amendment-disclaimer name="PriceOracle" /%} ## Example OracleDelete JSON @@ -29,8 +27,7 @@ _(Added by the [PriceOracle amendment][].)_ | Field | JSON Type | Internal Type | Required? | Description | |--------------------|-----------|---------------|-----------|-------------| -| `Account` | String | AccountID | Yes | This account must match the account in the `Owner` field of the `Oracle` object. | -| `OracleDocumentID` | String | UInt32 | Yes | A unique identifier of the price oracle for the `Account`. | +| `OracleDocumentID` | Number | UInt32 | Yes | The identifying number of the price oracle, which must be unique per owner. | ## Error Cases diff --git a/docs/references/protocol/transactions/types/oracleset.md b/docs/references/protocol/transactions/types/oracleset.md index 9518b1bc8d8..bd8247e7f84 100644 --- a/docs/references/protocol/transactions/types/oracleset.md +++ b/docs/references/protocol/transactions/types/oracleset.md @@ -7,9 +7,9 @@ labels: # OracleSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetOracle.cpp "Source") -Creates a new `Oracle` ledger entry or updates the fields of an existing one, using the Oracle Document ID. +Create or update a [price oracle](../../../../concepts/decentralized-storage/price-oracles.md). Only the owner of an existing price oracle can update it. -_(Added by the [PriceOracle amendment][].)_ +{% amendment-disclaimer name="PriceOracle" /%} ## Example OracleSet JSON @@ -40,9 +40,8 @@ _(Added by the [PriceOracle amendment][].)_ | Field | JSON Type | Internal Type | Required? | Description | |--------------------|-----------|---------------|-----------|-------------| -| `Account` | String | AccountID | Yes | This account must match the account in the `Owner` field of the `Oracle` object. | -| `OracleDocumentID` | Number | UInt32 | Yes | A unique identifier of the price oracle for the `Account`. | -| `Provider` | String | Blob | Variable | An arbitrary value that identifies an oracle provider, such as Chainlink, Band, or DIA. This field is a string, up to 256 ASCII hex encoded characters (0x20-0x7E). This field is required when creating a new `Oracle` ledger entry, but is optional for updates. | +| `OracleDocumentID` | Number | UInt32 | Yes | The identifying number of the price oracle, which must be unique per owner. | +| `Provider` | String | Blob | Variable | An arbitrary value that identifies an oracle provider, such as Chainlink, Band, or DIA. This field is a string, up to 256 ASCII hex encoded characters (0x20-0x7E). This field is required when creating a new price oracle, but is optional for updates. | | `URI` | String | Blob | No | An optional Universal Resource Identifier to reference price data off-chain. This field is limited to 256 bytes. | | `LastUpdateTime` | Number | UInt32 | Yes | The time the data was last updated, in seconds since the [UNIX Epoch](https://en.wikipedia.org/wiki/Unix_time). The value must be within 300 seconds (5 minutes) of the ledger's close time. | | `AssetClass` | String | Blob | Variable | Describes the type of asset, such as "currency", "commodity", or "index". This field is a string, up to 16 ASCII hex encoded characters (0x20-0x7E). This field is required when creating a new `Oracle` ledger entry, but is optional for updates. | diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index b64a298a112..716dd404c7e 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -10,7 +10,7 @@ labels: # Payment [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Payment.cpp "Source") -A Payment transaction represents a transfer of value from one account to another. (Depending on the path taken, this can involve additional exchanges of value, which occur atomically.) This transaction type can be used for several [types of payments](#types-of-payments). +Send value to an account. (Depending on the path taken, this can involve exchanges of several types of funds, all of which occur atomically.) This transaction type can be used for several [types of payments](#types-of-payments). Payments are also the only way to [create accounts](#creating-accounts). @@ -40,12 +40,12 @@ Payments are also the only way to [create accounts](#creating-accounts). | Field | JSON Type | [Internal Type][] | Required? | Description | |:-----------------|:---------------------|:------------------|:----------|:------------| | `Amount` | [Currency Amount][] | Amount | API v1: Yes | Alias to `DeliverMax`. | -| `CredentialIDs` | Array of Strings | Vector256 | No | Set of Credentials to authorize a deposit made by this transaction. Each member of the array must be the ledger entry ID of a Credential entry in the ledger. _(Requires the [Credentials amendment][]._ {% not-enabled /%})_ | +| `CredentialIDs` | Array of Strings | Vector256 | No | Set of Credentials to authorize a deposit made by this transaction. Each member of the array must be the ledger entry ID of a Credential entry in the ledger. {% amendment-disclaimer name="Credentials" /%} | | `DeliverMax` | [Currency Amount][] | Amount | Yes | [API v2][]: The maximum amount of currency to deliver. [Partial payments](#partial-payments) can deliver less than this amount and still succeed; other payments fail unless they deliver the exact amount. {% badge href="https://github.com/XRPLF/rippled/releases/tag/2.0.0" %}New in: rippled 2.0.0{% /badge %} | | `DeliverMin` | [Currency Amount][] | Amount | No | Minimum amount of destination currency this transaction should deliver. Only valid if this is a [partial payment](#partial-payments). | | `Destination` | String - [Address][] | AccountID | Yes | The account receiving the payment. | | `DestinationTag` | Number | UInt32 | No | Arbitrary tag that identifies the reason for the payment to the destination, or a hosted recipient to pay. | -| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If this is a cross-currency payment, only use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) to convert currency. Both the sender and the recipient must have valid credentials that grant access to the specified domain. This field has no effect if the payment is not cross-currency. _(Requires the [PermissionedDEX amendment][] {% not-enabled /%})_ | +| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of a permissioned domain. If this is a cross-currency payment, only use the corresponding [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md) to convert currency. Both the sender and the recipient must have valid credentials that grant access to the specified domain. This field has no effect if the payment is not cross-currency. {% amendment-disclaimer name="PermissionedDEX" %/} | | `InvoiceID` | String - Hexadecimal | UInt256 | No | Arbitrary 256-bit value representing a specific reason or identifier for this payment. | | `Paths` | Array of path arrays | PathSet | No | _(Auto-fillable)_ Array of [payment paths](../../../../concepts/tokens/fungible-tokens/paths.md) to be used for this transaction. Must be omitted for XRP-to-XRP transactions. | | `SendMax` | [Currency Amount][] | Amount | No | Highest amount of source currency this transaction is allowed to cost, including [transfer fees](../../../../concepts/tokens/fungible-tokens/transfer-fees.md), exchange rates, and [slippage](http://en.wikipedia.org/wiki/Slippage_%28finance%29). Does not include the [XRP destroyed as a cost for submitting the transaction](../../../../concepts/transactions/transaction-cost.md). Must be supplied for cross-currency/cross-issue payments. Must be omitted for XRP-to-XRP payments. | @@ -145,12 +145,12 @@ In the above example with a ¥95/$15 offer and a ¥5/$2 offer, the situation is ## MPT Payments -_(Requires the [MPTokensV1 amendment][] {% not-enabled /%})_ - When you send a payment using [MPTs](/docs/concepts/tokens/fungible-tokens/multi-purpose-tokens), the _Amount_ field requires only the `mpt_issuance_id` and the `value`. The `MPTokenIssuanceID` is used to uniquely identify the MPT for the transaction. Version 1 MPTokens only support direct MPT payment between accounts. They cannot be traded in the decentralized exchange. +{% amendment-disclaimer name="MPTokensV1" /%} + ### Sample MPT Payment transaction ```json @@ -175,7 +175,7 @@ Version 1 MPTokens only support direct MPT payment between accounts. They cannot ``` ## Credential IDs -_(Requires the [Credentials amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="Credentials" /%} You can send money to an account that uses [Deposit Authorization](../../../../concepts/accounts/depositauth.md) by providing the `CredentialIDs` field with an exact set of credentials that are preauthorized by the recipient. The set of credentials must match a [DepositPreauth entry](../../ledger-data/ledger-entry-types/depositpreauth.md) in the ledger. diff --git a/docs/references/protocol/transactions/types/paymentchannelclaim.md b/docs/references/protocol/transactions/types/paymentchannelclaim.md index 415ef1bd8f7..56bb50710c8 100644 --- a/docs/references/protocol/transactions/types/paymentchannelclaim.md +++ b/docs/references/protocol/transactions/types/paymentchannelclaim.md @@ -7,7 +7,7 @@ labels: # PaymentChannelClaim [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") -Claim funds from a payment channel, adjust the payment channel's expiration, or both. This transaction can be used differently depending on the transaction sender's role in the specified channel: +Claim funds from a [payment channel](../../../../concepts/payment-types/payment-channels.md), adjust the payment channel's expiration, or both. This transaction can be used differently depending on the transaction sender's role in the specified channel: The **source address** of a channel can: @@ -25,7 +25,7 @@ The **destination address** of a channel can: - Cause a channel to be closed if its `Expiration` or `CancelAfter` time is older than the previous ledger's close time. Any validly formed `PaymentChannelClaim` transaction has this effect, regardless of the contents of the transaction. -_(Added by the [PayChan amendment][].)_ +{% amendment-disclaimer name="PayChan" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/paymentchannelcreate.md b/docs/references/protocol/transactions/types/paymentchannelcreate.md index 4fcdbc9c591..90f1f5c62f5 100644 --- a/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -9,7 +9,7 @@ labels: Create a [payment channel](../../../../concepts/payment-types/payment-channels.md) and fund it. The address sending this transaction becomes the "source address" of the payment channel. -_(Added by the [PayChan amendment][].)_ +{% amendment-disclaimer name="PayChan" /%} ## Example {% $frontmatter.seo.title %} JSON @@ -41,7 +41,7 @@ _(Added by the [PayChan amendment][].)_ | `CancelAfter` | Number | UInt32 | No | The time, in [seconds since the Ripple Epoch][], when this channel expires. Any transaction that would modify the channel after this time closes the channel without otherwise affecting it. This value is immutable; the channel can be closed earlier than this time but cannot remain open after this time. | | `DestinationTag` | Number | UInt32 | No | Arbitrary tag to further specify the destination for this payment channel, such as a hosted recipient at the destination address. | -If the `Destination` account is blocking incoming payment channels, the transaction fails with result code `tecNO_PERMISSION`. _(Requires the [DisallowIncoming amendment][] )_ +If the `Destination` account is blocking incoming payment channels, the transaction fails with result code `tecNO_PERMISSION`. {% amendment-disclaimer name="DisallowIncoming" /%} ## See Also diff --git a/docs/references/protocol/transactions/types/paymentchannelfund.md b/docs/references/protocol/transactions/types/paymentchannelfund.md index 48a0c9a1874..8e259aaad29 100644 --- a/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -9,7 +9,7 @@ labels: Add an additional amount to an open [payment channel](../../../../concepts/payment-types/payment-channels.md), and optionally update the expiration time of the channel. Only the source account of the channel can use this transaction. -_(Added by the [PayChan amendment][].)_ +{% amendment-disclaimer name="PayChan" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/permissioneddomaindelete.md b/docs/references/protocol/transactions/types/permissioneddomaindelete.md index a7947a95183..fcf7230b73c 100644 --- a/docs/references/protocol/transactions/types/permissioneddomaindelete.md +++ b/docs/references/protocol/transactions/types/permissioneddomaindelete.md @@ -2,15 +2,16 @@ seo: description: Delete a permissioned domain. labels: - - Compliance - - Permissioned Domains + - Compliance + - Permissioned Domains +status: not_enabled --- # PermissionedDomainDelete [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PermissionedDomainDelete.cpp "Source") Delete a [permissioned domain][] that you own. -_(Requires the [PermissionedDomains amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="PermissionedDomains" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/permissioneddomainset.md b/docs/references/protocol/transactions/types/permissioneddomainset.md index 7734a92cac9..97abb5097c6 100644 --- a/docs/references/protocol/transactions/types/permissioneddomainset.md +++ b/docs/references/protocol/transactions/types/permissioneddomainset.md @@ -2,15 +2,16 @@ seo: description: Create or update a permissioned domain. labels: - - Compliance - - Permissioned Domains + - Compliance + - Permissioned Domains +status: not_enabled --- # PermissionedDomainSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PermissionedDomainSet.cpp "Source") Create a [permissioned domain][], or modify one that you own. -_(Requires the [PermissionedDomains amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="PermissionedDomains" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/setregularkey.md b/docs/references/protocol/transactions/types/setregularkey.md index ff3b7c0bf39..98d36bd9f4d 100644 --- a/docs/references/protocol/transactions/types/setregularkey.md +++ b/docs/references/protocol/transactions/types/setregularkey.md @@ -2,13 +2,13 @@ seo: description: Add, remove, or modify an account's regular key pair. labels: - - Security + - Security --- # SetRegularKey [[Source]](https://github.com/XRPLF/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") -A `SetRegularKey` transaction assigns, changes, or removes the regular key pair associated with an account. +Assign, change, or remove the [regular key pair](../../../../concepts/accounts/cryptographic-keys.md) associated with your account. You can protect your account by assigning a regular key pair to it and using it instead of the master key pair to sign transactions whenever possible. If your regular key pair is compromised, but your master key pair is not, you can use a `SetRegularKey` transaction to regain control of your account. @@ -27,7 +27,6 @@ You can protect your account by assigning a regular key pair to it and using it {% tx-example txid="6AA6F6EAAAB56E65F7F738A9A2A8A7525439D65BA990E9BA08F6F4B1C2D349B4" /%} {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} - | Field | JSON Type | [Internal Type][] | Description | |:-------------|:----------|:------------------|:------------------------------| diff --git a/docs/references/protocol/transactions/types/signerlistset.md b/docs/references/protocol/transactions/types/signerlistset.md index 2f1124e88c7..1c3b606cf11 100644 --- a/docs/references/protocol/transactions/types/signerlistset.md +++ b/docs/references/protocol/transactions/types/signerlistset.md @@ -5,10 +5,12 @@ labels: - Security --- # SignerListSet - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetSignerList.cpp "Source") -The SignerListSet transaction creates, replaces, or removes a list of signers that can be used to [multi-sign](../../../../concepts/accounts/multi-signing.md) a transaction. This transaction type was introduced by the [MultiSign amendment][]. +Create, replace, or remove a list of signers that can be used to [multi-sign](../../../../concepts/accounts/multi-signing.md) a transaction. + +{% amendment-disclaimer name="MultiSign" /%} + ## Example {% $frontmatter.seo.title %} JSON @@ -45,7 +47,6 @@ The SignerListSet transaction creates, replaces, or removes a list of signers th {% tx-example txid="09A9C86BF20695735AB03620EB1C32606635AC3DA0B70282F37C674FC889EFE7" /%} {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} - | Field | JSON Type | [Internal Type][] | Description | |:----------------|:----------|:------------------|:-----------------------------| diff --git a/docs/references/protocol/transactions/types/ticketcreate.md b/docs/references/protocol/transactions/types/ticketcreate.md index a6c7e93dfa5..eb3aba1383e 100644 --- a/docs/references/protocol/transactions/types/ticketcreate.md +++ b/docs/references/protocol/transactions/types/ticketcreate.md @@ -5,12 +5,11 @@ labels: - Transaction Sending --- # TicketCreate - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") -_(Added by the [TicketBatch amendment][].)_ +Set aside one or more [sequence numbers][Sequence Number] as [tickets](../../../../concepts/accounts/tickets.md). -A TicketCreate transaction sets aside one or more [sequence numbers][Sequence Number] as [Tickets](../../../../concepts/accounts/tickets.md). +{% amendment-disclaimer name="TicketBatch" /%} ## Example {% $frontmatter.seo.title %} JSON diff --git a/docs/references/protocol/transactions/types/trustset.md b/docs/references/protocol/transactions/types/trustset.md index 9d3eaf627e3..1726a73b0f6 100644 --- a/docs/references/protocol/transactions/types/trustset.md +++ b/docs/references/protocol/transactions/types/trustset.md @@ -5,7 +5,6 @@ labels: - Tokens --- # TrustSet - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetTrust.cpp "Source") Create or modify a [trust line](../../../../concepts/tokens/fungible-tokens/index.md) linking two accounts. @@ -31,7 +30,6 @@ Create or modify a [trust line](../../../../concepts/tokens/fungible-tokens/inde {% tx-example txid="8566673ECD0A9731C516906E5D2F47129C5C13713602140733831A56CEAE1A05" /%} {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} - | Field | JSON Type | [Internal Type][] | Description | |:-------------------------|:----------|:------------------|:------------------| @@ -42,7 +40,7 @@ Create or modify a [trust line](../../../../concepts/tokens/fungible-tokens/inde | `QualityIn` | Number | UInt32 | _(Optional)_ Value incoming balances on this trust line at the ratio of this number per 1,000,000,000 units. A value of `0` is shorthand for treating balances at face value. For example, if you set the value to 10,000,000, 1% of incoming funds remain with the sender. If an account sends 100 currency, the sender retains 1 currency unit and the destination receives 99 units. This option is included for parity: in practice, you are much more likely to set a `QualityOut` value. Note that this fee is separate and independent from token transfer fees. | | `QualityOut` | Number | UInt32 | _(Optional)_ Value outgoing balances on this trust line at the ratio of this number per 1,000,000,000 units. A value of `0` is shorthand for treating balances at face value. For example, if you set the value to 10,000,000, 1% of outgoing funds would remain with the issuer. If the sender sends 100 currency units, the issuer retains 1 currency unit and the destination receives 99 units. Note that this fee is separate and independent from token transfer fees. | -If the account specified in `LimitAmount.issuer` is blocking incoming trust lines, the transaction fails with the result code `tecNO_PERMISSION`. _(Requires the [DisallowIncoming amendment][] )_ +If the account specified in `LimitAmount.issuer` is blocking incoming trust lines, the transaction fails with the result code `tecNO_PERMISSION`. {% amendment-disclaimer name="DisallowIncoming" /%} ## TrustSet Flags diff --git a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md index 994233e4817..e9c2688e674 100644 --- a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md +++ b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md @@ -8,15 +8,13 @@ status: not_enabled # XChainAccountCreateCommit [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L466-L474 "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -This transaction can only be used for XRP-XRP bridges. - -The `XChainAccountCreateCommit` transaction creates a new account for a witness server to submit transactions on an issuing chain. +Create a new account for a [witness server](../../../../concepts/xrpl-sidechains/witness-servers.md) to submit transactions on an issuing chain. This transaction can only be used for XRP-XRP bridges. {% admonition type="danger" name="Warning" %}This transaction should only be executed if the witness attestations will be reliably delivered to the destination chain. If the signatures aren't delivered, then account creation will be blocked until attestations are received. This can be used maliciously; to disable this transaction on XRP-XRP bridges, omit the bridge's `MinAccountCreateAmount` field.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} + ## Example XChainAccountCreateCommit JSON ```json diff --git a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md index d4b7b3033d2..0fb48fc2edc 100644 --- a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md @@ -8,9 +8,7 @@ status: not_enabled # XChainAddAccountCreateAttestation [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L447-L464 "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainAddAccountCreateAttestation` transaction provides an attestation from a witness server that an `XChainAccountCreateCommit` transaction occurred on the other chain. +Provide an attestation from a [witness server](../../../../concepts/xrpl-sidechains/witness-servers.md) that an `XChainAccountCreateCommit` transaction occurred on the other chain. The signature must be from one of the keys on the door's signer list at the time the signature was provided. If the signature list changes between the time the signature was submitted and the quorum is reached, the new signature set is used and some of the currently collected signatures may be removed. @@ -18,6 +16,7 @@ Any account can submit signatures. {% admonition type="info" name="Note" %}The reward is only sent to accounts that have keys on the current list. A quorum of signers need to agree on the `SignatureReward`, the same way they need to agree on the other data. A single witness server can't provide an incorrect value for this in an attempt to collect a larger reward.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainAddAccountCreateAttestation JSON diff --git a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md index 7c2b6725f00..835e4e88383 100644 --- a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md @@ -8,9 +8,7 @@ status: not_enabled # XChainAddClaimAttestation [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L429-L445 "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainAddClaimAttestation` transaction provides proof from a witness server, attesting to an `XChainCommit` transaction. +Provide proof from a [witness server](../../../../concepts/xrpl-sidechains/witness-servers.md) attesting to an `XChainCommit` transaction. The signature must be from one of the keys on the door's signer list at the time the signature was provided. However, if the signature list changes between the time the signature was submitted and the quorum is reached, the new signature set is used and some of the currently collected signatures may be removed. @@ -18,6 +16,7 @@ Any account can submit signatures. {% admonition type="info" name="Note" %}The reward is only sent to accounts that have keys on the current list. A quorum of signers need to agree on the `SignatureReward`, the same way they need to agree on the other data. A single witness server can't provide an incorrect value for this in an attempt to collect a larger reward.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainAddClaimAttestation JSON diff --git a/docs/references/protocol/transactions/types/xchainclaim.md b/docs/references/protocol/transactions/types/xchainclaim.md index fadd466b480..66b0c9b9a37 100644 --- a/docs/references/protocol/transactions/types/xchainclaim.md +++ b/docs/references/protocol/transactions/types/xchainclaim.md @@ -6,14 +6,13 @@ labels: status: not_enabled --- # XChainClaim -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L418-L427 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainClaim` transaction completes a cross-chain transfer of value. It allows a user to claim the value on the destination chain - the equivalent of the value locked on the source chain. A user can only claim the value if they own the cross-chain claim ID associated with the value locked on the source chain (the `Account` field). The user can send the funds to anyone (the `Destination` field). This transaction is only needed if an `OtherChainDestination` isn't specified in the `XChainCommit` transaction, or if something goes wrong with the automatic transfer of funds. +Complete a [cross-chain transfer of value](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md). It allows a user to claim the value on the destination chain - the equivalent of the value locked on the source chain. A user can only claim the value if they own the cross-chain claim ID associated with the value locked on the source chain (the `Account` field). The user can send the funds to anyone (the `Destination` field). This transaction is only needed if an `OtherChainDestination` isn't specified in the `XChainCommit` transaction, or if something goes wrong with the automatic transfer of funds. If the transaction succeeds in moving funds, the referenced `XChainOwnedClaimID` ledger object will be destroyed. This prevents transaction replay. If the transaction fails, the `XChainOwnedClaimID` won't be destroyed and the transaction can be re-run with different parameters. +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainClaim JSON diff --git a/docs/references/protocol/transactions/types/xchaincommit.md b/docs/references/protocol/transactions/types/xchaincommit.md index bf4e9950787..8eb98218369 100644 --- a/docs/references/protocol/transactions/types/xchaincommit.md +++ b/docs/references/protocol/transactions/types/xchaincommit.md @@ -6,12 +6,14 @@ labels: status: not_enabled --- # XChainCommit -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L408-L416 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +Do the second step in a [cross-chain transfer](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md). This transaciton has two modes: -The `XChainCommit` is the second step in a cross-chain transfer. It puts assets into trust on the locking chain so that they can be wrapped on the issuing chain, or burns wrapped assets on the issuing chain so that they can be returned on the locking chain. +- Put assets into trust on the locking chain so that they can be wrapped on the issuing chain. +- Burns wrapped assets on the issuing chain so that they can be returned on the locking chain. +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainCommit JSON diff --git a/docs/references/protocol/transactions/types/xchaincreatebridge.md b/docs/references/protocol/transactions/types/xchaincreatebridge.md index 477a469ac0b..63c069123a3 100644 --- a/docs/references/protocol/transactions/types/xchaincreatebridge.md +++ b/docs/references/protocol/transactions/types/xchaincreatebridge.md @@ -6,11 +6,9 @@ labels: status: not_enabled --- # XChainCreateBridge -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L381-L388 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainCreateBridge` transaction creates a new `Bridge` ledger object and defines a new cross-chain bridge entrance on the chain that the transaction is submitted on. It includes information about door accounts and assets for the bridge. +Creates a new [cross-chain bridge](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md) on the chain that the transaction is submitted on, providing information about door accounts and assets for the bridge. The transaction must be submitted first by the locking chain door account. To set up a valid bridge, door accounts on both chains must submit this transaction, in addition to setting up witness servers. @@ -18,6 +16,7 @@ The complete production-grade setup would also include a `SignerListSet` transac {% admonition type="info" name="Note" %}Each door account can only have one bridge. This prevents the creation of duplicate bridges for the same asset, which can cause asset imbalances on either chain.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainCreateBridge JSON diff --git a/docs/references/protocol/transactions/types/xchaincreateclaimid.md b/docs/references/protocol/transactions/types/xchaincreateclaimid.md index 597b5aa757e..60cd3370768 100644 --- a/docs/references/protocol/transactions/types/xchaincreateclaimid.md +++ b/docs/references/protocol/transactions/types/xchaincreateclaimid.md @@ -6,16 +6,15 @@ labels: status: not_enabled --- # XChainCreateClaimID -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L399-L406 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainCreateClaimID` transaction creates a new cross-chain claim ID that is used for a cross-chain transfer. A cross-chain claim ID represents *one* cross-chain transfer of value. +Create a new cross-chain claim ID that is used for a [cross-chain transfer](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md). A cross-chain claim ID represents *one* cross-chain transfer of value. This transaction is the first step of a cross-chain transfer of value and is submitted on the destination chain, not the source chain. It also includes the account on the source chain that locks or burns the funds on the source chain. +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainCreateClaimID JSON diff --git a/docs/references/protocol/transactions/types/xchainmodifybridge.md b/docs/references/protocol/transactions/types/xchainmodifybridge.md index 05dcd604f46..87a6a63d4a2 100644 --- a/docs/references/protocol/transactions/types/xchainmodifybridge.md +++ b/docs/references/protocol/transactions/types/xchainmodifybridge.md @@ -6,16 +6,15 @@ labels: status: not_enabled --- # XChainModifyBridge -[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/TxFormats.cpp#L390-L397 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ - -The `XChainModifyBridge` transaction allows bridge managers to modify the parameters of the bridge. They can only change the `SignatureReward` and the `MinAccountCreateAmount`. +Modify the parameters of a [cross-chain bridge](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md). Only managers can send this transaction, and they can only change the `SignatureReward` and the `MinAccountCreateAmount`. This transaction must be sent by the door account and requires the entities that control the witness servers to coordinate and provide the signatures for this transaction. This coordination happens outside the ledger. {% admonition type="info" name="Note" %}You can't modify the signer list for the bridge with this transaction. The signer list is on the door account itself and is changed in the same way signer lists are changed on accounts (via a `SignerListSet` transaction).{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} ## Example XChainModifyBridge JSON diff --git a/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md b/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md index 1409f357cfc..77b4f2f9651 100644 --- a/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md +++ b/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md @@ -14,7 +14,7 @@ steps: ['Connect', 'Generate', 'Acquire tokens', 'Check for AMM', 'Look up AMMCr --- # Create an Automated Market Maker -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} An [Automated Market Maker (AMM)](../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) can be an efficient way to facilitate exchanges between two assets while earning its liquidity providers passive income. This tutorial shows how to create an AMM for a given asset pair. diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md index ac81aa8c945..51a2ccc1005 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md @@ -8,7 +8,7 @@ labels: --- # Set Up an IOU-IOU Bridge -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} Setting up an IOU-IOU bridge enables you to move tokens between chains. diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md index 2f5a2120443..c94ddd0ae9c 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md @@ -8,7 +8,7 @@ labels: --- # Set Up an XRP-XRP Bridge -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} Setting up an XRP-XRP bridge enables you to move XRP between chains. The set up requires using the genesis account on the issuing chain as a door account to submit attestations and create transaction submission accounts for witnesses. diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md b/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md index b588ec505a4..668ad9f9239 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md @@ -8,7 +8,7 @@ labels: --- # Submit Cross-chain Transactions -_(Requires the [XChainBridge amendment][] {% not-enabled /%})_ +{% amendment-disclaimer name="XChainBridge" /%} This tutorial explains how to create a test account on a locking chain (_Devent_), and transfer XRP to an issuing chain (_Sidechain-Devnet_), using a supported [client library](../../../references/client-libraries.md) to query and submit transactions. Witness servers are already set up to monitor the XRP-XRP bridge and submit attestations. diff --git a/docs/use-cases/tokenization/stablecoin-issuer.md b/docs/use-cases/tokenization/stablecoin-issuer.md index 3908140dbdc..bc4fe26b9dd 100644 --- a/docs/use-cases/tokenization/stablecoin-issuer.md +++ b/docs/use-cases/tokenization/stablecoin-issuer.md @@ -159,7 +159,7 @@ See [Enact Global Freeze](../../tutorials/how-tos/use-tokens/enact-global-freeze ### Clawback -_(Requires the [Clawback amendment][] )_ +{% amendment-disclaimer name="Clawback" /%} Clawback is an optional setting that you can choose before you begin to distribute your stablecoin. For regulatory purposes, some issuers _must_ have the ability to recover issued tokens after they are distributed to accounts. For example, if an issuer were to discover that tokens were sent to an account sanctioned for illegal activity, the issuer could recover, or _claw back_, the funds. @@ -206,7 +206,7 @@ Decentralized exchanges (DEXes) are integral to the decentralized finance ecosys ### List on an AMM -_(Added by the [AMM amendment][])_ +{% amendment-disclaimer name="AMM" /%} Automated Market Makers (AMMs) are smart contracts that provide liquidity in the XRP Ledger's decentralized exchange. Each AMM holds a pool of two assets and enables users to swap between them at an exchange rate set by a formula. From e309215ed0a456ced98b54c290599dcce49d908b Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Mon, 6 Oct 2025 12:35:03 -0700 Subject: [PATCH 2/9] Apply suggestions from @maria-robobug review Co-authored-by: Maria Shodunke --- docs/references/protocol/transactions/types/escrowcancel.md | 2 +- docs/references/protocol/transactions/types/escrowfinish.md | 2 +- docs/references/protocol/transactions/types/nftokenburn.md | 2 +- docs/references/protocol/transactions/types/offercancel.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/references/protocol/transactions/types/escrowcancel.md b/docs/references/protocol/transactions/types/escrowcancel.md index 996e766ad52..77bbb1c2622 100644 --- a/docs/references/protocol/transactions/types/escrowcancel.md +++ b/docs/references/protocol/transactions/types/escrowcancel.md @@ -7,7 +7,7 @@ labels: # EscrowCancel [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") -Return funds from an expired [escrow](../../../../concepts/payment-types/escrow.md) to it sender. +Return funds from an expired [escrow](../../../../concepts/payment-types/escrow.md) to its sender. {% amendment-disclaimer name="Escrow" /%} diff --git a/docs/references/protocol/transactions/types/escrowfinish.md b/docs/references/protocol/transactions/types/escrowfinish.md index 04dea5d2119..eb102bcd0bf 100644 --- a/docs/references/protocol/transactions/types/escrowfinish.md +++ b/docs/references/protocol/transactions/types/escrowfinish.md @@ -7,7 +7,7 @@ labels: # EscrowFinish [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") -Deliver XRP from an [escrow](../../../../concepts/payment-types/escrow.md) to the recipient. +Deliver funds from an [escrow](../../../../concepts/payment-types/escrow.md) to the recipient. {% amendment-disclaimer name="Escrow" /%} diff --git a/docs/references/protocol/transactions/types/nftokenburn.md b/docs/references/protocol/transactions/types/nftokenburn.md index a1afb208cc0..13d13597e9a 100644 --- a/docs/references/protocol/transactions/types/nftokenburn.md +++ b/docs/references/protocol/transactions/types/nftokenburn.md @@ -7,7 +7,7 @@ labels: # NFTokenBurn [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenBurn.cpp "Source") -Burn (destroy) a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). The NFT's current holder can always burn it, and if the token's "Burnable" flag is enabled, the issuer and their authorized minter (if they have one) can also burn the NFT. +Burn (destroy) a [non-fungible token (NFT)](../../../../concepts/tokens/nfts/index.md). The NFT's current holder can always burn it, and if the token's **Burnable** flag is enabled, the issuer and their authorized minter (if they have one) can also burn the NFT. If the transaction succeeds, it removes the corresponding [NFToken][] object from the [NFTokenPage entry][] that was storing it. This can cause the pages of an NFT directory to be consolidated. diff --git a/docs/references/protocol/transactions/types/offercancel.md b/docs/references/protocol/transactions/types/offercancel.md index 795d14e105c..e2bc6729aa4 100644 --- a/docs/references/protocol/transactions/types/offercancel.md +++ b/docs/references/protocol/transactions/types/offercancel.md @@ -8,7 +8,7 @@ labels: [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") -Cancel an [offer](../../../../concepts/tokens/decentralized-exchange/offers.md) in the decentralized exchange. +Cancel an [offer](../../../../concepts/tokens/decentralized-exchange/offers.md) to trade in the decentralized exchange. ## Example {% $frontmatter.seo.title %} JSON From 221e5da1eabd01d1e1d922a4127673f970e1f9e1 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 12:41:27 -0700 Subject: [PATCH 3/9] Improve consistency of transaction reference docs --- .../protocol/transactions/types/accountdelete.md | 2 +- docs/references/protocol/transactions/types/accountset.md | 2 +- docs/references/protocol/transactions/types/ammbid.md | 2 +- docs/references/protocol/transactions/types/batch.md | 2 +- .../references/protocol/transactions/types/checkcancel.md | 3 +-- docs/references/protocol/transactions/types/checkcash.md | 3 +-- .../references/protocol/transactions/types/checkcreate.md | 2 +- docs/references/protocol/transactions/types/clawback.md | 2 +- .../protocol/transactions/types/credentialaccept.md | 3 +-- .../protocol/transactions/types/credentialcreate.md | 3 +-- .../protocol/transactions/types/credentialdelete.md | 3 +-- .../protocol/transactions/types/depositpreauth.md | 3 +-- docs/references/protocol/transactions/types/index.md | 6 ++---- .../protocol/transactions/types/nftokenacceptoffer.md | 2 +- .../references/protocol/transactions/types/nftokenburn.md | 2 +- .../protocol/transactions/types/nftokencanceloffer.md | 2 +- .../protocol/transactions/types/nftokencreateoffer.md | 2 +- .../references/protocol/transactions/types/nftokenmint.md | 2 +- .../references/protocol/transactions/types/offercancel.md | 2 +- .../references/protocol/transactions/types/offercreate.md | 2 +- .../protocol/transactions/types/oracledelete.md | 5 ++--- docs/references/protocol/transactions/types/oracleset.md | 2 +- docs/references/protocol/transactions/types/payment.md | 8 ++++---- .../protocol/transactions/types/paymentchannelclaim.md | 2 +- .../protocol/transactions/types/paymentchannelcreate.md | 2 +- .../protocol/transactions/types/paymentchannelfund.md | 2 +- .../protocol/transactions/types/signerlistset.md | 2 +- .../protocol/transactions/types/ticketcreate.md | 2 +- docs/references/protocol/transactions/types/trustset.md | 2 +- .../transactions/types/xchainaccountcreatecommit.md | 4 ++-- .../types/xchainaddaccountcreateattestation.md | 4 ++-- .../transactions/types/xchainaddclaimattestation.md | 4 ++-- .../references/protocol/transactions/types/xchainclaim.md | 4 ++-- .../protocol/transactions/types/xchaincommit.md | 4 ++-- .../protocol/transactions/types/xchaincreatebridge.md | 4 ++-- .../protocol/transactions/types/xchaincreateclaimid.md | 4 ++-- .../protocol/transactions/types/xchainmodifybridge.md | 4 ++-- 37 files changed, 50 insertions(+), 59 deletions(-) diff --git a/docs/references/protocol/transactions/types/accountdelete.md b/docs/references/protocol/transactions/types/accountdelete.md index 11ed6d6fa4e..180bc5a01fa 100644 --- a/docs/references/protocol/transactions/types/accountdelete.md +++ b/docs/references/protocol/transactions/types/accountdelete.md @@ -2,7 +2,7 @@ seo: description: Delete an account. labels: - - Accounts + - Accounts --- # AccountDelete [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") diff --git a/docs/references/protocol/transactions/types/accountset.md b/docs/references/protocol/transactions/types/accountset.md index f4fce041db8..1da61c0c722 100644 --- a/docs/references/protocol/transactions/types/accountset.md +++ b/docs/references/protocol/transactions/types/accountset.md @@ -2,7 +2,7 @@ seo: description: Set options on an account. labels: - - Accounts + - Accounts --- # AccountSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetAccount.cpp "Source") diff --git a/docs/references/protocol/transactions/types/ammbid.md b/docs/references/protocol/transactions/types/ammbid.md index 01bde0e97d6..ecf88fb60c7 100644 --- a/docs/references/protocol/transactions/types/ammbid.md +++ b/docs/references/protocol/transactions/types/ammbid.md @@ -2,7 +2,7 @@ seo: description: Bid on an Automated Market Maker's auction slot, which grants a discounted fee. labels: - - AMM + - AMM --- # AMMBid [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMBid.cpp "Source") diff --git a/docs/references/protocol/transactions/types/batch.md b/docs/references/protocol/transactions/types/batch.md index 02b5eab9f8f..d7d0df02746 100644 --- a/docs/references/protocol/transactions/types/batch.md +++ b/docs/references/protocol/transactions/types/batch.md @@ -2,7 +2,7 @@ seo: description: Create and submit a batch of up to 8 transactions that succeed or fail atomically. labels: - - Transaction Sending + - Transaction Sending status: not_enabled --- # Batch diff --git a/docs/references/protocol/transactions/types/checkcancel.md b/docs/references/protocol/transactions/types/checkcancel.md index b55fd84ff07..a2f8f1ad972 100644 --- a/docs/references/protocol/transactions/types/checkcancel.md +++ b/docs/references/protocol/transactions/types/checkcancel.md @@ -2,7 +2,7 @@ seo: description: Cancel a check. labels: - - Checks + - Checks --- # CheckCancel [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") @@ -24,7 +24,6 @@ Cancels an unredeemed [check](../../../../concepts/payment-types/checks.md), rem {% tx-example txid="D3328000315C6DCEC1426E4E549288E3672752385D86A40D56856DBD10382953" /%} - {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Description | diff --git a/docs/references/protocol/transactions/types/checkcash.md b/docs/references/protocol/transactions/types/checkcash.md index 4d045e77e41..46d54a64b79 100644 --- a/docs/references/protocol/transactions/types/checkcash.md +++ b/docs/references/protocol/transactions/types/checkcash.md @@ -2,7 +2,7 @@ seo: description: Redeem a check. labels: - - Checks + - Checks --- # CheckCash [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CashCheck.cpp "Source") @@ -27,7 +27,6 @@ Since the funds for a check are not guaranteed, redeeming a check can fail becau {% tx-example txid="67B71B13601CDA5402920691841AC27A156463678E106FABD45357175F9FF406" /%} - {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Description | diff --git a/docs/references/protocol/transactions/types/checkcreate.md b/docs/references/protocol/transactions/types/checkcreate.md index 9c2faa2c231..4195a19cec2 100644 --- a/docs/references/protocol/transactions/types/checkcreate.md +++ b/docs/references/protocol/transactions/types/checkcreate.md @@ -2,7 +2,7 @@ seo: description: Create a check. labels: - - Checks + - Checks --- # CheckCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") diff --git a/docs/references/protocol/transactions/types/clawback.md b/docs/references/protocol/transactions/types/clawback.md index d730fda234e..e939a5068ee 100644 --- a/docs/references/protocol/transactions/types/clawback.md +++ b/docs/references/protocol/transactions/types/clawback.md @@ -2,7 +2,7 @@ seo: description: Claw back tokens you've issued. labels: - - Tokens + - Tokens --- # Clawback [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Clawback.cpp "Source") diff --git a/docs/references/protocol/transactions/types/credentialaccept.md b/docs/references/protocol/transactions/types/credentialaccept.md index e6f4ec07ba0..33c97346f8a 100644 --- a/docs/references/protocol/transactions/types/credentialaccept.md +++ b/docs/references/protocol/transactions/types/credentialaccept.md @@ -23,8 +23,7 @@ Accept a [credential](../../../../concepts/decentralized-storage/credentials.md) } ``` - -## CredentialAccept Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} In addition to the [common fields][], CredentialAccept transactions use the following fields: diff --git a/docs/references/protocol/transactions/types/credentialcreate.md b/docs/references/protocol/transactions/types/credentialcreate.md index 1025fe3c170..2bf38741b3b 100644 --- a/docs/references/protocol/transactions/types/credentialcreate.md +++ b/docs/references/protocol/transactions/types/credentialcreate.md @@ -23,8 +23,7 @@ Provisionally issue a [credential](../../../../concepts/decentralized-storage/cr } ``` - -## CredentialCreate Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} In addition to the [common fields][], CredentialCreate transactions use the following fields: diff --git a/docs/references/protocol/transactions/types/credentialdelete.md b/docs/references/protocol/transactions/types/credentialdelete.md index 7c244816da5..b02777ef79b 100644 --- a/docs/references/protocol/transactions/types/credentialdelete.md +++ b/docs/references/protocol/transactions/types/credentialdelete.md @@ -23,8 +23,7 @@ Remove a [credential](../../../../concepts/decentralized-storage/credentials.md) } ``` - -## CredentialDelete Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} In addition to the [common fields][], CredentialDelete transactions use the following fields: diff --git a/docs/references/protocol/transactions/types/depositpreauth.md b/docs/references/protocol/transactions/types/depositpreauth.md index 86e9dfd2081..9face8175a7 100644 --- a/docs/references/protocol/transactions/types/depositpreauth.md +++ b/docs/references/protocol/transactions/types/depositpreauth.md @@ -2,7 +2,7 @@ seo: description: Preauthorize an account to send payments to you. labels: - - Security + - Security --- # DepositPreauth [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") @@ -51,7 +51,6 @@ Grant preauthorization to send payments to your account. This is only useful if {% tx-example txid="CB1BF910C93D050254C049E9003DA1A265C107E0C8DE4A7CFF55FADFD39D5656" /%} - {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | diff --git a/docs/references/protocol/transactions/types/index.md b/docs/references/protocol/transactions/types/index.md index e4b0a1f1586..ffab047e316 100644 --- a/docs/references/protocol/transactions/types/index.md +++ b/docs/references/protocol/transactions/types/index.md @@ -1,12 +1,10 @@ --- -html: transaction-types.html -parent: transaction-formats.html seo: description: All the different types of transactions that the XRP Ledger can process. metadata: - indexPage: true + indexPage: true labels: - - Blockchain + - Blockchain --- # Transaction Types diff --git a/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/docs/references/protocol/transactions/types/nftokenacceptoffer.md index abb16beb733..c0a9244916b 100644 --- a/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -2,7 +2,7 @@ seo: description: Accept an offer to buy or sell an NFT. labels: - - NFTs, Non-fungible Tokens + - NFTs, Non-fungible Tokens --- # NFTokenAcceptOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "Source") diff --git a/docs/references/protocol/transactions/types/nftokenburn.md b/docs/references/protocol/transactions/types/nftokenburn.md index 13d13597e9a..31d33cb0c7a 100644 --- a/docs/references/protocol/transactions/types/nftokenburn.md +++ b/docs/references/protocol/transactions/types/nftokenburn.md @@ -2,7 +2,7 @@ seo: description: Permanently destroy an NFT. labels: - - Non-fungible Tokens, NFTs + - Non-fungible Tokens, NFTs --- # NFTokenBurn [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenBurn.cpp "Source") diff --git a/docs/references/protocol/transactions/types/nftokencanceloffer.md b/docs/references/protocol/transactions/types/nftokencanceloffer.md index 345331a1a02..dd629784285 100644 --- a/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -2,7 +2,7 @@ seo: description: Cancel offers to buy or sell an NFT. labels: - - NFTs, Non-fungible Tokens + - NFTs, Non-fungible Tokens --- # NFTokenCancelOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCancelOffer.cpp "Source") diff --git a/docs/references/protocol/transactions/types/nftokencreateoffer.md b/docs/references/protocol/transactions/types/nftokencreateoffer.md index c374ee803a8..123b82d460a 100644 --- a/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -2,7 +2,7 @@ seo: description: Create an offer to buy or sell an NFT. labels: - - Non-fungible Tokens, NFTs + - Non-fungible Tokens, NFTs --- # NFTokenCreateOffer [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "Source") diff --git a/docs/references/protocol/transactions/types/nftokenmint.md b/docs/references/protocol/transactions/types/nftokenmint.md index 7b710b1d077..35405097440 100644 --- a/docs/references/protocol/transactions/types/nftokenmint.md +++ b/docs/references/protocol/transactions/types/nftokenmint.md @@ -2,7 +2,7 @@ seo: description: Mint a Non-Fungible Token (NFT). labels: - - Non-fungible Tokens, NFTs + - Non-fungible Tokens, NFTs --- # NFTokenMint [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") diff --git a/docs/references/protocol/transactions/types/offercancel.md b/docs/references/protocol/transactions/types/offercancel.md index e2bc6729aa4..154af110540 100644 --- a/docs/references/protocol/transactions/types/offercancel.md +++ b/docs/references/protocol/transactions/types/offercancel.md @@ -2,7 +2,7 @@ seo: description: Cancel an offer to trade in the decentralized exchange. labels: - - Decentralized Exchange + - Decentralized Exchange --- # OfferCancel diff --git a/docs/references/protocol/transactions/types/offercreate.md b/docs/references/protocol/transactions/types/offercreate.md index 1f4dba6cfdd..e6d5f92de9b 100644 --- a/docs/references/protocol/transactions/types/offercreate.md +++ b/docs/references/protocol/transactions/types/offercreate.md @@ -2,7 +2,7 @@ seo: description: Offer to trade currencies in the decentralized exchange; create a limit order. labels: - - Decentralized Exchange + - Decentralized Exchange --- # OfferCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateOffer.cpp "Source") diff --git a/docs/references/protocol/transactions/types/oracledelete.md b/docs/references/protocol/transactions/types/oracledelete.md index 2f81726906d..93f659c522d 100644 --- a/docs/references/protocol/transactions/types/oracledelete.md +++ b/docs/references/protocol/transactions/types/oracledelete.md @@ -2,7 +2,7 @@ seo: description: Delete a price oracle. labels: - - Oracle + - Oracle --- # OracleDelete [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteOracle.cpp "Source") @@ -22,8 +22,7 @@ Delete a [price oracle](../../../../concepts/decentralized-storage/price-oracles } ``` - -## OracleDelete Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | Internal Type | Required? | Description | |--------------------|-----------|---------------|-----------|-------------| diff --git a/docs/references/protocol/transactions/types/oracleset.md b/docs/references/protocol/transactions/types/oracleset.md index bd8247e7f84..6aeb886e423 100644 --- a/docs/references/protocol/transactions/types/oracleset.md +++ b/docs/references/protocol/transactions/types/oracleset.md @@ -2,7 +2,7 @@ seo: description: Create or update a price oracle. labels: - - Oracle + - Oracle --- # OracleSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetOracle.cpp "Source") diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index 716dd404c7e..e559766f8d7 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -2,10 +2,10 @@ seo: description: Send funds to another account, convert between currencies, or create a new account by sending it XRP. labels: - - Payments - - XRP - - Cross-Currency - - Tokens + - Payments + - XRP + - Cross-Currency + - Tokens --- # Payment [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Payment.cpp "Source") diff --git a/docs/references/protocol/transactions/types/paymentchannelclaim.md b/docs/references/protocol/transactions/types/paymentchannelclaim.md index 56bb50710c8..44811d7237d 100644 --- a/docs/references/protocol/transactions/types/paymentchannelclaim.md +++ b/docs/references/protocol/transactions/types/paymentchannelclaim.md @@ -2,7 +2,7 @@ seo: description: Claim funds from a payment channel. labels: - - Payment Channels + - Payment Channels --- # PaymentChannelClaim [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") diff --git a/docs/references/protocol/transactions/types/paymentchannelcreate.md b/docs/references/protocol/transactions/types/paymentchannelcreate.md index 90f1f5c62f5..82c67a2dada 100644 --- a/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -2,7 +2,7 @@ seo: description: Open a new payment channel. labels: - - Payment Channels + - Payment Channels --- # PaymentChannelCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") diff --git a/docs/references/protocol/transactions/types/paymentchannelfund.md b/docs/references/protocol/transactions/types/paymentchannelfund.md index 8e259aaad29..e5a7f94031c 100644 --- a/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -2,7 +2,7 @@ seo: description: Add more funds to a payment channel. labels: - - Payment Channels + - Payment Channels --- # PaymentChannelFund [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") diff --git a/docs/references/protocol/transactions/types/signerlistset.md b/docs/references/protocol/transactions/types/signerlistset.md index 1c3b606cf11..355456c3c89 100644 --- a/docs/references/protocol/transactions/types/signerlistset.md +++ b/docs/references/protocol/transactions/types/signerlistset.md @@ -2,7 +2,7 @@ seo: description: Add, remove, or modify an account's multi-signing list. labels: - - Security + - Security --- # SignerListSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetSignerList.cpp "Source") diff --git a/docs/references/protocol/transactions/types/ticketcreate.md b/docs/references/protocol/transactions/types/ticketcreate.md index eb3aba1383e..cbdd8f99410 100644 --- a/docs/references/protocol/transactions/types/ticketcreate.md +++ b/docs/references/protocol/transactions/types/ticketcreate.md @@ -2,7 +2,7 @@ seo: description: Set aside one or more sequence numbers as tickets. labels: - - Transaction Sending + - Transaction Sending --- # TicketCreate [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") diff --git a/docs/references/protocol/transactions/types/trustset.md b/docs/references/protocol/transactions/types/trustset.md index 1726a73b0f6..a54b07ec1d8 100644 --- a/docs/references/protocol/transactions/types/trustset.md +++ b/docs/references/protocol/transactions/types/trustset.md @@ -2,7 +2,7 @@ seo: description: Add or modify a trust line. labels: - - Tokens + - Tokens --- # TrustSet [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetTrust.cpp "Source") diff --git a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md index e9c2688e674..6e360b79b38 100644 --- a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md +++ b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md @@ -2,7 +2,7 @@ seo: description: Create an account on another chain to serve as a door account for a cross-chain bridge. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainAccountCreateCommit @@ -38,7 +38,7 @@ Create a new account for a [witness server](../../../../concepts/xrpl-sidechains ``` -## XChainAccountCreateCommit Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:------------------|:--------------------|:------------------|:----------| :-----------| diff --git a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md index 0fb48fc2edc..d7154091b9c 100644 --- a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md @@ -2,7 +2,7 @@ seo: description: Provide an attestation that an XChainAccountCreateCommit transaction occurred on another chain, for a cross-chain bridge. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainAddAccountCreateAttestation @@ -49,7 +49,7 @@ Any account can submit signatures. ``` -## XChainAddAccountCreateAttestation Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:---------------------------|:--------------------|:------------------|:----------|:------------| diff --git a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md index 835e4e88383..62ffb70ca0a 100644 --- a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md @@ -2,7 +2,7 @@ seo: description: Provide an attestation that an XChainCommit transaction occurred on another chain, for a cross-chain bridge. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainAddClaimAttestation @@ -69,7 +69,7 @@ Any account can submit signatures. ``` -## XChainAddClaimAttestation Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:---------------------------|:--------------------|:------------------|:----------|-------------| diff --git a/docs/references/protocol/transactions/types/xchainclaim.md b/docs/references/protocol/transactions/types/xchainclaim.md index 66b0c9b9a37..af99bd6d683 100644 --- a/docs/references/protocol/transactions/types/xchainclaim.md +++ b/docs/references/protocol/transactions/types/xchainclaim.md @@ -2,7 +2,7 @@ seo: description: Complete a cross-chain transfer of value by claiming the value on the destination chain. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainClaim @@ -37,7 +37,7 @@ If the transaction succeeds in moving funds, the referenced `XChainOwnedClaimID` ``` -## XChainClaim Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:------------------------|:--------------------|:------------------|:----------|-------------| diff --git a/docs/references/protocol/transactions/types/xchaincommit.md b/docs/references/protocol/transactions/types/xchaincommit.md index 8eb98218369..797f07476db 100644 --- a/docs/references/protocol/transactions/types/xchaincommit.md +++ b/docs/references/protocol/transactions/types/xchaincommit.md @@ -2,7 +2,7 @@ seo: description: Start a cross-chain transfer of value. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainCommit @@ -37,7 +37,7 @@ Do the second step in a [cross-chain transfer](../../../../concepts/xrpl-sidecha ``` -## XChainCommit Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:------------------------|:--------------------|:------------------|:----------|-------------| diff --git a/docs/references/protocol/transactions/types/xchaincreatebridge.md b/docs/references/protocol/transactions/types/xchaincreatebridge.md index 63c069123a3..5d82e1b56ec 100644 --- a/docs/references/protocol/transactions/types/xchaincreatebridge.md +++ b/docs/references/protocol/transactions/types/xchaincreatebridge.md @@ -2,7 +2,7 @@ seo: description: Create a bridge between two chains. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainCreateBridge @@ -40,7 +40,7 @@ The complete production-grade setup would also include a `SignerListSet` transac ``` -## XChainCreateBridge Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:-------------------------|:--------------------|:------------------|:----------|:------------| diff --git a/docs/references/protocol/transactions/types/xchaincreateclaimid.md b/docs/references/protocol/transactions/types/xchaincreateclaimid.md index 60cd3370768..7fc9e02a820 100644 --- a/docs/references/protocol/transactions/types/xchaincreateclaimid.md +++ b/docs/references/protocol/transactions/types/xchaincreateclaimid.md @@ -2,7 +2,7 @@ seo: description: Create a cross-chain claim ID that is used for a cross-chain transfer. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainCreateClaimID @@ -38,7 +38,7 @@ It also includes the account on the source chain that locks or burns the funds o ``` -## XChainCreateClaimID Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:-------------------|:---------------------|:------------------|:----------|-------------| diff --git a/docs/references/protocol/transactions/types/xchainmodifybridge.md b/docs/references/protocol/transactions/types/xchainmodifybridge.md index 87a6a63d4a2..5186f8ba544 100644 --- a/docs/references/protocol/transactions/types/xchainmodifybridge.md +++ b/docs/references/protocol/transactions/types/xchainmodifybridge.md @@ -2,7 +2,7 @@ seo: description: Modify the parameters of a cross-chain bridge. labels: - - Interoperability + - Interoperability status: not_enabled --- # XChainModifyBridge @@ -38,7 +38,7 @@ This transaction must be sent by the door account and requires the entities that ``` -## XChainModifyBridge Fields +{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%} | Field | JSON Type | [Internal Type][] | Required? | Description | |:-------------------------|:--------------------|:------------------|:----------|-------------| From 89249a2f0cdbe90a61da15a1481a4509435a3e6a Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Mon, 6 Oct 2025 12:44:06 -0700 Subject: [PATCH 4/9] Apply more review suggestions Co-authored-by: Maria Shodunke --- .../protocol/ledger-data/ledger-entry-types/accountroot.md | 2 +- .../protocol/transactions/types/xchaincreatebridge.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index f0d37784f0f..f796759c5e0 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -55,7 +55,7 @@ labels: | `RegularKey` | 文字列 | AccountID | いいえ | このアカウントのトランザクションに署名するときにマスターキーの代わりに使用できる[キーペア](../../../../concepts/accounts/cryptographic-keys.md)のアドレス。この値を変更するには[SetRegularKeyトランザクション][]を使用してください。 | | `Sequence` | 数値 | UInt32 | はい | このアカウントの有効な次のトランザクションの[シーケンス番号](../../data-types/basic-data-types.md#アカウントシーケンス) を表します。 | | `TicketCount` | 数値 | UInt32 | いいえ | このアカウントが台帳に保有する[チケット](../../../../concepts/accounts/tickets.md)の数です。これは、アカウントが一度に250 チケットという上限以内に留まることを保証するために自動的に更新されます。このフィールドは、チケットの数がゼロの場合は省略されます。 {% amendment-disclaimer name="TicketBatch" /%} | -| `TickSize` | 数値 | UInt8 | いいえ | このアドレスが発行した通貨が関わるオファーの為替レートに使用する有効桁数。有効な値は`3`以上`15`以下です。_（[TickSize Amendment][]により追加されました。）_ | +| `TickSize` | 数値 | UInt8 | いいえ | このアドレスが発行した通貨が関わるオファーの為替レートに使用する有効桁数。有効な値は`3`以上`15`以下です。{% amendment-disclaimer name="TickSize" /%} | | `TransferRate` | 数値 | UInt32 | いいえ | このアカウントが発行した通貨を他のユーザが相互に送金する際に、これらのユーザに請求する[送金手数料](../../../../concepts/tokens/fungible-tokens/transfer-fees.md)。 | | `WalletLocator` | 文字列 | UInt256 | いいえ | ユーザが設定できる任意の256bit値。 | | `WalletSize` | 数値 | UInt32 | いいえ | 未使用。(コード上ではこのフィールドをサポートしていますが、設定する方法はありません)。 | diff --git a/docs/references/protocol/transactions/types/xchaincreatebridge.md b/docs/references/protocol/transactions/types/xchaincreatebridge.md index 5d82e1b56ec..51204e23659 100644 --- a/docs/references/protocol/transactions/types/xchaincreatebridge.md +++ b/docs/references/protocol/transactions/types/xchaincreatebridge.md @@ -8,7 +8,7 @@ status: not_enabled # XChainCreateBridge [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/XChainBridge.cpp "Source") -Creates a new [cross-chain bridge](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md) on the chain that the transaction is submitted on, providing information about door accounts and assets for the bridge. +Create a new [cross-chain bridge](../../../../concepts/xrpl-sidechains/cross-chain-bridges.md) on the chain that the transaction is submitted on, providing information about door accounts and assets for the bridge. The transaction must be submitted first by the locking chain door account. To set up a valid bridge, door accounts on both chains must submit this transaction, in addition to setting up witness servers. From 317a8ffdfcc4015d7c7605acfe0fedb056330e3f Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 13:39:41 -0700 Subject: [PATCH 5/9] Add an 'Updated' mode for amendment-disclaimer & fix disclaimer font size in tables --- .../docs/concepts/accounts/multi-signing.md | 2 +- @l10n/ja/translations.yaml | 2 ++ @theme/components/Amendments.tsx | 27 ++++++++++++++++++- @theme/markdoc/schema.ts | 5 ++++ @theme/styles.css | 6 +++++ docs/concepts/accounts/multi-signing.md | 4 +-- 6 files changed, 41 insertions(+), 5 deletions(-) diff --git a/@l10n/ja/docs/concepts/accounts/multi-signing.md b/@l10n/ja/docs/concepts/accounts/multi-signing.md index a5273fc1823..c29c22cf887 100644 --- a/@l10n/ja/docs/concepts/accounts/multi-signing.md +++ b/@l10n/ja/docs/concepts/accounts/multi-signing.md @@ -24,7 +24,7 @@ labels: [SignerListSetトランザクション][]は、_署名者リスト_（自分のアドレスからのトランザクションを承認できるアドレスのセット）を定義します。署名者リストには、1～32のアドレスを含めることができます。このリストには、自分のアドレスを含めることはできず、重複して登録することはできません。リストの _Signer Weight_ と _Quorum_ の設定を使用することで、どのような組み合わせでどれだけの署名が必要かを制御することができます。 -_([ExpandedSignerList amendment][]により更新されました。)_ +{% amendment-disclaimer name="ExpandedSignerList" mode="updated" /%} ### Signer Weight diff --git a/@l10n/ja/translations.yaml b/@l10n/ja/translations.yaml index 4dc6d134993..37be36ab776 100644 --- a/@l10n/ja/translations.yaml +++ b/@l10n/ja/translations.yaml @@ -143,6 +143,8 @@ component.amendment-status.requires.1: " " component.amendment-status.requires.2: が必要です。 component.amendment-status.added.1: " " component.amendment-status.added.2: により追加されました。 +component.amendment-status.updated.1: " " +component.amendment-status.updated.2: により更新されました。 # Amendment tracker translations amendment.loading: ロード中Amendments... diff --git a/@theme/components/Amendments.tsx b/@theme/components/Amendments.tsx index b7a3fc914db..d4205a9484f 100644 --- a/@theme/components/Amendments.tsx +++ b/@theme/components/Amendments.tsx @@ -226,7 +226,8 @@ function AmendmentBadge(props: { amendment: Amendment }) { export function AmendmentDisclaimer(props: { name: string, - compact: boolean + compact: boolean, + mode: string }) { const [amendmentStatus, setStatus] = React.useState(null) const [loading, setLoading] = React.useState(true) @@ -310,6 +311,30 @@ export function AmendmentDisclaimer(props: { ) } + + if (props.mode === "updated") { + return ( +

( + { + amendmentStatus.date ? ( + <> + {translate("component.amendment-status.updated.1", "Updated by the ")}{link()} + {translate("component.amendment-status.updated.2", ".")} + {" "} + + + ) : ( + <> + {translate("component.amendment-status.updates.1", "The ")}{link()} + {translate("component.amendment-status.updates.2", "updates this.")} + {" "} + + + ) + } + )

+ ) + } return (

( diff --git a/@theme/markdoc/schema.ts b/@theme/markdoc/schema.ts index 6e4b2539617..c053d8a2c5d 100644 --- a/@theme/markdoc/schema.ts +++ b/@theme/markdoc/schema.ts @@ -233,6 +233,11 @@ export const amendmentDisclaimer: Schema & { tagName: string } = { type: 'Boolean', required: false, default: false + }, + mode: { + type: 'String', + required: false, + default: '' // empty string for "Requires ... / Added by ..." } }, render: 'AmendmentDisclaimer', diff --git a/@theme/styles.css b/@theme/styles.css index 90b191b92dc..adfacca4699 100644 --- a/@theme/styles.css +++ b/@theme/styles.css @@ -342,6 +342,12 @@ ul.nav.navbar-nav { [data-component-name="Markdown/Markdown"] { --md-table-font-size: 14px; + --md-table-line-height: 1.5; +} + +[data-component-name="Markdown/Markdown"] td p { + font-size: var(--md-table-font-size); + line-height: var(--md-table-line-height); } @media screen and (min-width: 990px) { diff --git a/docs/concepts/accounts/multi-signing.md b/docs/concepts/accounts/multi-signing.md index f4e00fa7b3c..05ded81834e 100644 --- a/docs/concepts/accounts/multi-signing.md +++ b/docs/concepts/accounts/multi-signing.md @@ -1,6 +1,4 @@ --- -html: multi-signing.html -parent: accounts.html seo: description: Use multi-signing for greater security sending transactions. labels: @@ -23,7 +21,7 @@ Before you can multi-sign, you must create a list of which addresses can sign fo The [SignerListSet transaction][] defines a _signer list_, a set of addresses that can authorize transactions from your address. You can include 1 to 32 addresses in a signer list. The list cannot include your address and there can be no duplicate entries. You can control how many signatures are needed, in which combinations, by using the _Signer Weight_ and _Quorum_ settings in the list. -_(Updated by the [ExpandedSignerList amendment][].)_ +{% amendment-disclaimer name="ExpandedSignerList" mode="updated" /%} ### Signer Weight From 259994d74f74fed83e614dfe6c18a6496a2dad9e Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 13:52:39 -0700 Subject: [PATCH 6/9] Migrate more amendment disclaimers to component --- .../ja/docs/concepts/accounts/depositauth.md | 22 +++++++++---------- .../tokens/decentralized-exchange/ticksize.md | 10 ++++----- .../fungible-tokens/authorized-trust-lines.md | 3 ++- .../concepts/tokens/fungible-tokens/index.md | 2 +- .../ledger-entry-types/amendments.md | 8 +++---- .../ledger-data/ledger-entry-types/amm.md | 11 ++++------ .../ledger-entry-types/directorynode.md | 4 ++-- .../ledger-data/ledger-entry-types/escrow.md | 8 +++---- .../ledger-entry-types/feesettings.md | 8 +++---- .../ledger-entry-types/negativeunl.md | 12 +++++----- .../ledger-entry-types/paychannel.md | 7 ++---- .../ledger-entry-types/signerlist.md | 9 +++----- .../transaction-results/tec-codes.md | 10 ++++----- .../transaction-results/tef-codes.md | 2 +- .../protocol/transactions/types/accountset.md | 8 +++---- .../transactions/types/depositpreauth.md | 2 +- .../transactions/types/escrowcancel.md | 5 ++--- .../transactions/types/escrowcreate.md | 5 ++--- .../transactions/types/escrowfinish.md | 6 ++--- .../transactions/types/paymentchannelclaim.md | 6 ++--- .../types/paymentchannelcreate.md | 6 ++--- .../transactions/types/paymentchannelfund.md | 6 ++--- .../fungible-tokens/trust-line-tokens.md | 2 +- 23 files changed, 66 insertions(+), 96 deletions(-) diff --git a/@l10n/ja/docs/concepts/accounts/depositauth.md b/@l10n/ja/docs/concepts/accounts/depositauth.md index 7119ad1d023..2f9ede74aa9 100644 --- a/@l10n/ja/docs/concepts/accounts/depositauth.md +++ b/@l10n/ja/docs/concepts/accounts/depositauth.md @@ -1,17 +1,13 @@ --- -html: depositauth.html -parent: accounts.html seo: description: DepositAuth設定をすると、アカウントは着信ペイメントをデフォルトでブロックします。 labels: - - セキュリティ - - 支払い + - セキュリティ + - 支払い outdated_translation: true　 --- # Deposit Authorization -_（[DepositAuth Amendment][]により追加されました。）_ - Deposit Authorizationは、XRP Ledgerの[アカウント](index.md)のオプション機能です。Deposit Authorizationが有効な場合、トランザクションはそのトランザクションの送信者がアカウント自体でない限り、アカウントへはどのような資産も送信できません。Deposit Authorizationのアカウントは、次の2つの方法でのみ入金することができます。 - [事前承認](#事前承認)されたアカウントから。 @@ -19,6 +15,8 @@ Deposit Authorizationは、XRP Ledgerの[アカウント](index.md)のオプシ デフォルトでは、新しいアカウントではDepositAuthが無効になっています。 +{% amendment-disclaimer name="DepositAuth" /%} + ## 背景 金融サービスの規制やライセンスによっては、企業や組織に対して、受領するすべてのトランザクションの送信者を把握するよう義務付けています。これは、自由に生成できる偽名で参加者を識別し、デフォルトですべてのアドレスからあらゆる宛先への支払いを可能とするXRP Ledgerのような分散型システムとっては課題となります。 @@ -27,7 +25,7 @@ Deposit Authorizationフラグにより、XRP Ledgerを使用するユーザが Deposit Authorizationを有効にすると、[Checks](/resources/known-amendments.md#checks)、[Escrow](../payment-types/escrow.md)、および[Payment Channel](/resources/known-amendments.md#paychan)から資金を受領できます。このような「二段階」トランザクションモデルでは、最初に送金元は資金の送金を承認するトランザクションを送信し、次に送金先は資金受領を承認するトランザクションを送信します。 -Deposit Authorizationが有効になっている場合に[Paymentトランザクション][]から資金を受領するには、このような支払の送金元を[事前承認](#事前承認)する必要があります。_（[DepositPreauth Amendment][]により追加されました。）_ +Deposit Authorizationが有効になっている場合に[Paymentトランザクション][]から資金を受領するには、このような支払の送金元を[事前承認](#事前承認)する必要があります。{% amendment-disclaimer name="DepositPreauth" /%} ## 推奨される使い方 @@ -42,15 +40,15 @@ Deposit Authorizationを最大限に活用するため、以下の実施を推 Deposit Authorizationが有効化されているアカウントの特徴は次のとおりです。 - [Paymentトランザクション][]の送信先には**できません**。ただし**以下の例外**は除きます。 - - 送金先により、支払の送金元が[事前承認](#事前承認)されている場合。_（[DepositPreauth Amendment][]により追加されました。）_ + - 送金先により、支払の送金元が[事前承認](#事前承認)されている場合。{% amendment-disclaimer name="DepositPreauth" /%} - アカウントのXRP残高がアカウントの最低[必要準備金](reserves.md)以下で、XRP PaymentのAmountがアカウントの最低準備金（現時点では10XRP）以下である場合は、このアカウントを送金先に指定できます。これにより、アカウントがトランザクションを送信することも、XRPを受領することもできずに操作不可能な状態になるのを防ぎます。この場合、アカウントの所有者の準備金は関係ありません。 - **以下に該当する場合にのみ**[PaymentChannelClaimトランザクション][]からXRPを受領できます。 - PaymentChannelClaimトランザクションの送金元がPayment Channelの送金先である場合。 - - PaymentChannelClaimトランザクションの送金先がPaymentChannelClaimの送金元を[事前承認している](#事前承認)場合。_（[DepositPreauth Amendment][]により追加されました。）_ + - PaymentChannelClaimトランザクションの送金先がPaymentChannelClaimの送金元を[事前承認している](#事前承認)場合。{% amendment-disclaimer name="DepositPreauth" /%} - **以下に該当する場合にのみ**[EscrowFinishトランザクション][]からXRPを受領できます。 - EscrowFinishトランザクションの送金元がEscrowの送金先である場合。 - - EscrowFinishトランザクションの送金先がEscrowFinishの送金元を[事前承認している](#事前承認)場合。_（[DepositPreauth Amendment][]により追加されました。）_ -- [CheckCash][]トランザクションを送信してXRPまたはトークンを受領**できます**。 _（[Checks Amendment][]により追加されました。）_ + - EscrowFinishトランザクションの送金先がEscrowFinishの送金元を[事前承認している](#事前承認)場合。{% amendment-disclaimer name="DepositPreauth" /%} +- [CheckCash][]トランザクションを送信してXRPまたはトークンを受領**できます**。 {% amendment-disclaimer name="Checks" /%} - [OfferCreateトランザクション][]を送信してXRPまたはトークンを受領**できます**。 - 即時には完全に実行されないOfferCreateトランザクションがアカウントから送信される場合、このアカウントは、後でオファーが他のアカウントの[Payment][]トランザクションと[OfferCreate][]トランザクションによって消費される時点で、注文済みXRPとトークンのリマインダーを受信する**ことがあります**。 - アカウントが[NoRippleフラグ](../tokens/fungible-tokens/rippling.md)を有効にせずにトラストラインを作成している場合、またはDefaultRippleフラグを有効にして通貨を発行した場合は、アカウントはRipplingの結果として、[Paymentトランザクション][]でそれらのトラストラインのトークンを受領**できます**。このようなトランザクションの送金先にすることはできません。 @@ -80,7 +78,7 @@ Deposit Authorizationが有効化されているアカウントの特徴は次 ## 事前承認 -_（[DepositPreauth Amendment][]により追加されました。）_ +{% amendment-disclaimer name="DepositPreauth" /%} DepositAuthが有効なアカウントは、特定の送金元を _事前承認_ することにより、DepositAuthが有効になっていても、これらの送金元からの支払を受領することができます。これにより、特定の送金元からの資金の直接送金が可能となり、受取人はトランザクションごとに個別にアクションを実行する必要がなくなります。事前承認はDepositAuthの使用にあたり必須の要件ではありませんが、事前承認により特定の操作を実行しやすくなります。 diff --git a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/ticksize.md b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/ticksize.md index 30b5b0003d9..a5317f95b14 100644 --- a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/ticksize.md +++ b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/ticksize.md @@ -1,16 +1,12 @@ --- -html: ticksize.html -parent: decentralized-exchange.html seo: description: 発行者は、為替レートのごくわずかな差を超えて、頻繁な取引を抑制するためにオーダーブックで通貨のカスタムチックサイズを設定することができます。 labels: - - 分散型取引所 - - トークン + - 分散型取引所 + - トークン --- # ティックサイズ -_（[TickSize Amendment][]により追加されました。）_ - オファーがオーダーブックに対して発行されると、そのオファーに関係する通貨の発行者によって設定された`TickSize`の値に基づいて、為替レートが切り捨てられます。トレーダーがXRPとトークンを交換するオファーを出した場合は、そのトークンの発行者からの`TickSize`が適用されます。トレーダーが2種類のトークンを交換するオファーを出した場合は、小さい方の`TickSize`の値（有効数字の桁数が少ない値）がこのオファーに適用されます。いずれの通貨にも`TickSize`が設定されていない場合、デフォルトが適用されます。 オーダーブックにオファーが発行されると、`TickSize` によりオファーの為替レートの _有効数字_ の桁数が切り捨てられます。発行者は[AccountSetトランザクション][]を使用して`TickSize`を`3`～`15`の整数に設定できます。為替レートは有効数字と指数で表されますが、`TickSize`は指数には影響しません。これにより、XRP Ledgerでは価値が大きく異なる資産（ハイパーインフレ通貨と希少通貨など）間の為替レートを表せます。発行者が設定する`TickSize`が小さいほど、トレーダーはより多くの増分をオファーして、既存のオファーよりも高い為替レートと見えるようにする必要があります。 @@ -19,6 +15,8 @@ _（[TickSize Amendment][]により追加されました。）_ 発行者が`TickSize`を有効化、無効化、または変更する場合、以前の設定で発行されたオファーはその影響を受けません。 +{% amendment-disclaimer name="TickSize" /%} + ## 参照項目 - [Dev Blog: Introducing the TickSize Amendment](https://ripple.com/dev-blog/ticksize-amendment-open-voting/#ticksize-amendment-overview) diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md index c82b42d8781..e920e59a22f 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/authorized-trust-lines.md @@ -28,7 +28,8 @@ XRP Ledger上のステーブルコインと認可トラストラインの使用 3. 顧客は[TrustSetトランザクション][]を送信し、発行者のアドレスにトラストラインを作成し、正のリミットを設定します。 4. 発行者はTrustSetトランザクションを送信し、顧客のトラストラインを認可します。 -{% admonition type="success" name="ヒント" %}2つのTrustSetトランザクション（ステップ3および4）は、どちらの順序で発生しても構いません。発行者がトラストラインを先に認可した場合、これにより限度額が0に設定されたトラストラインが作成され、顧客のTrustSetトランザクションは、事前に認可されたトラストラインの限度額を設定することになります。([TrustSetAuth amendment][]により追加されました。)_{% /admonition %} +{% admonition type="success" name="ヒント" %}2つのTrustSetトランザクション（ステップ3および4）は、どちらの順序で発生しても構いません。発行者がトラストラインを先に認可した場合、これにより限度額が0に設定されたトラストラインが作成され、顧客のTrustSetトランザクションは、事前に認可されたトラストラインの限度額を設定することになります。{% /admonition %} + ## 注意事項 認可トラストラインを使用するつもりがない場合でも、[運用アカウントと予備アカウント](../../accounts/account-types.md)のRequire Auth設定を有効にし、これらのアカウントにトラストラインを認可させないようにすることができます。これは、これらのアカウントが誤ってトークンを発行することを防止します（たとえば、ユーザが誤って間違ったアドレスをトラストしてしまった場合など）。これはあくまで予防措置であり、運用アカウントと予備アカウントが意図したとおりに _発行者の_ トークンを転送することを止めるものではありません。 diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md index 32f8718156c..1c7967eddf8 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md @@ -41,7 +41,7 @@ labels: 1. [トレード](../decentralized-exchange/index.md)によって、限度額以上のトークンを取得した場合 2. プラスの残高があるトラストラインの限度額を減らした場合 -3. [チェックの現金化](../../payment-types/checks.md)によって、トークンを限度額以上取得する場合 (_[CheckCashMakesTrustLine amendment][]により追加されました。_) +3. [チェックの現金化](../../payment-types/checks.md)によって、トークンを限度額以上取得する場合 {% amendment-disclaimer name="CheckCashMakesTrustLine" /%} ## トラストラインの設定 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md index dd162e4e7c7..bfa8d810c12 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md @@ -1,10 +1,8 @@ --- -html: amendments-object.html #amendments.html is taken by the concept page -parent: ledger-entry-types.html seo: description: 有効化されているAmendmentと保留中のAmendmentのステータスを持つシングルトンオブジェクトです。 labels: - - ブロックチェーン + - ブロックチェーン --- # Amendments [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L110-L113 "Source") @@ -54,8 +52,8 @@ labels: | `Flags` | 数値 | UInt32 | はい | ブール値フラグのビットマップ。Amendmentオブジェクトタイプにはフラグが定義されていないため、この値は常に`0`です。 | | `LedgerEntryType` | 文字列 | UInt16 | はい | 値が`0x0066`（文字列`Amendments`にマッピング）の場合は、このオブジェクトがXRP **Ledgerに対するAmendmentのステータスを記述していることを示します**。 | | `Majorities` | 配列 | Array | いいえ | _（省略可）_ 過半数の支持を得ているがまだ有効になっていないAmendmentのステータスを記述するオブジェクトの配列。省略されている場合は、過半数の支持を得ている保留中のAmendmentがありません。 | -| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。_（[fixPreviousTxnID amendment][]により追加されました。）_ | -| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。_（[fixPreviousTxnID amendment][]により追加されました。）_ | +| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。{% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。{% amendment-disclaimer name="fixPreviousTxnID" /%} | `Majorities`フィールドにメンバーが含まれている場合、各メンバーは`Majority`フィールドのみが含まれているオブジェクトです。このフィールドの内容は、以下のフィールドからなるネストオブジェクトです。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md index a5f5a4d276f..929c5a9cad3 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md @@ -1,18 +1,15 @@ --- -html: amm.html -parent: ledger-entry-types.html seo: description: 自動マーケットメーカー（AMM）インスタンスの定義と詳細。 labels: - - AMM + - AMM --- # AMM [[ソース]](https://github.com/xrplf/rippled/blob/c1e4bfb08bcc9f187d794a71d653003a6148dc68/src/ripple/protocol/impl/LedgerFormats.cpp#L265-L275 "Source") -{% amendment-disclaimer name="AMM" /%} - `AMM`レジャーエントリは、単一の[自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)インスタンスを表します。これは常に[特殊なAccountRootエントリ](accountroot.md#ammの特殊なaccountrootエントリ)と対になっています。 +{% amendment-disclaimer name="AMM" /%} ## AMMのJSONの例 @@ -70,8 +67,8 @@ labels: | `Account` | 文字列 | AccountID | はい | このAMMの資産を保有する[特殊なアカウント](accountroot.md#ammの特殊なaccountrootエントリ)のアドレス。 | | `AuctionSlot` | オブジェクト | Object | いいえ | オークションスロットの現在の所有者の詳細。[オークションスロットオブジェクト](#オークションスロットオブジェクト)形式です。| | `LPTokenBalance` | [通貨額][] | Amount | はい | AMMインスタンスの流動性供給者トークンの発行残高の合計。このトークンの保有者は、保有量に比例してAMMの取引手数料に投票したり、取引手数料の徴収とともに増えていくAMMの資産の一部とトークンを交換したりすることができます。 | -| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。_（[fixPreviousTxnID amendment][]により追加されました。）_ | -| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。_（[fixPreviousTxnID amendment][]により追加されました。）_ | +| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。{% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。{% amendment-disclaimer name="fixPreviousTxnID" /%} | | `TradingFee` | 数値 | UInt16 | はい | AMMインスタンスに対する取引に課される手数料のパーセンテージを1/100,000の単位で指定します。最大値は1000で、これは1%の手数料となります。 | | `VoteSlots` | 配列 | Array | いいえ | プールの取引手数料に関する投票を表す、投票オブジェクトのリスト。| diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md index 2568ff24103..7f887940937 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md @@ -104,8 +104,8 @@ labels: | `LedgerEntryType` | 文字列 | UInt16 | はい | 値が`0x0064`（文字列`DirectoryNode`にマッピング）の場合は、このオブジェクトがディレクトリの一部であることを示します。 | | `NFTokenID` | 文字列 | UInt256 | いいえ |(NFTオファーディレクトリのみ) 購入または売却オファーに紐づくNFTのID。. | | `Owner` | 文字列 | AccountID | いいえ | （所有者ディレクトリのみ）このディレクトリ内のオブジェクトを所有するアカウントのアドレス。 | -| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。_（[fixPreviousTxnID amendment][]により追加されました。）_ | -| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。_（[fixPreviousTxnID amendment][]により追加されました。）_ | +| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。{% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。{% amendment-disclaimer name="fixPreviousTxnID" /%} | | `RootIndex` | 文字列 | UInt256 | はい | このディレクトリのルートオブジェクトのID。 | | `TakerGetsCurrency` | 文字列 | UInt160 | いいえ | （オファーディレクトリのみ）このディレクトリのオファーのTakerGetsの額の通貨コード。 | | `TakerGetsIssuer` | 文字列 | UInt160 | いいえ | （オファーディレクトリのみ）このディレクトリのオファーのTakerGetsの額のイシュアー。 | diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md index b7b87c2c71c..3b0e47ab4a0 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md @@ -1,18 +1,16 @@ --- -html: escrow-object.html #escrow.html is taken by the concept page -parent: ledger-entry-types.html seo: description: 条件付き決済のために保有されているXRPを含みます。 labels: - - Escrow + - Escrow --- # Escrow [[ソース]](https://github.com/XRPLF/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") -_（[Escrow Amendment][]により追加されました。）_ - `Escrow`レジャーエントリは特定の条件が満たされるまでXRPを保持する1つの[エスクロー](../../../../concepts/payment-types/escrow.md)を表します。 +{% amendment-disclaimer name="Escrow" /%} + ## {% $frontmatter.seo.title %}のJSONの例 ```json diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md index c4acbb829ef..570e697c294 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md @@ -1,10 +1,8 @@ --- -html: feesettings.html -parent: ledger-entry-types.html seo: description: コンセンサスで承認された基本トランザクションコストと必要準備金があるシングルトンオブジェクトです。 labels: - - 手数料 + - 手数料 --- # FeeSettings [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") @@ -39,8 +37,8 @@ labels: | `ReferenceFeeUnits` | 数値 | UInt32 | 「手数料単位」に変換された`BaseFee` | | `ReserveBase` | 数値 | UInt32 | XRP Ledgerのアカウントの[基本準備金](../../../../concepts/accounts/reserves.md#基本準備金と所有者準備金)（XRPのdrop数）。 | | `ReserveIncrement` | 数値 | UInt32 | 所有するオブジェクトごとに増加する[所有者準備金](../../../../concepts/accounts/reserves.md#基本準備金と所有者準備金)（XRPのdrop数）。 | -| `PreviousTxnID` | 文字列 | UInt256 | このエントリを最後に変更したトランザクションの識別ハッシュ。_（[fixPreviousTxnID amendment][]により追加されました。）_ | -| `PreviousTxnLgrSeq` | 数値 | UInt32 | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。_（[fixPreviousTxnID amendment][]により追加されました。）_ | +| `PreviousTxnID` | 文字列 | UInt256 | このエントリを最後に変更したトランザクションの識別ハッシュ。{% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | 数値 | UInt32 | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。{% amendment-disclaimer name="fixPreviousTxnID" /%} | {% admonition type="danger" name="警告" %}このレジャーオブジェクトのJSONフォーマットは一般的ではありません。`BaseFee`、`ReserveBase`、および`ReserveIncrement`はXRPのdrop数を示しますが、通常の[XRP指定][通貨額]フォーマットでは***ありません*** 。{% /admonition %} diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md index 80131a8e3a9..ff1594ee5ef 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md @@ -1,19 +1,17 @@ --- -html: negativeunl.html -parent: ledger-entry-types.html seo: description: 現在オフラインと思われるバリデータの一覧を表します。 labels: - - ブロックチェーン + - ブロックチェーン --- # NegativeUNL -{% amendment-disclaimer name="NegativeUNL" /%} - `NegativeUNL`オブジェクトタイプは、[ネガティブUNL](../../../../concepts/consensus-protocol/negative-unl.md)の現在の状態、つまり現在オフラインであると考えられる信頼できるバリデーションのリストを含んでいます。 各台帳のバージョンには、**最大1つの**`NegativeUNL`オブジェクトが含まれます。無効になっているか、無効になる予定のバリデータがない場合、台帳には`NegativeUNL`オブジェクトは存在しません。 +{% amendment-disclaimer name="NegativeUNL" /%} + ## {% $frontmatter.seo.title %} JSONの例 ```json @@ -42,8 +40,8 @@ labels: | `DisabledValidators` | 配列 | Array | いいえ | `DisabledValidator`オブジェクト(下記参照)は、現在無効になっている信頼できるバリデータを表すリストです。 | | `Flags` | 数値 | UInt32 | はい | 真偽値フラグのビットマップ。NegativeUNLオブジェクトタイプにはフラグが定義されていないため、この値は常に`0`となります。 | | `LedgerEntryType` | 文字列 | UInt16 | はい | `0x004E`は文字列`NegativeUNL`に対応し、このオブジェクトがNegativeUNLであることを意味します。 | -| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。_（[fixPreviousTxnID amendment][]により追加されました。）_ | -| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。_（[fixPreviousTxnID amendment][]により追加されました。）_ | +| `PreviousTxnID` | 文字列 | UInt256 | いいえ | このエントリを最後に変更したトランザクションの識別ハッシュ。{% amendment-disclaimer name="fixPreviousTxnID" /%} | +| `PreviousTxnLgrSeq` | 数値 | UInt32 | いいえ | このエントリを最後に変更したトランザクションが含まれる[レジャーインデックス](../ledger-header.md)。{% amendment-disclaimer name="fixPreviousTxnID" /%} | | `ValidatorToDisable` | 文字列 | Blob | いいえ | 次回のフラグレジャーで無効化される予定の信頼できるバリデータの公開鍵を表します。 | | `ValidatorToReEnable` | 文字列 | Blob | いいえ | 次回のフラグレジャーで再有効化される予定のネガティブUNLの信頼できるバリデータの公開鍵を表します。 | diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md index d8a4f7fe62d..8d5287c6c7b 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md @@ -1,18 +1,15 @@ --- -html: paychannel.html -parent: ledger-entry-types.html seo: description: 非同期XRP支払い用のチャネルです。 labels: - - Payment Channel + - Payment Channel --- # PayChannel [[ソース]](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") -_（[PayChan Amendment][]により追加されました。）_ - `PayChannel`エントリは1つの[支払いチャネル](../../../../concepts/payment-types/payment-channels.md)を表します。 +{% amendment-disclaimer name="PayChan" /%} ## {% $frontmatter.seo.title %}のJSONの例 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md index b922a0f3e54..bdfb01aeea4 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md @@ -1,18 +1,15 @@ --- -html: signerlist.html -parent: ledger-entry-types.html seo: description: マルチシグトランザクションのアドレスのリストです。 labels: - - セキュリティ + - セキュリティ --- # SignerList [[ソース]](https://github.com/XRPLF/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") -_（[MultiSign Amendment][]により追加されました。）_ - `SignerList`オブジェクトタイプは、個別アカウントの代わりにグループとしてトランザクション署名をすることが承認されている署名者のリストです。[SignerListSetトランザクション][]を使用して、SignerListを作成、置き換え、または削除できます。 +{% amendment-disclaimer name="MultiSign" /%} ## {% $frontmatter.seo.title %}のJSONの例 @@ -74,7 +71,7 @@ _（[MultiSign Amendment][]により追加されました。）_ |:---------------|:----------|:--------------|:--------------------------------| | `Account` | 文字列 | AccountID | 署名がマルチシグに提供されるXRP Ledgerアドレス。レジャーの資金供給のあるアドレスである必要はありません。 | | `SignerWeight` | 数値 | UInt16 | この署名者による署名の重み。マルチシグは、付与された署名の重みの合計がSignerListの`SignerQuorum`値を超えている場合にのみ有効となります。 | -| `WalletLocator` | 文字列 | UInt256 | （省略可）任意の16進数データ。これは署名者を識別するため、または他の関連する目的のために使用することができます。[ExpandedSignerList amendment][]により追加されました。 | +| `WalletLocator` | 文字列 | UInt256 | （省略可）任意の16進数データ。これは署名者を識別するため、または他の関連する目的のために使用することができます。{% amendment-disclaimer name="ExpandedSignerList" /%} | マルチシグトランザクションを処理する際に、サーバはトランザクション実行時にレジャーに関する`Account`値を間接参照します。アドレスが資金供給のある[AccountRootオブジェクト](accountroot.md)に対応して _いない_ 場合、そのアドレスに関連付けられているマスターシークレットによってのみ有効な署名を生成できます。アカウントがレジャーに _確かに_ 存在している場合は、アカウントの状態により異なります。アカウントにレギュラーキーが設定されている場合はレギュラーキーを使用できます。アカウントのマスターキーが無効化されていない場合に限り、アカウントのマスターキーを使用できます。マルチシグを別のマルチシグの一部として使用することはできません。 diff --git a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md index 809622c0318..dc0e9997b4a 100644 --- a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -1,10 +1,8 @@ --- -html: tec-codes.html -parent: transaction-results.html seo: description: tecコードは、トランザクションは失敗したものの、トランザクションコストを適用するために、このトランザクションがレジャーに適用されたことを示します。 labels: - - トランザクション送信 + - トランザクション送信 --- # tecコード [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TER.cpp "ソース") @@ -30,7 +28,7 @@ labels: | `tecDIR_FULL` | 121 | トランザクションがアカウントの所有者ディレクトリにオブジェクト（トラストライン、Check、Escrow、Payment Channelなど）を追加しようと試みましたが、このアカウントはレジャーにこれ以上のオブジェクトを所有できません。 | | `tecDUPLICATE` | 149 | トランザクションが、すでに存在するオブジェクト（[DepositPreauth][]の承認など）を作成しようとしました。 | | `tecDST_TAG_NEEDED` | 143 | [Paymentトランザクション][]の宛先タグが省略されましたが、支払先アカウントでは`lsfRequireDestTag`フラグが有効になっています。 | -| `tecEMPTY_DID` | 187 | トランザクションが[DIDエントリ](../../ledger-data/ledger-entry-types/did.md)を作成しようとしましたが、内容が空でした。DIDは空にできません。 _([DID amendment][] {% not-enabled /%}により追加されました。)_ | +| `tecEMPTY_DID` | 187 | トランザクションが[DIDエントリ](../../ledger-data/ledger-entry-types/did.md)を作成しようとしましたが、内容が空でした。DIDは空にできません。 {% amendment-disclaimer name="DID" /%} | | `tecEXPIRED` | 148 | トランザクションがオブジェクト（OfferやCheckなど）を作成しようとしましたが、そのオブジェクトで指定された有効期限がすでに経過しています。 | | `tecFAILED_PROCESSING` | 105 | トランザクションの処理中に不明なエラーが発生しました。 | | `tecFROZEN` | 137 | [OfferCreateトランザクション][]が失敗しました。関係する1つまたは両方の資産が[Global Freeze](../../../../concepts/tokens/fungible-tokens/freezes.md)の対象となっています。 | @@ -42,8 +40,8 @@ labels: | `tecINSUFFICIENT_PAYMENT` | 161 | 指定された金額は、トランザクションに関わるすべての料金を支払うには十分ではありません。例えば、非代替性トークンを取引する場合、購入金額はブローカー手数料と販売金額の両方を支払うには不十分である可能性があります。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecINSUFFICIENT_RESERVE` | 141 | トランザクションによって[必要準備金](../../../../concepts/accounts/reserves.md)が増加し、送信側アカウントの残高を超える可能性があります。[SignerListSet][]、[PaymentChannelCreate][]、[PaymentChannelFund][]、および[EscrowCreate][]からこのエラーコードが返されることがあります。詳細は、[SignerListと準備金](../../ledger-data/ledger-entry-types/signerlist.md#signerlistと準備金)をご覧ください。 | | `tecINTERNAL` | 144 | 不明な内部エラーが発生し、トランザクションコストは適用されました。通常はこのエラーは返されません。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | -| `tecINVARIANT_FAILED` | 147 | このトランザクションを実行しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]により追加されました。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | -| `tecKILLED` | 150 | [OfferCreateトランザクション][]がtfFillOrKillフラグを指定しましたが、トランザクションを確定できなかったため、このトランザクションは取り消されました。_（[fix1578 Amendment][]により追加されました。）_ | +| `tecINVARIANT_FAILED` | 147 | このトランザクションを実行しようとしたところ、不変性チェックが失敗しました。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。{% amendment-disclaimer name="EnforceInvariants" /%} | +| `tecKILLED` | 150 | [OfferCreateトランザクション][]がtfFillOrKillフラグを指定しましたが、トランザクションを確定できなかったため、このトランザクションは取り消されました。{% amendment-disclaimer name="fix1578" /%} | | `tecMAX_SEQUENCE_REACHED` | 153 | シーケンス番号フィールドはすでに最大値に達しています。これには`MintedNFTokens`フィールドも含まれます。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecNEED_MASTER_KEY` | 142 | このトランザクションはマスターキーを必要とする変更（[マスターキーの無効化または残高フリーズ能力の放棄](../types/accountset.md#accountsetのフラグ)など）を試みました。| | `tecNFTOKEN_BUY_SELL_MISMATCH` | 155 | [NFTokenAcceptOfferトランザクション][]は、非代替性トークンの購入と売却に関する対応しないオファーをマッチングさせようとしました。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | diff --git a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tef-codes.md b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tef-codes.md index 2e77a00980c..ccff46f4ae3 100644 --- a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tef-codes.md +++ b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tef-codes.md @@ -25,7 +25,7 @@ labels: | `tefEXCEPTION` | トランザクションの処理中に、サーバが予期しない状態になりました。この状態は、予期しない入力（トランザクションのバイナリーデータの形式が大幅に誤っている場合など）が原因となった可能性があります。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tefFAILURE` | トランザクション適用中の不明な障害。 | | `tefINTERNAL` | トランザクションの適用を試みた際に、サーバが予期しない状態になりました。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | -| `tefINVARIANT_FAILED` | [トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)を請求しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]により追加されました。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | +| `tefINVARIANT_FAILED` | [トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)を請求しようとしたところ、不変性チェックが失敗しました。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 {% amendment-disclaimer name="EnforceInvariants" /%} | | `tefMASTER_DISABLED` | トランザクションはアカウントのマスターキーで署名されていましたが、アカウントに`lsfDisableMaster`フィールドが設定されていました。 | | `tefMAX_LEDGER` | トランザクションには[`LastLedgerSequence`](../../../../concepts/transactions/reliable-transaction-submission.md#lastledgersequence)パラメーターが指定されていましたが、現在のレジャーのシーケンス番号はすでに指定値を上回っています。 | | `tefNO_AUTH_REQUIRED` | [TrustSetトランザクション][]で相手トラストラインを承認済みとしてマークしようとしましたが、自身のアカウントにおいて`lsfRequireAuth`フラグが有効になっていないため、承認できません。 | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md index e8899554f16..c0d911a0432 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md @@ -34,10 +34,10 @@ AccountSetトランザクションは、[XRP Ledgerのアカウント](../../led | [`Domain`](#domain) | 文字列 | Blob | _（省略可）_ このアカウントを保有するドメインのASCII小文字を表現する16進文字列。[256バイトを超える長さは使用できません。](https://github.com/XRPLF/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | | `EmailHash` | 文字列 | Hash128 | _（省略可）_ アバターイメージの生成に使用されるメールアドレスのハッシュ。一般的に、クライアントは[Gravatar](http://en.gravatar.com/site/implement/hash/)を使用してこのイメージを表示しています。 | | `MessageKey` | 文字列 | Blob | _（省略可）_ 暗号化されたメッセージをこのアカウントに送信するための公開鍵です。キーを設定するには、正確に33バイトである必要があり、最初のバイトはキーの種類を示します。secp256k1鍵の場合は`0x02`または`0x03`、Ed25519鍵の場合は`0xED`です。キーを削除するには、空の値を使用します。 | -| `NFTokenMinter` | 文字列 | Blob | _(省略可)_ あなたのために[NFTokensをミントする](../../../../tutorials/javascript/nfts/assign-an-authorized-minter.md)ことができる別のアカウント。 _([NonFungibleTokensV1_1 amendment][]により追加されました.)_ | +| `NFTokenMinter` | 文字列 | Blob | _(省略可)_ あなたのために[NFTokensをミントする](../../../../tutorials/javascript/nfts/assign-an-authorized-minter.md)ことができる別のアカウント。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | [`SetFlag`](#accountsetのフラグ) | 数値 | UInt32 | _（省略可）_ このアカウントについてオプションを有効にするための整数フラグ。 | | [`TransferRate`](#transferrate) | 符号なし整数 | UInt32 | _（省略可）_ ユーザがこのアカウントのトークンを送金するときに請求される手数料。通貨単位の10億分の1で表現されます。手数料なしを意味する特殊なケースの`0`を除いて、`2000000000`より大きくしたり、`1000000000`より小さくしたりすることはできません。 | -| [`TickSize`](../../../../concepts/tokens/decentralized-exchange/ticksize.md) | 符号なし整数 | UInt8 | _（省略可）_このアドレスによって発行されている通貨が関係するオファーに使用する為替レートの呼値の単位。それらのオファーの為替レートは、この有効桁数へと丸められます。有効な値は`3`から`15`、または無効にするための`0`です_（[TickSize Amendment][]により追加されました）。_ | +| [`TickSize`](../../../../concepts/tokens/decentralized-exchange/ticksize.md) | 符号なし整数 | UInt8 | _（省略可）_このアドレスによって発行されている通貨が関係するオファーに使用する為替レートの呼値の単位。それらのオファーの為替レートは、この有効桁数へと丸められます。有効な値は`3`から`15`、または無効にするための`0`です{% amendment-disclaimer name="TickSize" /%} | | `WalletLocator` | 文字列 | UInt256 | _（省略可）_ 任意の256ビット値です。指定された場合、この値はアカウントの設定の一部として保存さ れますが、固有の定義や要件を持ちません。 | | `WalletSize` | 数値 | UInt32 | _（省略可）_ 使用されません。このフィールドはAccountSetトランザクションで有効ですが、何の機能もありません | @@ -73,10 +73,10 @@ AccountSetトランザクションは、[XRP Ledgerのアカウント](../../led | フラグの名前 | 10進値 | 説明 | |:----------------------------------|:------|:--------------| | `asfAccountTxnID` | 5 | このアカウントの直近のトランザクションのIDを追跡します。[AccountTxnID](../common-fields.md#accounttxnid)については必須です。 | -| `asfAllowTrustLineClawback` | 16 | アカウントの発行したトークンを回収する機能を有効にします。 _（[Clawback Amendment][]により追加されました）。_　所有者ディレクトリが存在する場合はClawback機能を有効にできません。つまり、トラストラインやオファー、エスクロー、ペイメントチャネル、チェック、または署名者リストを設定する前に行う必要があります。このフラグは、有効にした後は無効にできません。| +| `asfAllowTrustLineClawback` | 16 | アカウントの発行したトークンを回収する機能を有効にします。 {% amendment-disclaimer name="Clawback" /%}　所有者ディレクトリが存在する場合はClawback機能を有効にできません。つまり、トラストラインやオファー、エスクロー、ペイメントチャネル、チェック、または署名者リストを設定する前に行う必要があります。このフラグは、有効にした後は無効にできません。| | `asfAuthorizedNFTokenMinter` | 10 | このアカウントの代わりに、別のアカウントが非代替性トークン（NFToken）をミントすることを許可するために使用します。認可されたアカウントを[AccountRoot](../../ledger-data/ledger-entry-types/accountroot.md)オブジェクトの`NFTokenMinter`フィールドで指定します。認可されたアカウントを削除するには、このフラグを有効にして`NFTokenMinter`フィールドを省略します。 {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `asfDefaultRipple` | 8 | このアカウントのトラストラインでの[リップリング](../../../../concepts/tokens/fungible-tokens/rippling.md)をデフォルトで有効にします。 | -| `asfDepositAuth` | 9 | このアカウントに対して[Deposit Authorization](../../../../concepts/accounts/depositauth.md)を有効にします _（[DepositAuth Amendment][]により追加されました）。_ | +| `asfDepositAuth` | 9 | このアカウントに対して[Deposit Authorization](../../../../concepts/accounts/depositauth.md)を有効にします {% amendment-disclaimer name="DepositAuth" /%} | | `asfDisableMaster` | 4 | マスターキーペアの使用を禁止します。[レギュラーキー](../../../../concepts/accounts/cryptographic-keys.md)や[署名者リスト](../../../../concepts/accounts/multi-signing.md)など、トランザクションに署名するための別の手段がアカウントで設定されている場合のみ有効にできます。 | | `asfDisallowIncomingCheck` | 13 | チェックの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | | `asfDisallowIncomingNFTokenOffer` | 12 | NFTokenOffersの着信をブロックします。{% amendment-disclaimer name="DisallowIncoming" /%} | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md b/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md index e8d9279433b..bcccc53e4e5 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md @@ -12,7 +12,7 @@ DepositPreauthトランザクションは、あなたのアカウントへの支 {% admonition type="success" name="ヒント" %}このトランザクションを使用して、Deposit Authorizationを有効にする前に事前承認できます。これは、Deposit Authorizationの義務化への円滑な移行に役立ちます。{% /admonition %} -_[DepositPreauth Amendment][]により追加されました。_ +{% amendment-disclaimer name="DepositPreauth" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md index 3e8aea38c4b..7537fda41dc 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md @@ -2,15 +2,14 @@ seo: description: Escrowに留保されているXRPを送金元に返金します。 labels: - - Escrow + - Escrow --- # EscrowCancel - [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") Escrowに留保されているXRPを送金元に返金します。 -_[Escrow Amendment][]により追加されました。_ +{% amendment-disclaimer name="Escrow" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md index 57684a7f18d..82082319652 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md @@ -2,15 +2,14 @@ seo: description: Escrowプロセスが終了または取り消されるまでXRPを隔離します。 labels: - - Escrow + - Escrow --- # EscrowCreate - [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") Escrowプロセスが終了または取り消されるまでXRPを隔離します。 -_[Escrow Amendment][]により追加されました。_ +{% amendment-disclaimer name="Escrow" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md index fe8e9928e39..8c6bd60ce1b 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md @@ -2,16 +2,14 @@ seo: description: エスクローされたXRPを受取人へ送金します。 labels: - - Escrow + - Escrow --- # EscrowFinish - [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") エスクロー(保留中の支払い)から受取人へXRPを送金します。 -_[Escrow Amendment][]により追加されました。_ - +{% amendment-disclaimer name="Escrow" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md index a1ebf3eb95c..d2fecbebed3 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md @@ -1,10 +1,8 @@ --- -html: paymentchannelclaim.html -parent: transaction-types.html seo: description: Payment Channelに対しXRPを請求します。 labels: - - Payment Channel + - Payment Channel --- # PaymentChannelClaim [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") @@ -27,7 +25,7 @@ Channelの**宛先アドレス**は以下の操作を実行できます。 - Channelの`Expiration`または`CancelAfter`の時刻が前のレジャーの閉鎖時刻よりも古い場合にはChannelが閉鎖します。有効な形式のPaymentChannelClaimトランザクションでは、トランザクションの内容に関わらず常にこの効果があります。 -_[PayChan Amendment][]により追加されました。_ +{% amendment-disclaimer name="PayChan" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md index e48c39ae5e6..11db8013610 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -2,15 +2,15 @@ seo: description: 新しいペイメントチャネルを作成します。 labels: - - Payment Channel + - Payment Channel --- # PaymentChannelCreate [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "ソース") -_[PayChan Amendment][]により追加されました。_ - [ペイメントチャンネル](../../../../concepts/payment-types/payment-channels.md)を作成し、XRPで資金を供給します。このトランザクションを送信するアドレスが、ペイメントチャネルの「送信元アドレス」となります。 +{% amendment-disclaimer name="PayChan" /%} + ## {% $frontmatter.seo.title %} JSONの例 ```json diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md index f43cb7ee94a..bd1fb9b77f6 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -1,17 +1,15 @@ --- -html: paymentchannelfund.html -parent: transaction-types.html seo: description: Payment ChannelにXRPを追加します。 labels: - - Payment Channel + - Payment Channel --- # PaymentChannelFund [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") Payment ChannelにXRPを追加する、有効期限の更新も可能。このトランザクションは、Channelの支払元アドレスだけが使用できます。 -_[PayChan Amendment][]により追加されました。_ +{% amendment-disclaimer name="PayChan" /%} ## {% $frontmatter.seo.title %} JSONの例 diff --git a/docs/concepts/tokens/fungible-tokens/trust-line-tokens.md b/docs/concepts/tokens/fungible-tokens/trust-line-tokens.md index d8a352e611f..9362129170e 100644 --- a/docs/concepts/tokens/fungible-tokens/trust-line-tokens.md +++ b/docs/concepts/tokens/fungible-tokens/trust-line-tokens.md @@ -37,7 +37,7 @@ There are three cases where you can hold a balance that is _greater_ than your l 1. When you acquire more of that token through [trading](../decentralized-exchange/index.md). 2. When you decrease the limit on a trust line that has a positive balance. -3. When you acquire more of that token by [cashing a Check](../../payment-types/checks.md). (_Requires the [CheckCashMakesTrustLine amendment][]_) +3. When you acquire more of that token by [cashing a Check](../../payment-types/checks.md). {% amendment-disclaimer name="CheckCashMakesTrustLine" /%} ## Trust Line Settings From 07f4436b45783c3def1f0f5041220f336690ea86 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 14:27:23 -0700 Subject: [PATCH 7/9] Rename redundant pseudo-transactions index page --- .../docs/concepts/consensus-protocol/negative-unl.md | 4 ++-- @l10n/ja/docs/_snippets/pseudo-tx-fields-intro.md | 2 +- .../docs/concepts/consensus-protocol/negative-unl.md | 4 ++-- .../look-up-transaction-results.md | 4 ++-- @l10n/ja/docs/concepts/transactions/index.md | 2 +- .../ja/docs/references/protocol/transactions/index.md | 2 +- .../pseudo-transaction-types/enableamendment.md | 6 ++---- .../{pseudo-transaction-types.md => index.md} | 0 .../transactions/pseudo-transaction-types/setfee.md | 4 +--- .../pseudo-transaction-types/unlmodify.md | 10 ++++------ docs/_snippets/pseudo-tx-fields-intro.md | 2 +- docs/concepts/consensus-protocol/negative-unl.md | 4 ++-- .../look-up-transaction-results.md | 4 ++-- docs/concepts/transactions/index.md | 2 +- .../ledger-data/ledger-entry-types/ledgerhashes.md | 2 +- docs/references/protocol/transactions/index.md | 2 +- .../pseudo-transaction-types/enableamendment.md | 6 +++--- .../{pseudo-transaction-types.md => index.md} | 0 .../transactions/pseudo-transaction-types/setfee.md | 6 +++--- .../pseudo-transaction-types/unlmodify.md | 11 ++++------- redirects.yaml | 3 +++ sidebars.yaml | 2 +- 22 files changed, 38 insertions(+), 44 deletions(-) rename @l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/{pseudo-transaction-types.md => index.md} (100%) rename docs/references/protocol/transactions/pseudo-transaction-types/{pseudo-transaction-types.md => index.md} (100%) diff --git a/@l10n/es-ES/docs/concepts/consensus-protocol/negative-unl.md b/@l10n/es-ES/docs/concepts/consensus-protocol/negative-unl.md index 1fe6d50962c..e079cbb81db 100644 --- a/@l10n/es-ES/docs/concepts/consensus-protocol/negative-unl.md +++ b/@l10n/es-ES/docs/concepts/consensus-protocol/negative-unl.md @@ -74,7 +74,7 @@ En cada flag ledger, se aplican todos los siguientes cambios: 1. Los cambios la UNL negativa que se programaron en el flag ledger anterior entran en vigencia para la siguiente versión del ledger. El proceso de consenso para validar este flag ledger en sí mismo no utiliza el cambio programado. - **Nota:** Esto es uno de los únicos momentos en los que el estado de datos del ledger se modifica sin una [transacción](../transactions/index.md) o [pseudo-transacción](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md). + **Nota:** Esto es uno de los únicos momentos en los que el estado de datos del ledger se modifica sin una [transacción](../transactions/index.md) o [pseudo-transacción](../../references/protocol/transactions/pseudo-transaction-types/index.md). 2. Si la UNL negativa no está llena, cada servidor propone añadir **hasta 1** validador a la UNL negativa entre sus validadores confiables con una fiabilidad inferior al 50%. 3. Si la UNL negativa no está vacía, cada servidor propone eliminar **hasta 1** validador de la UNL negativa. Un servidor puede proponer eliminar un validador de la UNL negativa por dos motivos: @@ -82,7 +82,7 @@ En cada flag ledger, se aplican todos los siguientes cambios: - No tiene a ese validador en su UNL. (Si un validador deja de funcionar permanentemente, esta regla garantiza que se elimine de la UNL negativa en el ledger después de que se haya eliminado de las UNL configuradas de los servidores). 4. Si un cambio propuesto a la UNL negativa logra un consenso, el cambio se programa para entrar en vigencia en el siguiente flag ledger. Se puede programar hasta una adición y una eliminación de esta manera. -Las propuestas para agregar y eliminar validadores de la UNL negativa toman la forma de [pseudo-transacciones de UNLModify][]. El proceso de consenso determina si cada pseudo-transacción logra un consenso o se descarta, de la misma manera que otras [pseudo-transacciones](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md). En otras palabras, para que un validador en particular se agregue o elimine a la UNL negativa, se debe lograr un consenso de servidores sobre el mismo cambio. +Las propuestas para agregar y eliminar validadores de la UNL negativa toman la forma de [pseudo-transacciones de UNLModify][]. El proceso de consenso determina si cada pseudo-transacción logra un consenso o se descarta, de la misma manera que otras [pseudo-transacciones](../../references/protocol/transactions/pseudo-transaction-types/index.md). En otras palabras, para que un validador en particular se agregue o elimine a la UNL negativa, se debe lograr un consenso de servidores sobre el mismo cambio. Los cambios programados y efectivos de la UNL negativa se rastrean en el [objeto NegativeUNL](../../references/protocol/ledger-data/ledger-entry-types/negativeunl.md) en los datos de estado del ledger. diff --git a/@l10n/ja/docs/_snippets/pseudo-tx-fields-intro.md b/@l10n/ja/docs/_snippets/pseudo-tx-fields-intro.md index c2bce5a6d9d..cec75dcb82a 100644 --- a/@l10n/ja/docs/_snippets/pseudo-tx-fields-intro.md +++ b/@l10n/ja/docs/_snippets/pseudo-tx-fields-intro.md @@ -1,3 +1,3 @@ ## {% $frontmatter.seo.title %} フィールド -[共通フィールド][../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md]に加えて、{% $frontmatter.seo.title %}擬似トランザクションは以下のフィールドを使用します。 +[共通フィールド][../references/protocol/transactions/pseudo-transaction-types/index.md]に加えて、{% $frontmatter.seo.title %}擬似トランザクションは以下のフィールドを使用します。 diff --git a/@l10n/ja/docs/concepts/consensus-protocol/negative-unl.md b/@l10n/ja/docs/concepts/consensus-protocol/negative-unl.md index d9389993c3a..199fb6cae95 100644 --- a/@l10n/ja/docs/concepts/consensus-protocol/negative-unl.md +++ b/@l10n/ja/docs/concepts/consensus-protocol/negative-unl.md @@ -73,7 +73,7 @@ Vaは、サーバ側のコンセンサス見解と一致した過去2 1. 前のフラグレジャーで予定されていたネガティブUNLの変更は、次のレジャーバージョンから有効となる。このフラグレジャーの検証のための合意プロセスそのものは、予定されていた変更を利用しない。 - {% admonition type="info" name="注記" %}これは、[トランザクション](../transactions/index.md)や[疑似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)を行わずにレジャーの状態データを変更する唯一の機会です。{% /admonition %} + {% admonition type="info" name="注記" %}これは、[トランザクション](../transactions/index.md)や[疑似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/index.md)を行わずにレジャーの状態データを変更する唯一の機会です。{% /admonition %} 2. ネガティブUNLが満杯でない場合、各サーバは信頼度50%未満のバリデータの中から、**最大1つ**のバリデータをネガティブUNLに追加することを提案する。 3. ネガティブUNLが空でない場合、各サーバはネガティブUNLから**最大1つ**のバリデータを削除することを提案する。サーバがバリデータをネガティブUNLから削除することを提案できる理由は2つある。 @@ -81,7 +81,7 @@ Vaは、サーバ側のコンセンサス見解と一致した過去2 - 自身のUNLにそのバリデータを持たない。(バリデータが永久に停止した場合、このルールは、サーバの設定済みUNLからバリデータが削除された後に、オンレジャーのネガティブUNLからバリデータが削除されることを確実にする)。 4. ネガティブUNLの変更案がコンセンサスに達した場合、その変更は次のフラグレジャーから適用される予定である。この方法で最大1つの追加と1つの削除をスケジュールすることができる。 -ネガティブUNLにバリデータを追加したり削除したりする提案は[UNLModify pseudo-transactions][]の形式を取る。それぞれの擬似トランザクションは他の[擬似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)と同じように合意形成プロセスによって合意を得るか捨てられるかが決定される。言い換えると、あるバリデータがネガティブUNLに追加されたり削除されたりするためには、サーバの総意として同じ変更を提案する必要がある。 +ネガティブUNLにバリデータを追加したり削除したりする提案は[UNLModify pseudo-transactions][]の形式を取る。それぞれの擬似トランザクションは他の[擬似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/index.md)と同じように合意形成プロセスによって合意を得るか捨てられるかが決定される。言い換えると、あるバリデータがネガティブUNLに追加されたり削除されたりするためには、サーバの総意として同じ変更を提案する必要がある。 ネガティブUNLの予定された有効な変更は、レジャーの状態データの中の[ネガティブUNLオブジェクト](../../references/protocol/ledger-data/ledger-entry-types/negativeunl.md)に追跡される。 diff --git a/@l10n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md b/@l10n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md index ac36bde5a20..7606af80a46 100644 --- a/@l10n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md +++ b/@l10n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md @@ -92,7 +92,7 @@ XRP Ledgerは共有システムとなっていて、すべてのデータが公 ほとんどのメタデータは、[`AffectedNodes`配列](../../../references/protocol/transactions/metadata.md#affectednodes)に含まれています。この配列で探す対象は、トランザクションのタイプによって異なります。ほぼすべてのトランザクションが、送金元の[AccountRootオブジェクト][]を変更してXRP[トランザクションコスト](../transaction-cost.md)を消却し、[アカウントのシーケンス番号](../../../references/protocol/data-types/basic-data-types.md#アカウントシーケンス)を増やします。 -**情報:** このルールの例外として[疑似トランザクション](../../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)があります。このトランザクションは実在するアカウントから送信されないため、AccountRootオブジェクトを変更しません。その他の例外として、AccountRootオブジェクトの`Balance`フィールドを変更せずに、AccountRootオブジェクトを変更するトランザクションがあります。[Free Key Resetトランザクション](../transaction-cost.md#key-resetトランザクション)の場合、送金元のXRP残高は変わりません。トランザクションによって消却される金額と同額のXRPをアカウントが受け取る場合（ただし、このようなことはほとんどありません）、そのアカウントの正味残高は変わりません。（XRPを受領したアカウントに関係なくトランザクションコストはメタデータの別の場所に反映されます。） +**情報:** このルールの例外として[疑似トランザクション](../../../references/protocol/transactions/pseudo-transaction-types/index.md)があります。このトランザクションは実在するアカウントから送信されないため、AccountRootオブジェクトを変更しません。その他の例外として、AccountRootオブジェクトの`Balance`フィールドを変更せずに、AccountRootオブジェクトを変更するトランザクションがあります。[Free Key Resetトランザクション](../transaction-cost.md#key-resetトランザクション)の場合、送金元のXRP残高は変わりません。トランザクションによって消却される金額と同額のXRPをアカウントが受け取る場合（ただし、このようなことはほとんどありません）、そのアカウントの正味残高は変わりません。（XRPを受領したアカウントに関係なくトランザクションコストはメタデータの別の場所に反映されます。） 以下は、上記のステップ1からのレスポンス全文例です。レジャーに対して行われた変更を把握できるか確認してください。 @@ -435,7 +435,7 @@ TrustSetトランザクションは、[`RippleState`オブジェクト](../../.. ### 疑似トランザクション -[疑似トランザクション](../../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)にもメタデータがありますが、これらのトランザクションは通常のトランザクションのすべてのルールに従うとは限りません。これらのトランザクションは、実在のアカウントには関連付けられていないため（この`Account`の値は、[base58エンコード形式の数字の0](../../accounts/addresses.md#特別なアドレス)です）、レジャーのAccountRootオブジェクトを変更して`Sequence`シーケンス番号を増やしたり、XRPを消却したりしません。疑似トランザクションは、特別なレジャーオブジェクトに対して特定の変更のみを行います。 +[疑似トランザクション](../../../references/protocol/transactions/pseudo-transaction-types/index.md)にもメタデータがありますが、これらのトランザクションは通常のトランザクションのすべてのルールに従うとは限りません。これらのトランザクションは、実在のアカウントには関連付けられていないため（この`Account`の値は、[base58エンコード形式の数字の0](../../accounts/addresses.md#特別なアドレス)です）、レジャーのAccountRootオブジェクトを変更して`Sequence`シーケンス番号を増やしたり、XRPを消却したりしません。疑似トランザクションは、特別なレジャーオブジェクトに対して特定の変更のみを行います。 - [EnableAmendment疑似トランザクション][]は、[Amendmentレジャーオブジェクト](../../../references/protocol/ledger-data/ledger-entry-types/amendments.md)を変更して、有効なAmendment、過半数の支持を得ている保留中のAmendment、および保留中の期間を追跡します。 - [SetFee疑似トランザクション][]は、[FeeSettingsレジャーオブジェクト](../../../references/protocol/ledger-data/ledger-entry-types/feesettings.md)を変更して、[トランザクションコスト](../transaction-cost.md)および[必要準備金](../../accounts/reserves.md)のベースレベルを変更します。 diff --git a/@l10n/ja/docs/concepts/transactions/index.md b/@l10n/ja/docs/concepts/transactions/index.md index db97434a0c2..004b205a115 100644 --- a/@l10n/ja/docs/concepts/transactions/index.md +++ b/@l10n/ja/docs/concepts/transactions/index.md @@ -9,7 +9,7 @@ labels: --- # トランザクション -_トランザクション（取引）_ は、XRP Ledgerを変更する唯一の方法です。[コンセンサスプロセス](../consensus-protocol/index.md)に従って署名され、送信され、検証済みのレジャーバージョンに承認された場合にのみ、トランザクションは最終的なものになります。レジャーのルールによっては、_[疑似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)_ も生成されます。このトランザクションは署名も送信もされませんが、コンセンサスによって承認されなければならないことは同様です。失敗したトランザクションであっても、スパム対策の[トランザクションコスト][]を支払のためXRPの残高が変わるため、レジャーに記録されます。 +_トランザクション（取引）_ は、XRP Ledgerを変更する唯一の方法です。[コンセンサスプロセス](../consensus-protocol/index.md)に従って署名され、送信され、検証済みのレジャーバージョンに承認された場合にのみ、トランザクションは最終的なものになります。レジャーのルールによっては、_[疑似トランザクション](../../references/protocol/transactions/pseudo-transaction-types/index.md)_ も生成されます。このトランザクションは署名も送信もされませんが、コンセンサスによって承認されなければならないことは同様です。失敗したトランザクションであっても、スパム対策の[トランザクションコスト][]を支払のためXRPの残高が変わるため、レジャーに記録されます。 トランザクションで行えることは、送金だけではありません。XRP Ledgerのトランザクションは、さまざまな[支払いタイプ](../payment-types/index.md)に対応しているだけでなく、[暗号鍵](../accounts/cryptographic-keys.md)のローテーション、その他の設定の管理、およびXRP Ledgerの[分散型取引所](../tokens/decentralized-exchange/index.md)での取引にも使用されます。[トランザクションタイプの詳細なリスト](../../references/protocol/transactions/types/index.md)については、[`rippled` APIリファレンス](../../references/http-websocket-apis/index.md)をご覧ください。 diff --git a/@l10n/ja/docs/references/protocol/transactions/index.md b/@l10n/ja/docs/references/protocol/transactions/index.md index 3b2fb2ffbf8..3ecd6d36cee 100644 --- a/@l10n/ja/docs/references/protocol/transactions/index.md +++ b/@l10n/ja/docs/references/protocol/transactions/index.md @@ -8,7 +8,7 @@ metadata: --- # トランザクションリファレンス - _トランザクション_ は、XRP Ledgerを変更する唯一の方法です。[コンセンサスプロセス](../../../concepts/consensus-protocol/index.md)に従って署名され、送信され、検証済みのレジャーバージョンに承認された場合にのみ、トランザクションは[最終](../../../concepts/transactions/finality-of-results/index.md)的なものになります。レジャーのルールによっては、 _[疑似トランザクション](pseudo-transaction-types/pseudo-transaction-types.md)_ も生成されます。このトランザクションは署名も送信もされませんが、コンセンサスによって承認されなければならないことは同様です。失敗したトランザクションも、スパム対策の[トランザクションコスト][]を支払うためにXRPの残高が変更されることから、レジャーに含まれます。 + _トランザクション_ は、XRP Ledgerを変更する唯一の方法です。[コンセンサスプロセス](../../../concepts/consensus-protocol/index.md)に従って署名され、送信され、検証済みのレジャーバージョンに承認された場合にのみ、トランザクションは[最終](../../../concepts/transactions/finality-of-results/index.md)的なものになります。レジャーのルールによっては、 _[疑似トランザクション](pseudo-transaction-types/index.md)_ も生成されます。このトランザクションは署名も送信もされませんが、コンセンサスによって承認されなければならないことは同様です。失敗したトランザクションも、スパム対策の[トランザクションコスト][]を支払うためにXRPの残高が変更されることから、レジャーに含まれます。 {% raw-partial file="/@l10n/ja/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md index 3d07c98f701..0c1c0853b6f 100644 --- a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md +++ b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md @@ -1,14 +1,12 @@ --- -html: enableamendment.html -parent: pseudo-transaction-types.html seo: description: トランザクション処理を変更するAmendmentプロセスの進行状況を追跡します。 labels: - - ブロックチェーン + - ブロックチェーン --- # EnableAmendment -トランザクション処理を変更する[Amendmentプロセス](../../../../concepts/networks-and-servers/amendments.md#amendmentプロセス)の進行状況を追跡します。この疑似トランザクションは、提案されたAmendmentが多数の承認を獲得したか否かや、Amendmentの有効化の状況を示します。 +`EnableAmendment`[疑似トランザクション](./index.md)はトランザクション処理を変更する[Amendmentプロセス](../../../../concepts/networks-and-servers/amendments.md#amendmentプロセス)の進行状況を追跡します。この疑似トランザクションは、提案されたAmendmentが多数の承認を獲得したか否かや、Amendmentの有効化の状況を示します。 {% admonition type="info" name="注記" %}疑似トランザクションは送信できませんが、レジャーの処理時に疑似トランザクションが見つかることがあります。{% /admonition %} diff --git a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/index.md similarity index 100% rename from @l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md rename to @l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/index.md diff --git a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md index 02a7e388baf..8af459b4bc1 100644 --- a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md +++ b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md @@ -1,6 +1,4 @@ --- -html: setfee.html -parent: pseudo-transaction-types.html seo: description: 手数料投票の結果としてトランザクションコストまたはアカウント準備金の要件が変更されます。 labels: @@ -8,7 +6,7 @@ labels: --- # SetFee -[手数料投票](../../../../concepts/consensus-protocol/fee-voting.md)の結果として[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)または[アカウント準備金](../../../../concepts/accounts/reserves.md)の要件が変更されます。 +`SetFee`[疑似トランザクション](./index.md)は[手数料投票](../../../../concepts/consensus-protocol/fee-voting.md)の結果として[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)または[アカウント準備金](../../../../concepts/accounts/reserves.md)の要件が変更されます。 {% admonition type="info" name="注記" %}疑似トランザクションは送信できませんが、レジャーの処理時に疑似トランザクションが見つかることがあります。{% /admonition %} diff --git a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md index 2167875bc0d..12a033933c0 100644 --- a/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md +++ b/@l10n/ja/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md @@ -1,19 +1,17 @@ --- -html: unlmodify.html -parent: pseudo-transaction-types.html seo: description: 現在オフラインとみなされている信頼できるバリデータのリストを変更します。 labels: - - ブロックチェーン + - ブロックチェーン --- # UNLModify -{% amendment-disclaimer name="NegativeUNL" /%} - -`UNLModify`[疑似トランザクション](pseudo-transaction-types.md)は[Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md)の変更を示し、信頼できるバリデータがオフラインになったかオンラインに戻ってきたことを示します。 +`UNLModify`[疑似トランザクション](./index.md)は[Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md)の変更を示し、信頼できるバリデータがオフラインになったかオンラインに戻ってきたことを示します。 {% admonition type="info" name="注記" %}擬似トランザクションを送信することはできませんが、台帳を処理する際に擬似トランザクションを発見することがあります。{% /admonition %} +{% amendment-disclaimer name="NegativeUNL" /%} + ## {% $frontmatter.seo.title %} JSONの例 ```json diff --git a/docs/_snippets/pseudo-tx-fields-intro.md b/docs/_snippets/pseudo-tx-fields-intro.md index 4ca1faae6ad..f1cb75f2fbe 100644 --- a/docs/_snippets/pseudo-tx-fields-intro.md +++ b/docs/_snippets/pseudo-tx-fields-intro.md @@ -1,3 +1,3 @@ ## {% $frontmatter.seo.title %} Fields -In addition to the [common fields](../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md), {% $frontmatter.seo.title %} pseudo-transactions use the following fields: +In addition to the [common fields](../references/protocol/transactions/pseudo-transaction-types/index.md), {% $frontmatter.seo.title %} pseudo-transactions use the following fields: diff --git a/docs/concepts/consensus-protocol/negative-unl.md b/docs/concepts/consensus-protocol/negative-unl.md index 30decaabc16..0def00a637a 100644 --- a/docs/concepts/consensus-protocol/negative-unl.md +++ b/docs/concepts/consensus-protocol/negative-unl.md @@ -72,7 +72,7 @@ Each flag ledger, all of the following changes apply: 1. Changes to the Negative UNL that were scheduled in the previous flag ledger go into effect for the following ledger version. The consensus process for validating this flag ledger itself does not use the scheduled change. - {% admonition type="info" name="Note" %} This is one of the only times a ledger's state data is modified without a [transaction](../transactions/index.md) or [pseudo-transaction](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md).{% /admonition %} + {% admonition type="info" name="Note" %} This is one of the only times a ledger's state data is modified without a [transaction](../transactions/index.md) or [pseudo-transaction](../../references/protocol/transactions/pseudo-transaction-types/index.md).{% /admonition %} 2. If the Negative UNL is not full, each server proposes adding **up to 1** validator to the Negative UNL from among its trusted validators with less than 50% reliability. 3. If the Negative UNL is not empty, each server proposes removing **up to 1** validator from the Negative UNL. A server can propose removing a validator from the Negative UNL for two reasons: @@ -80,7 +80,7 @@ Each flag ledger, all of the following changes apply: - It does not have that validator in its UNL. (If a validator goes down permanently, this rule ensures that it gets removed from the on-ledger Negative UNL after it has been removed from servers' configured UNLs.) 4. If a proposed change to the Negative UNL achieves a consensus, the change is scheduled to go into effect in the following flag ledger. Up to one addition and one removal can be scheduled this way. -The proposals to add and remove validators from the Negative UNL take the form of [UNLModify pseudo-transactions][]. The consensus process determines whether each pseudo-transaction achieves a consensus or gets thrown out, in the same way as other [pseudo-transactions](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md). In other words, for a particular validator to be added or removed from the Negative UNL, a consensus of servers must propose the same change. +The proposals to add and remove validators from the Negative UNL take the form of [UNLModify pseudo-transactions][]. The consensus process determines whether each pseudo-transaction achieves a consensus or gets thrown out, in the same way as other [pseudo-transactions](../../references/protocol/transactions/pseudo-transaction-types/index.md). In other words, for a particular validator to be added or removed from the Negative UNL, a consensus of servers must propose the same change. Scheduled and effective changes to the Negative UNL are tracked in the [NegativeUNL object](../../references/protocol/ledger-data/ledger-entry-types/negativeunl.md) in the ledger's state data. diff --git a/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md b/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md index 9fd6cda1e33..1d1d6edd1c5 100644 --- a/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md +++ b/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md @@ -92,7 +92,7 @@ Transaction metadata describes _exactly_ how the transaction was applied to the Most of the metadata is contained in [the `AffectedNodes` array](../../../references/protocol/transactions/metadata.md#affectednodes). What to look for in this array depends on the type of transaction. Almost every transaction modifies the sender's [AccountRoot object][] to destroy the XRP [transaction cost](../transaction-cost.md) and increase the [account's Sequence number](../../../references/protocol/data-types/basic-data-types.md#account-sequence). -**Info:** One exception to this rule is for [pseudo-transactions](../../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md), which aren't sent from a real account and thus do not modify an AccountRoot object. There are other exceptions that modify an AccountRoot object without changing its `Balance` field: [free key reset transactions](../transaction-cost.md#key-reset-transaction) do not change the sender's XRP balance; and in the unlikely scenario that a transaction causes an account to receive exactly as much XRP as it destroys, the account's Balance shows no net change. (The net decrease in XRP occurs elsewhere in the metadata, debited from wherever the account sent the XRP.) +**Info:** One exception to this rule is for [pseudo-transactions](../../../references/protocol/transactions/pseudo-transaction-types/index.md), which aren't sent from a real account and thus do not modify an AccountRoot object. There are other exceptions that modify an AccountRoot object without changing its `Balance` field: [free key reset transactions](../transaction-cost.md#key-reset-transaction) do not change the sender's XRP balance; and in the unlikely scenario that a transaction causes an account to receive exactly as much XRP as it destroys, the account's Balance shows no net change. (The net decrease in XRP occurs elsewhere in the metadata, debited from wherever the account sent the XRP.) This example shows the full response from step 1 above. See if you can figure out what changes it made to the ledger: @@ -435,7 +435,7 @@ Most other transactions create a specific type of ledger entry and [adjust the s ### Pseudo-Transactions -[Pseudo-transactions](../../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md) also have metadata, but they do not follow all the rules of normal transactions. They are not tied to a real account (the `Account` value is the [base58-encoded form of the number 0](../../accounts/addresses.md#special-addresses)), so they do not modify an AccountRoot object in the ledger to increase the `Sequence` number or destroy XRP. Pseudo-transactions only make specific changes to special ledger objects: +[Pseudo-transactions](../../../references/protocol/transactions/pseudo-transaction-types/index.md) also have metadata, but they do not follow all the rules of normal transactions. They are not tied to a real account (the `Account` value is the [base58-encoded form of the number 0](../../accounts/addresses.md#special-addresses)), so they do not modify an AccountRoot object in the ledger to increase the `Sequence` number or destroy XRP. Pseudo-transactions only make specific changes to special ledger objects: - [EnableAmendment pseudo-transactions][] modify the [Amendments ledger object](../../../references/protocol/ledger-data/ledger-entry-types/amendments.md) to track which amendments are enabled, and which ones are pending with majority support and for how long. - [SetFee pseudo-transactions][] modify the [FeeSettings ledger object](../../../references/protocol/ledger-data/ledger-entry-types/feesettings.md) to change the base levels for the [transaction cost](../transaction-cost.md) and [reserve requirements](../../accounts/reserves.md). diff --git a/docs/concepts/transactions/index.md b/docs/concepts/transactions/index.md index d4591670b4f..d78f23aa916 100644 --- a/docs/concepts/transactions/index.md +++ b/docs/concepts/transactions/index.md @@ -9,7 +9,7 @@ labels: --- # Transactions -A _Transaction_ is the only way to modify the XRP Ledger. Transactions are only final if signed, submitted, and accepted into a validated ledger version following the [consensus process](../consensus-protocol/index.md). Some ledger rules also generate _[pseudo-transactions](../../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost][]. +A _Transaction_ is the only way to modify the XRP Ledger. Transactions are only final if signed, submitted, and accepted into a validated ledger version following the [consensus process](../consensus-protocol/index.md). Some ledger rules also generate _[pseudo-transactions](../../references/protocol/transactions/pseudo-transaction-types/index.md)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost][]. Transactions can do more than send money. In addition to supporting various [Payment Types](../payment-types/index.md), transactions in the XRP Ledger are also used to rotate [cryptographic keys](../accounts/cryptographic-keys.md), manage other settings, and trade in the XRP Ledger's [decentralized exchange](../tokens/decentralized-exchange/index.md). The [`rippled` API reference](../../references/http-websocket-apis/index.md) has a complete [list of transaction types](../../references/protocol/transactions/types/index.md). diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md b/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md index 074ab3f8044..4b65dba0e64 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md @@ -9,7 +9,7 @@ labels: (Not to be confused with the ["ledger hash" string data type][Hash], which uniquely identifies a ledger version. This page describes the `LedgerHashes` ledger entry type.) -The `LedgerHashes` ledger entry type contains a history of prior ledgers that led up to this ledger version, in the form of their hashes. Entries of this type are modified automatically when closing a ledger. (This is one of the only times a ledger's state data is modified without a [transaction](../../../../concepts/transactions/index.md) or [pseudo-transaction](../../transactions/pseudo-transaction-types/pseudo-transaction-types.md).) The `LedgerHashes` entries exist to make it possible to look up a previous ledger's hash with only the current ledger version and at most one lookup of a previous ledger version. +The `LedgerHashes` ledger entry type contains a history of prior ledgers that led up to this ledger version, in the form of their hashes. Entries of this type are modified automatically when closing a ledger. (This is one of the only times a ledger's state data is modified without a [transaction](../../../../concepts/transactions/index.md) or [pseudo-transaction](../../transactions/pseudo-transaction-types/index.md).) The `LedgerHashes` entries exist to make it possible to look up a previous ledger's hash with only the current ledger version and at most one lookup of a previous ledger version. There are two kinds of `LedgerHashes` entry. Both types have the same fields. Each ledger version contains: diff --git a/docs/references/protocol/transactions/index.md b/docs/references/protocol/transactions/index.md index cf508e0e605..2249ae3ec7c 100644 --- a/docs/references/protocol/transactions/index.md +++ b/docs/references/protocol/transactions/index.md @@ -8,7 +8,7 @@ metadata: --- # Transaction Reference -A _Transaction_ is the only way to cause changes in the XRP Ledger. Transactions' outcomes are only [final](../../../concepts/transactions/finality-of-results/index.md) if signed, submitted, and accepted into a validated ledger version following the [consensus process](../../../concepts/consensus-protocol/index.md). Some ledger rules also generate _[pseudo-transactions](pseudo-transaction-types/pseudo-transaction-types.md)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost][]. +A _Transaction_ is the only way to cause changes in the XRP Ledger. Transactions' outcomes are only [final](../../../concepts/transactions/finality-of-results/index.md) if signed, submitted, and accepted into a validated ledger version following the [consensus process](../../../concepts/consensus-protocol/index.md). Some ledger rules also generate _[pseudo-transactions](pseudo-transaction-types/index.md)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost][]. {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md b/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md index 8cca8021981..325578e5dc1 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md @@ -2,12 +2,12 @@ seo: description: Enable a change in transaction processing. labels: - - Blockchain + - Blockchain --- # EnableAmendment [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") -An `EnableAmendment` pseudo-transaction marks a change in the status of a proposed amendment. The possible status changes are: +An `EnableAmendment` [pseudo-transaction](./index.md) marks a change in the status of a proposed [amendment to the protocol](../../../../concepts/networks-and-servers/amendments.md). The possible status changes are: - The amendment gains supermajority approval from validators. - The amendment loses supermajority approval. @@ -34,7 +34,7 @@ An `EnableAmendment` pseudo-transaction marks a change in the status of a propos | Field | JSON Type | [Internal Type][] | Description | |:-----------------|:----------|:------------------|:--------------------------| -| `Amendment` | String | UInt256 | A unique identifier for the amendment. This is not intended to be a human-readable name. See [Amendments](../../../../concepts/networks-and-servers/amendments.md) for a list of known amendments. | +| `Amendment` | String | UInt256 | A unique identifier for the amendment. This is not intended to be a human-readable name. See [Known Amendments](../../../../../resources/known-amendments.md) for a list of known amendments. | | `LedgerSequence` | Number | UInt32 | The [ledger index][] where this pseudo-transaction appears. This distinguishes the pseudo-transaction from other occurrences of the same change. | ## EnableAmendment Flags diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md b/docs/references/protocol/transactions/pseudo-transaction-types/index.md similarity index 100% rename from docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md rename to docs/references/protocol/transactions/pseudo-transaction-types/index.md diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md b/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md index 78d0d852312..1c68c4c25d8 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md @@ -2,12 +2,12 @@ seo: description: Change global reserve and transaction cost settings. labels: - - Fees + - Fees --- # SetFee [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") -A `SetFee` [pseudo-transaction](pseudo-transaction-types.md) marks a change in [transaction cost](../../../../concepts/transactions/transaction-cost.md) or [reserve requirements](../../../../concepts/accounts/reserves.md) as a result of [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). +A `SetFee` [pseudo-transaction](./index.md) marks a change in [transaction cost](../../../../concepts/transactions/transaction-cost.md) or [reserve requirements](../../../../concepts/accounts/reserves.md) as a result of [fee voting](../../../../concepts/consensus-protocol/fee-voting.md). {% admonition type="info" name="Note" %}You cannot send a pseudo-transaction, but you may find one when processing ledgers.{% /admonition %} @@ -58,7 +58,7 @@ This transaction has two formats, depending on whether the [XRPFees amendment][] ## {% $frontmatter.seo.title %} Fields -The fields of a SetFee pseudo-transaction depend on whether the [XRPFees amendment][] was enabled at the time. In addition to the [common fields](./pseudo-transaction-types.md), they can use the following: +The fields of a SetFee pseudo-transaction depend on whether the [XRPFees amendment][] was enabled at the time. In addition to the [common fields](./index.md), they can use the following: {% tabs %} {% tab label="Current Format" %} diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md index 8f11ec84591..fb463c8a81f 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md @@ -1,20 +1,18 @@ --- -html: unlmodify.html -parent: pseudo-transaction-types.html seo: description: Change the list of trusted validators currently considered offline. labels: - - Blockchain + - Blockchain --- # UNLModify [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") -{% amendment-disclaimer name="NegativeUNL" /%} - -A `UNLModify` [pseudo-transaction](pseudo-transaction-types.md) marks a change to the [Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md), indicating that a trusted validator has gone offline or come back online. +A `UNLModify` [pseudo-transaction](./index.md) marks a change to the [Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md), indicating that a trusted validator has gone offline or come back online. {% admonition type="info" name="Note" %}You cannot send a pseudo-transaction, but you may find one when processing ledgers.{% /admonition %} +{% amendment-disclaimer name="NegativeUNL" /%} + ## Example {% $frontmatter.seo.title %} JSON ```json @@ -31,7 +29,6 @@ A `UNLModify` [pseudo-transaction](pseudo-transaction-types.md) marks a change t ``` {% partial file="/docs/_snippets/pseudo-tx-fields-intro.md" /%} - | Name | JSON Type | [Internal Type][] | Description | |:---------------------|:----------|:------------------|:----------------------| diff --git a/redirects.yaml b/redirects.yaml index 86f4aa3fcc3..127f235cf78 100644 --- a/redirects.yaml +++ b/redirects.yaml @@ -1,3 +1,6 @@ +/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types/: + to: /docs/references/protocol/transactions/pseudo-transaction-types/ + type: 301 /docs/concepts/tokens/transfer-fees/: to: /docs/concepts/tokens/fungible-tokens/transfer-fees/ type: 301 diff --git a/sidebars.yaml b/sidebars.yaml index a1972ed5e32..1de5c7dff18 100644 --- a/sidebars.yaml +++ b/sidebars.yaml @@ -447,7 +447,7 @@ - page: docs/references/protocol/transactions/types/xchaincreatebridge.md - page: docs/references/protocol/transactions/types/xchaincreateclaimid.md - page: docs/references/protocol/transactions/types/xchainmodifybridge.md - - page: docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md + - page: docs/references/protocol/transactions/pseudo-transaction-types/index.md expanded: false items: - page: docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md From f509c4b185b34afb6136b68479b31685dd41c1f9 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 14:27:46 -0700 Subject: [PATCH 8/9] Move more amendment disclaimers to end of section --- @l10n/ja/docs/concepts/accounts/depositauth.md | 4 ++-- @l10n/ja/docs/concepts/accounts/tickets.md | 10 ++++------ .../automated-market-makers.md | 4 ++-- .../ledger-data/ledger-entry-types/accountroot.md | 4 ++-- .../docs/use-cases/tokenization/stablecoin-issuer.md | 7 ++++--- .../decentralized-identifiers.md | 8 +++----- .../automated-market-makers.md | 12 ++++-------- .../concepts/tokens/decentralized-exchange/offers.md | 4 ++-- docs/concepts/xrpl-sidechains/cross-chain-bridges.md | 10 ++++------ docs/concepts/xrpl-sidechains/index.md | 10 ++++------ docs/concepts/xrpl-sidechains/witness-servers.md | 10 ++++------ .../account-methods/account_channels.md | 8 +++----- .../ledger-methods/ledger_entry.md | 8 ++++---- .../get_aggregate_price.md | 7 ++----- .../ledger-data/ledger-entry-types/accountroot.md | 4 ++-- .../ledger-data/ledger-entry-types/negativeunl.md | 6 +++--- .../ledger-data/ledger-entry-types/signerlist.md | 8 ++++---- .../protocol/transactions/types/payment.md | 4 ++-- .../use-tokens/create-an-automated-market-maker.md | 12 +++++------- .../use-xrpl-sidechains/set-up-iou-iou-bridge.md | 10 ++++------ .../use-xrpl-sidechains/set-up-xrp-xrp-bridge.md | 9 +++------ .../submit-cross-chain-transaction.md | 8 +++----- .../javascript/send-payments/sending-mpts.md | 8 ++++---- .../creating-an-asset-backed-multi-purpose-token.md | 8 ++++---- docs/use-cases/tokenization/stablecoin-issuer.md | 7 ++++--- 25 files changed, 82 insertions(+), 108 deletions(-) diff --git a/@l10n/ja/docs/concepts/accounts/depositauth.md b/@l10n/ja/docs/concepts/accounts/depositauth.md index 2f9ede74aa9..ebc9ae146fc 100644 --- a/@l10n/ja/docs/concepts/accounts/depositauth.md +++ b/@l10n/ja/docs/concepts/accounts/depositauth.md @@ -78,8 +78,6 @@ Deposit Authorizationが有効化されているアカウントの特徴は次 ## 事前承認 -{% amendment-disclaimer name="DepositPreauth" /%} - DepositAuthが有効なアカウントは、特定の送金元を _事前承認_ することにより、DepositAuthが有効になっていても、これらの送金元からの支払を受領することができます。これにより、特定の送金元からの資金の直接送金が可能となり、受取人はトランザクションごとに個別にアクションを実行する必要がなくなります。事前承認はDepositAuthの使用にあたり必須の要件ではありませんが、事前承認により特定の操作を実行しやすくなります。 事前承認は通貨に依存しません。特定の通貨のみについてアカウントを事前承認することはできません。 @@ -96,6 +94,8 @@ DepositPreauthトランザクションの処理が完了すると、承認済み 事前承認は、DepositAuthが有効なアカウントへのその他の送金方法には影響しません。詳しいルールについては、[詳細なセマンティクス](#詳細なセマンティクス)をご覧ください。 +{% amendment-disclaimer name="DepositPreauth" /%} + ### 承認の確認 [deposit_authorizedメソッド][]を使用して、特定のアカウントに対し別のアカウントへの入金が許可されているかどうかを確認できます。このメソッドは次の2点を確認します。 diff --git a/@l10n/ja/docs/concepts/accounts/tickets.md b/@l10n/ja/docs/concepts/accounts/tickets.md index 5fb39a1cdef..501e37b2e80 100644 --- a/@l10n/ja/docs/concepts/accounts/tickets.md +++ b/@l10n/ja/docs/concepts/accounts/tickets.md @@ -1,18 +1,16 @@ --- -html: tickets.html -parent: accounts.html seo: description: トランザクションを非連続的な順序で送信する labels: - - アカウント - - トランザクション送信 + - アカウント + - トランザクション送信 --- # Ticket -{% amendment-disclaimer name="TicketBatch" /%} - XRP Ledgerのチケットは、取引をすぐに送信せずに、その取引のために[シーケンス番号][]を確保する方法です。チケットを使うことで、通常の順序以外で取引を送信することができます。この使用例としては、必要な署名を集めるのに時間がかかるような[マルチサイン取引](multi-signing.md)などが挙げられます。 +{% amendment-disclaimer name="TicketBatch" /%} + ## 背景 [トランザクション](../transactions/index.md)にはシーケンス番号が付いているので、任意のトランザクションを2回以上実行することはできません。シーケンス番号はまた、任意のトランザクションが一意であることを保証します。全く同じ金額を同じ人に複数回送信する場合、シーケンス番号は毎回異なることが保証される1つの詳細です。最後に、シーケンス番号は、ネットワーク全体に送信される際に一部のトランザクションが順不同で届いたとしても、トランザクションを一貫した順序で並べるためのエレガントな方法を提供します。 diff --git a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md index 87eb9e84cac..e10619a3027 100644 --- a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md +++ b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md @@ -8,8 +8,6 @@ labels: --- # 自動マーケットメーカー(AMM)とは? -{% amendment-disclaimer name="AMM" /%} - 自動マーケットメーカー(AMM)は、XRP Ledgerの分散型取引所において流動性を提供します。個々のAMMは2つの資産のプールを保有します。ユーザは数式で定められた取引レートによりその2つの資産間でスワップが可能です。 ![自動マーケットメーカー](/docs/img/cpt-amm.png) @@ -24,6 +22,8 @@ labels: - AMMの手数料設定を変更するために投票する。票は、投票者が保有するLPトークンの数に基づいて重み付けされます。 - AMMの取引手数料の一時的な割引を得るために、LPトークンの一部を入札する。 +{% amendment-disclaimer name="AMM" /%} + ## AMMの仕組み AMMは2つの異なる資産を保有します。そのうちの最大1つはXRPとすることができ、そのうちの1つまたは両方が[トークン](../index.md)であることができます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index f796759c5e0..651d6e98a41 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -62,8 +62,6 @@ labels: ## AMMの特殊なAccountRootエントリ -{% amendment-disclaimer name="AMM" /%} - [自動マーケットメーカー](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)(AMM)は、AMMの詳細の一部を追跡するための[AMMレジャーエントリ](amm.md)に加えて、LPトークンを発行しAMMプール内の資産を保持するためにAccountRootレジャーエントリを使用します。AMMに関連するAccountRootのアドレスは、AMMが作成される前にユーザがそのアドレスを特定し資金を提供できないように、ランダム化されています。AMMのAccountRootは、通常のアカウントとは異なり、以下のような設定で作成されます。 - `lsfDisableMaster` **有効** : トランザクションへ署名する手段はありません。これにより、誰もそのアカウントを直接操作することができず、トランザクションを送信することができなくなります。 @@ -79,6 +77,8 @@ labels: LPトークンは他の[トークン](../../../../concepts/tokens/index.md)と同様に動作しますが、これらのトークンはAMM関連のトランザクションでも使用することができます。AMMの残高や、AMMに影響を与えたトランザクションの履歴は、通常のアカウントと同じように確認することができます。 +{% amendment-disclaimer name="AMM" /%} + ## AccountRootのフラグ AccountRootフラグの多くは、[AccountSetトランザクション][]で変更できるオプションに対応しています。ただし、レジャーで使用されるビット値は、トランザクションでそれらのフラグを有効または無効にするために使用される値とは異なります。レジャーのフラグは **lsf`** で始まる名前を持ちます。 diff --git a/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md b/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md index 52d2067df0d..54001ff52dc 100644 --- a/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md +++ b/@l10n/ja/docs/use-cases/tokenization/stablecoin-issuer.md @@ -159,14 +159,14 @@ _No Freeze_ 設定を有効にしない場合、アカウントが疑わしい ### Clawback -_([Clawback amendment][])_ - Clawbackは、ステーブルコインの配布を開始する前に選択できるオプション設定です。規制上の目的から、発行者の中には発行されたトークンをアカウントに配布した後に回収する能力を持たなければならない場合があります。例えば、トークンが違法行為で制裁を受けたアカウントに送られたことが発覚した場合、発行者はその資金を回収することができます。 [Clawback](../../references/protocol/transactions/types/clawback.md)をご覧ください。 ![Clawback](/docs/img/uc-stablecoin-clawback.png) +{% amendment-disclaimer name="Clawback" /%} + ### 部分支払い 部分支払い(Partial Payment)に注意してください。partial paymentフラグが有効になっている支払いは、0でない金額が着金した場合、微々たる金額であっても"成功"とみなされます。 @@ -206,7 +206,6 @@ Clawbackは、ステーブルコインの配布を開始する前に選択でき ### AMMへのリスト -{% amendment-disclaimer name="AMM" /%} 自動マーケットメイカー(AMM)は、XRP Ledgerの分散型取引所で流動性を提供するスマートコントラクトです。各AMMは2つの資産のプールを保有し、計算式で設定された取引レートでユーザがそれらの間でスワップを行うことを可能にします。 @@ -214,4 +213,6 @@ Clawbackは、ステーブルコインの配布を開始する前に選択でき [自動マーケットメーカー](../../concepts/tokens/decentralized-exchange/automated-market-makers.md)をご覧ください。 +{% amendment-disclaimer name="AMM" /%} + {% raw-partial file="/@l10n/ja/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/decentralized-storage/decentralized-identifiers.md b/docs/concepts/decentralized-storage/decentralized-identifiers.md index 8e3939d94b8..02a2cc92374 100644 --- a/docs/concepts/decentralized-storage/decentralized-identifiers.md +++ b/docs/concepts/decentralized-storage/decentralized-identifiers.md @@ -1,15 +1,11 @@ --- -html: decentralized-identifiers.html -parent: accounts.html seo: description: Decentralized identifiers enable verifiable, decentralized digital identities. labels: - - DID + - DID --- # Decentralized Identifiers -{% amendment-disclaimer name="DID" /%} - A Decentralized Identifier (DID) is a new type of identifier defined by the World Wide Web Consortium (W3C) that enables verifiable, digital identities. DIDs are fully under the control of the DID owner, independent from any centralized registry, identity provider, or certificate authority. The key principles of a DID are: @@ -24,6 +20,8 @@ The key principles of a DID are: {% admonition type="info" name="Note" %}The implementation of DIDs on the XRP Ledger conforms to the requirements in the [DID v1.0 specification](https://www.w3.org/TR/did-core/).{% /admonition %} +{% amendment-disclaimer name="DID" /%} + ## How It Works diff --git a/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md b/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md index daca6683541..fdd5e5ecc39 100644 --- a/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md +++ b/docs/concepts/tokens/decentralized-exchange/automated-market-makers.md @@ -3,14 +3,12 @@ seo: title: Automated Market Makers (AMMs) description: Automated Market Makers (AMMs) are an essential part of cryptocurrency, providing liquidity between asset pairs. Learn more about AMMs and the XRP Ledger. labels: - - XRP - - Decentralized Exchange - - AMM + - XRP + - Decentralized Exchange + - AMM --- # Automated Market Makers -{% amendment-disclaimer name="AMM" /%} - Automated Market Makers (AMMs) provide liquidity in the XRP Ledger's decentralized exchange (DEX). Each AMM holds a pool of two assets. You can swap between the two assets at an exchange rate set by a mathematical formula. ![Automated Market Maker](/docs/img/cpt-amm.png) @@ -25,10 +23,8 @@ LP tokens enable liquidity providers to: - Vote to change the AMM fee settings, each vote weighted by how many LP tokens the voter holds. - Bid some of their LP tokens to receive a temporary discount on the AMM trading fees. - ## How the AMM Works diff --git a/docs/concepts/tokens/decentralized-exchange/offers.md b/docs/concepts/tokens/decentralized-exchange/offers.md index 30e3c7ae891..d17303a0494 100644 --- a/docs/concepts/tokens/decentralized-exchange/offers.md +++ b/docs/concepts/tokens/decentralized-exchange/offers.md @@ -100,14 +100,14 @@ This is a consequence of how the network reaches agreement. For the entire peer- ## Permissioned and Hybrid Offers -{% amendment-disclaimer name="PermissionedDEX" /%} - By specifying a valid **permissioned domain ID**, you can place offers into a permissioned DEX instead of using the open DEX. You can only place a _permissioned offer_ if you hold the [credentials](../../decentralized-storage/credentials.md) required by the permissioned domain, and permissioned offers can only match other offers in the same permissioned domain. You can also place a _hybrid offer_ by using a domain ID and the Hybrid flag. Hybrid offers work like permissioned offers except that they can also match offers in the open DEX. Businesses with strict compliance requirements may want to use a permissioned DEX exclusively while traders with more relaxed compliance requirements can use hybrid offers to provide liquidity in more places. In most ways, permissioned and hybrid offers function like regular offers. They support all the same options, such as Fill-or-Kill, and are subject to the same requirements like the reserve per offer. One difference is that offers in a permissioned DEX can become _invalid_ if the account placing the offer loses access to the permissioned domain, for example because their credentials expired. For more information, see [Permissioned DEXes](./permissioned-dexes.md). +{% amendment-disclaimer name="PermissionedDEX" /%} + ## See Also diff --git a/docs/concepts/xrpl-sidechains/cross-chain-bridges.md b/docs/concepts/xrpl-sidechains/cross-chain-bridges.md index c3eb001602a..e0c9162bf2b 100644 --- a/docs/concepts/xrpl-sidechains/cross-chain-bridges.md +++ b/docs/concepts/xrpl-sidechains/cross-chain-bridges.md @@ -1,17 +1,13 @@ --- -html: cross-chain-bridges.html -parent: xrpl-sidechains.html seo: description: Cross-chain bridges for the XRP Ledger enable value in the form of XRP and other tokens (IOUs) to move efficiently between blockchains. status: not_enabled labels: - - Blockchain - - Interoperability + - Blockchain + - Interoperability --- # Cross-Chain Bridges -{% amendment-disclaimer name="XChainBridge" /%} - Cross-chain bridges enable you to move XRP and tokens between the XRP Ledger and other blockchains. When referring to the blockchains connected by a bridge, one is the locking chain and the other the issuing chain. A locking chain is where the digital asset originates from. These assets are locked in a trust when sent across a bridge to an issuing chain. @@ -22,6 +18,8 @@ An issuing chain is an independent ledger with its own consensus algorithm and t Both the locking and issuing chains operate as parallel networks with independent nodes and validators. They rely on independent [witness servers](witness-servers.md) to watch transactions between the two chains and attest that assets have moved into specifically designated accounts. +{% amendment-disclaimer name="XChainBridge" /%} + ## How Do Bridges Work? diff --git a/docs/concepts/xrpl-sidechains/index.md b/docs/concepts/xrpl-sidechains/index.md index 7ad05608439..a78865e1074 100644 --- a/docs/concepts/xrpl-sidechains/index.md +++ b/docs/concepts/xrpl-sidechains/index.md @@ -1,16 +1,12 @@ --- -html: xrpl-sidechains.html -parent: concepts.html seo: description: An XRPL sidechain is an independent ledger with its own consensus algorithm, transaction types, and rules. labels: - - Blockchain - - Interoperability + - Blockchain + - Interoperability --- # XRPL Sidechains -{% amendment-disclaimer name="XChainBridge" /%} - A sidechain is an independent ledger with its own consensus algorithm, transaction types, rules, and nodes. It acts as its own blockchain, running parallel to the mainchain (XRP Ledger), enabling value to move between the two without compromising the speed, efficiency, and throughput of the mainchain. Sidechains can customize the XRP Ledger protocol to the needs of a specific use case or project and run it as its own blockchain. Some examples include: @@ -20,6 +16,8 @@ Sidechains can customize the XRP Ledger protocol to the needs of a specific use * Building your own algorithmic stable coin with customised ledger types and transaction rules. * Building permissioned or nearly permissionless, centralized or largely decentralized ledgers whose assets can be traded on the Mainnet [decentralized exchange](../tokens/decentralized-exchange/index.md). +{% amendment-disclaimer name="XChainBridge" /%} + **Notes:** diff --git a/docs/concepts/xrpl-sidechains/witness-servers.md b/docs/concepts/xrpl-sidechains/witness-servers.md index 70be8d01bb0..9539c8ef80f 100644 --- a/docs/concepts/xrpl-sidechains/witness-servers.md +++ b/docs/concepts/xrpl-sidechains/witness-servers.md @@ -1,18 +1,14 @@ --- -html: witness-servers.html -parent: xrpl-sidechains.html seo: description: A witness server is a light-weight server that witnesses and signs transactions between the XRP Ledger and another chain. status: not_enabled labels: - - Blockchain - - Interoperability + - Blockchain + - Interoperability --- # Witness Servers [[Source]](https://github.com/seelabs/xbridge_witness "Source") -{% amendment-disclaimer name="XChainBridge" /%} - A _witness server_ acts as a neutral witness for transactions between a locking chain and an issuing chain. It listens to the door accounts on both sides of a bridge and signs attestations that confirm a transaction occurred. They are essentially acting as an oracle to “prove” that value was locked or burned on a source account, which allows the recipient to then claim (via minting or unlocking) the equivalent funds on the destination account. The bridge between the locking chain and the issuing chain includes the following information in its configuration: @@ -24,6 +20,8 @@ Anyone can run a witness server. However, the burden is on the participants of t {% admonition type="info" name="Note" %}Issuing chains may choose to configure a bridge with only one witness server initially and run the witness server itself. This strategy is helpful in the initial period, when the issuing chain hasn't established itself yet in the marketplace.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} + ## Witness Server Configuration diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md index 52ef0f89d03..e8b8eab1c30 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md @@ -1,18 +1,16 @@ --- -html: account_channels.html -parent: account-methods.html seo: description: Get a list of payment channels where the account is the source of the channel. labels: - - Payment Channels + - Payment Channels --- # account_channels [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source") -{% amendment-disclaimer name="PayChan" /%} - The `account_channels` method returns information about an account's Payment Channels. This includes only channels where the specified account is the channel's source, not the destination. (A channel's "source" and "owner" are the same.) All information retrieved is relative to a particular version of the ledger. +{% amendment-disclaimer name="PayChan" /%} + ## Request Format An example of the request format: diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index 209d2847ab9..02f61582fb5 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -887,10 +887,10 @@ rippled json ledger_entry '{ "nft_page": "255DD86DDF59D778081A06D02701E9B2C9F4F0 ### Get MPT Issuance Object -{% amendment-disclaimer name="MPTokensV1" /%} - Return an `MPTokenIssuance` object. +{% amendment-disclaimer name="MPTokensV1" /%} + | Field | Type | Description | |:---------------|:-------|:----------------------| | `mpt_issuance` | String | The 192-bit `MPTokenIssuanceID` that's associated with the MPTokenIssuance, as hexadecimal. | @@ -933,10 +933,10 @@ rippled json ledger_entry '{ "mpt_issuance": "000004C463C52827307480341125DA0577 ### Get MPToken Object -{% amendment-disclaimer name="MPTokensV1" /%} - Return an `MPToken` object. +{% amendment-disclaimer name="MPTokensV1" /%} + | Field | Type | Description | |:--------------------------|:-----------------|:------------| | `mptoken` | ️Object or String | If a string, interpret as ledger entry ID of the MPToken to retrieve. If an object, requires the sub-fields `account` and `mpt_issuance_id` to uniquely identify the MPToken. | diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md index 2e0d971ce39..5f02d57360a 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md @@ -2,17 +2,14 @@ seo: description: Calculate the aggregate price of specified Oracle instances. labels: - - Oracle + - Oracle --- # get_aggregate_price - -{% amendment-disclaimer name="PriceOracle" /%} - [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/GetAggregatePrice.cpp "Source") - The `get_aggregate_price` method retrieves the aggregate price of specified `Oracle` objects, returning three price statistics: mean, median, and trimmed mean. +{% amendment-disclaimer name="PriceOracle" /%} ## Request Format diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index dda47f7849d..9d70a6dc5a1 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -62,8 +62,6 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e ## Special AMM AccountRoot Entries -{% amendment-disclaimer name="AMM" /%} - Automated Market Makers use an AccountRoot ledger entry to issue their LP Tokens and hold the assets in the AMM pool, and an [AMM ledger entry](amm.md) for tracking some of the details of the AMM. The address of an AMM's AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoot objects are created with the following settings: - `lsfDisableMaster` **enabled** and no means of authorizing transactions. This ensures no one can control the account directly, and it cannot send transactions. @@ -79,6 +77,8 @@ In addition, the following special rules apply to an AMM's AccountRoot entry: Other than those exceptions, these accounts are like ordinary accounts; the LP Tokens they issue behave like other [tokens](../../../../concepts/tokens/index.md) except that those tokens can also be used in AMM-related transactions. You can check an AMM's balances and the history of transactions that affected it the same way you would with a regular account. +{% amendment-disclaimer name="AMM" /%} + ## AccountRoot Flags Many AccountRoot flags correspond to options you can change with an [AccountSet transaction][]. However, the bit values used in the ledger are different than the values used to enable or disable those flags in a transaction. Ledger flags have names that begin with **`lsf`**. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md index 2110d24ab54..e66886de2f4 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md @@ -2,17 +2,17 @@ seo: description: List of validators currently believed to be offline. labels: - - Blockchain + - Blockchain --- # NegativeUNL [[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L85-L91 "Source") -{% amendment-disclaimer name="NegativeUNL" /%} - The `NegativeUNL` ledger entry type contains the current status of the [Negative UNL](../../../../concepts/consensus-protocol/negative-unl.md), a list of trusted validators currently believed to be offline. Each ledger version contains **at most one** `NegativeUNL` entry. If no validators are currently disabled or scheduled to be disabled, there is no `NegativeUNL` entry. +{% amendment-disclaimer name="NegativeUNL" /%} + ## Example {% $frontmatter.seo.title %} JSON ```json diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md index de2c832b003..9ebae89746e 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md @@ -76,22 +76,22 @@ When processing a multi-signed transaction, the server looks up the `Account` va ## {% $frontmatter.seo.title %} Flags -{% amendment-disclaimer name="MultiSignReserve" /%} - SignerList entries can have the following value in the `Flags` field: | Flag Name | Hex Value | Decimal Value | Description | |:-------------------|:-------------|:--------------|:-------------------------| | `lsfOneOwnerCount` | `0x00010000` | 65536 | If this flag is enabled, this SignerList counts as one item for purposes of the [owner reserve](../../../../concepts/accounts/reserves.md#owner-reserves). Otherwise, this list counts as N+2 items, where N is the number of signers it contains. This flag is automatically enabled if you add or update a signer list after the [MultiSignReserve amendment][] is enabled. | +{% amendment-disclaimer name="MultiSignReserve" /%} + ## Signer Lists and Reserves A signer list contributes to its owner's [reserve requirement](../../../../concepts/accounts/reserves.md). Removing the signer list frees up the reserve. -The [MultiSignReserve amendment][] (enabled 2019-04-17) made it so each signer list counts as one item, regardless of how many members it has. As a result, the owner reserve for any signer list added or updated after this time is {% $env.PUBLIC_OWNER_RESERVE %}. +{% amendment-disclaimer name="MultiSignReserve" compact=true /%} made it so each signer list counts as one item, regardless of how many members it has. As a result, the owner reserve for any signer list added or updated after this time is {% $env.PUBLIC_OWNER_RESERVE %}. -A signer list created before the [MultiSignReserve amendment][] itself counts as two items towards the owner reserve, and each member of the list counts as one. As a result, the total owner reserve associated with an old signer list is anywhere from 3 times to 10 times as much as a new signer list. To update a signer list to use the new, reduced reserve, update the signer list by sending a [SignerListSet transaction][]. +A signer list created before the MultiSignReserve amendment counts as two items towards the owner reserve, plus one for each member of the list. As a result, the total owner reserve associated with an old signer list is anywhere from 3 times to 10 times as much as a new signer list. To update a signer list to use the new, reduced reserve, update the signer list by sending a [SignerListSet transaction][]. ## SignerList ID Format diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index e559766f8d7..67845da4fe9 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -175,8 +175,6 @@ Version 1 MPTokens only support direct MPT payment between accounts. They cannot ``` ## Credential IDs -{% amendment-disclaimer name="Credentials" /%} - You can send money to an account that uses [Deposit Authorization](../../../../concepts/accounts/depositauth.md) by providing the `CredentialIDs` field with an exact set of credentials that are preauthorized by the recipient. The set of credentials must match a [DepositPreauth entry](../../ledger-data/ledger-entry-types/depositpreauth.md) in the ledger. The credentials provided in the `CredentialIDs` field must all be valid, meaning: @@ -192,6 +190,8 @@ If you provide credentials even though the destination account does not use Depo The `CredentialIDs` field is only used for deposit authorization, not for trading in a [permissioned DEX](../../../../concepts/tokens/decentralized-exchange/permissioned-dexes.md), even though Permissioned DEXes also use credentials to grant access. To trade in a permissioned DEX, you use the `DomainID` field to specify a domain for which you hold valid credentials. {% /admonition %} +{% amendment-disclaimer name="Credentials" /%} + ## Special Case for Destination Accounts Below the Reserve If an account has Deposit Authorization enabled, but its current XRP balance is less than the [reserve requirement](../../../../concepts/accounts/reserves.md), there is a special exception to Deposit Authorization where anyone can send a Payment transaction, without preauthorization, for up to the base account reserve; this exists as an emergency measure to prevent an account from getting "stuck" without enough XRP to transact. To qualify for this special case, the payment MUST NOT use the `CredentialIDs` field. diff --git a/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md b/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md index 77b4f2f9651..f260fda3b95 100644 --- a/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md +++ b/docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md @@ -1,23 +1,21 @@ --- -parent: use-tokens.html seo: description: Set up an Automated Market Maker (AMM) embed_xrpl_js: true -status: not_enabled filters: - interactive_steps labels: - - Decentralized Exchange - - Tokens - - AMM + - Decentralized Exchange + - Tokens + - AMM steps: ['Connect', 'Generate', 'Acquire tokens', 'Check for AMM', 'Look up AMMCreate cost', 'Create AMM', 'Check AMM info', 'Check trust lines'] --- # Create an Automated Market Maker -{% amendment-disclaimer name="AMM" /%} - An [Automated Market Maker (AMM)](../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) can be an efficient way to facilitate exchanges between two assets while earning its liquidity providers passive income. This tutorial shows how to create an AMM for a given asset pair. +{% amendment-disclaimer name="AMM" /%} + diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md index 51a2ccc1005..8d26a77148d 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-iou-iou-bridge.md @@ -1,18 +1,16 @@ --- -html: set-up-iou-iou-bridge.html -parent: use-xrpl-sidechains.html seo: description: Steps to set up an IOU-IOU bridge. labels: - - Interoperability + - Interoperability --- # Set Up an IOU-IOU Bridge -{% amendment-disclaimer name="XChainBridge" /%} - Setting up an IOU-IOU bridge enables you to move tokens between chains. -**Note**: The code samples on this page illustrate how to bridge a hypotethical "TST" token from *Devnet* to *Sidechain-Devnet*, using a supported [client library](/docs/references/client-libraries.md) to query and submit transactions. +{% admonition type="info" name="Note" %}The code samples on this page illustrate how to bridge a hypotethical "TST" token from *Devnet* to *Sidechain-Devnet*, using a supported [client library](/docs/references/client-libraries.md) to query and submit transactions.{% /admonition %} + +{% amendment-disclaimer name="XChainBridge" /%} ## Prerequisites diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md index c94ddd0ae9c..46af4c50e83 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/set-up-xrp-xrp-bridge.md @@ -1,19 +1,16 @@ --- -html: set-up-xrp-xrp-bridge.html -parent: use-xrpl-sidechains.html seo: description: Steps to create an XRP-XRP bridge with a new sidechain. labels: - - Interoperability + - Interoperability --- # Set Up an XRP-XRP Bridge -{% amendment-disclaimer name="XChainBridge" /%} - Setting up an XRP-XRP bridge enables you to move XRP between chains. The set up requires using the genesis account on the issuing chain as a door account to submit attestations and create transaction submission accounts for witnesses. -**Note**: The code samples on this page illustrate how a bridge was set up between *Devnet* and *Sidechain-Devnet*, using a supported [client library](/docs/references/client-libraries.md) to query and submit transactions. This bridge is already created, so the process can't be reproduced on these networks. +{% admonition type="info" name="Note" %}The code samples on this page illustrate how a bridge was set up between *Devnet* and *Sidechain-Devnet*, using a supported [client library](/docs/references/client-libraries.md) to query and submit transactions. This bridge is already created, so the process can't be reproduced on these networks.{% /admonition %} +{% amendment-disclaimer name="XChainBridge" /%} ## Prerequisites diff --git a/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md b/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md index 668ad9f9239..9c2f0cccdef 100644 --- a/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md +++ b/docs/tutorials/how-tos/use-xrpl-sidechains/submit-cross-chain-transaction.md @@ -1,17 +1,15 @@ --- -html: submit-cross-chain-transactions.html -parent: use-xrpl-sidechains.html seo: description: Steps to submit a cross-chain transaction, using a bridge. labels: - - Interoperability + - Interoperability --- # Submit Cross-chain Transactions -{% amendment-disclaimer name="XChainBridge" /%} - This tutorial explains how to create a test account on a locking chain (_Devent_), and transfer XRP to an issuing chain (_Sidechain-Devnet_), using a supported [client library](../../../references/client-libraries.md) to query and submit transactions. Witness servers are already set up to monitor the XRP-XRP bridge and submit attestations. +{% amendment-disclaimer name="XChainBridge" /%} + ## Prerequisites - The locking and issuing chains are both up and running. diff --git a/docs/tutorials/javascript/send-payments/sending-mpts.md b/docs/tutorials/javascript/send-payments/sending-mpts.md index 564f4051057..8f8cc549e67 100644 --- a/docs/tutorials/javascript/send-payments/sending-mpts.md +++ b/docs/tutorials/javascript/send-payments/sending-mpts.md @@ -2,17 +2,17 @@ seo: description: Issue an asset-backed token such as a US Treasury bill using multi-purpose tokens. labels: - - Tokens - - MPT + - Tokens + - MPT --- # Sending MPTs -{% amendment-disclaimer name="MPTokensV1" /%} - To send an MPT to another account, the receiving account must first authorize the receipt of the MPT, based on its MPToken Issuance ID. This is to prevent malicious users from spamming accounts with unwanted tokens that could negatively impact storage and XRP reserves. Once an account receives an MPT, it can send the MPT to another account, provided the MPT was created with the _Can Transfer_ flag set, and the receiving account authorizes the MPT. +{% amendment-disclaimer name="MPTokensV1" /%} + ## Send MPT Utility The Send MPT utility lets you create an account, authorize it to receive a specific MPT issuance, then send it the authorized MPT from an issuer or holder account. (You can issue an MPT using the [MPT Generator](../../../use-cases/tokenization/creating-an-asset-backed-multi-purpose-token.md) utility.) diff --git a/docs/use-cases/tokenization/creating-an-asset-backed-multi-purpose-token.md b/docs/use-cases/tokenization/creating-an-asset-backed-multi-purpose-token.md index 5c21d6b462d..c429457d18b 100644 --- a/docs/use-cases/tokenization/creating-an-asset-backed-multi-purpose-token.md +++ b/docs/use-cases/tokenization/creating-an-asset-backed-multi-purpose-token.md @@ -2,13 +2,11 @@ seo: description: Issue an asset-backed token such as a US Treasury bill using multi-purpose tokens. labels: - - Tokens - - MPT + - Tokens + - MPT --- # Creating an Asset-backed Multi-purpose Token -{% amendment-disclaimer name="MPTokensV1" /%} - _As a financial professional, I want to use multi-purpose tokens to create an asset-backed token in order to profit from resale transactions._ A multi-purpose token (MPT) is a compact and flexible object that offers the best aspects of fungible and non-fungible tokens. It is the next generation of tokenization on the XRPL. Notable features include: @@ -21,6 +19,8 @@ A multi-purpose token (MPT) is a compact and flexible object that offers the bes To learn more, see [Multi-purpose Tokens](../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md). +{% amendment-disclaimer name="MPTokensV1" /%} + ## MPT Generator ![MPT Generator Utility](../../img/uc-mpt1-mpt-generator-empty-form.png) diff --git a/docs/use-cases/tokenization/stablecoin-issuer.md b/docs/use-cases/tokenization/stablecoin-issuer.md index bc4fe26b9dd..152a97d6712 100644 --- a/docs/use-cases/tokenization/stablecoin-issuer.md +++ b/docs/use-cases/tokenization/stablecoin-issuer.md @@ -159,14 +159,14 @@ See [Enact Global Freeze](../../tutorials/how-tos/use-tokens/enact-global-freeze ### Clawback -{% amendment-disclaimer name="Clawback" /%} - Clawback is an optional setting that you can choose before you begin to distribute your stablecoin. For regulatory purposes, some issuers _must_ have the ability to recover issued tokens after they are distributed to accounts. For example, if an issuer were to discover that tokens were sent to an account sanctioned for illegal activity, the issuer could recover, or _claw back_, the funds. See [Clawback](../../references/protocol/transactions/types/clawback.md). ![Clawback](/docs/img/uc-stablecoin-clawback.png) +{% amendment-disclaimer name="Clawback" /%} + ### Partial Payments Look out for partial payments. Payments with the partial payment flag enabled can be considered "successful" if any non-zero amount is delivered, even minuscule amounts. @@ -206,7 +206,6 @@ Decentralized exchanges (DEXes) are integral to the decentralized finance ecosys ### List on an AMM -{% amendment-disclaimer name="AMM" /%} Automated Market Makers (AMMs) are smart contracts that provide liquidity in the XRP Ledger's decentralized exchange. Each AMM holds a pool of two assets and enables users to swap between them at an exchange rate set by a formula. @@ -214,4 +213,6 @@ For any given pair of assets, there can be up to one AMM in the ledger. You can See [Automated Market Makers](../../concepts/tokens/decentralized-exchange/automated-market-makers.md). +{% amendment-disclaimer name="AMM" /%} + {% raw-partial file="/docs/_snippets/common-links.md" /%} From ab151da705e7fd079bc6d5d447e1114e6d3348ff Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 6 Oct 2025 14:30:16 -0700 Subject: [PATCH 9/9] Redirect redundant pseudo-transaction-types landing in Japanese too --- redirects.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/redirects.yaml b/redirects.yaml index 127f235cf78..dffb961e6e7 100644 --- a/redirects.yaml +++ b/redirects.yaml @@ -2356,6 +2356,9 @@ code_of_conduct.ja: type: 301 # Japanese +/ja/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types/: + to: /ja/docs/references/protocol/transactions/pseudo-transaction-types/ + type: 301 /ja/docs/concepts/tokens/transfer-fees/: to: /ja/docs/concepts/tokens/fungible-tokens/transfer-fees/ type: 301