diff --git a/@i18n/ja/docs/_snippets/tx-metadata-field-table.md b/@i18n/ja/docs/_snippets/tx-metadata-field-table.md index 0804058f77..c64d10a91b 100644 --- a/@i18n/ja/docs/_snippets/tx-metadata-field-table.md +++ b/@i18n/ja/docs/_snippets/tx-metadata-field-table.md @@ -3,5 +3,5 @@ | `AffectedNodes` | 配列 | このトランザクションで作成、削除、または修正された[レジャーオブジェクト](../references/protocol/ledger-data/ledger-entry-types/index.md)のリストと、個々のオブジェクトに対する具体的な変更内容。 | | `DeliveredAmount` | [通貨額][] | **廃止予定。**`delivered_amount`で置き換えられます。Partial Paymentsでない場合は省略されます。 | | `TransactionIndex` | 符号なし整数 | トランザクションが記録されているレジャーでのトランザクションの位置。この配列は0から始まります。（例えば、値が`2`の場合、そのレジャーの3番目のトランザクションであったことを意味します）。 | -| `TransactionResult` | 文字列 | トランザクションが成功したか、どのような理由で失敗したかを示す[結果コード](../references/protocol/transactions/transaction-results/transaction-results.md)。 | +| `TransactionResult` | 文字列 | トランザクションが成功したか、どのような理由で失敗したかを示す[結果コード](../references/protocol/transactions/transaction-results/index.md)。 | | [`delivered_amount`](../references/protocol/transactions/metadata.md#delivered_amount) | [通貨額][] | `Destination`アカウントが実際に受取った[通貨額][]。このフィールドは、トランザクションが[Partial Payments](../concepts/payment-types/partial-payments.md)であるかどうかにかかわらず、送金された金額を特定するために使用します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.27.0" %}新規: rippled 0.27.0{% /badge %} | diff --git a/@i18n/ja/docs/concepts/consensus-protocol/consensus-structure.md b/@i18n/ja/docs/concepts/consensus-protocol/consensus-structure.md index cbfa476a5d..e3cb115062 100644 --- a/@i18n/ja/docs/concepts/consensus-protocol/consensus-structure.md +++ b/@i18n/ja/docs/concepts/consensus-protocol/consensus-structure.md @@ -51,7 +51,7 @@ _図3: レジャーバージョンに適用されるトランザクション_ レジャーインスタンスに含まれる一連のトランザクションはそのレジャーに記録され、XRP Ledger履歴の監査を可能としています。レジャーN+1のアカウント残高がレジャーNのアカウント残高と異なる場合、レジャーN+1にはその変更の原因となったトランザクションが含まれます。 -検証済みのレジャー内に出現するトランザクションは、レジャーの変更に成功したか、または要求されたアクションを実行せずに処理された可能性があります。成功したトランザクションには、要求された変更がレジャーに適用されたことを示す**tesSUCCESS** [結果コード](../../references/protocol/transactions/transaction-results/transaction-results.md)が含まれます。レジャー内の失敗したトランザクションには、**tec**クラスの結果コードが含まれます。1 +検証済みのレジャー内に出現するトランザクションは、レジャーの変更に成功したか、または要求されたアクションを実行せずに処理された可能性があります。成功したトランザクションには、要求された変更がレジャーに適用されたことを示す**tesSUCCESS** [結果コード](../../references/protocol/transactions/transaction-results/index.md)が含まれます。レジャー内の失敗したトランザクションには、**tec**クラスの結果コードが含まれます。1 レジャーに含まれるトランザクションでは必ず、[トランザクションコスト](../transactions/transaction-cost.md)として一部のXRPが消却されます。この場合、**tes**コードまたは**tec**コードが含まれていたかどうかは関係ありません。消却するXRPの正確な量は、署名されたトランザクションの手順で定義されます。 diff --git a/@i18n/ja/docs/concepts/networks-and-servers/transaction-censorship-detection.md b/@i18n/ja/docs/concepts/networks-and-servers/transaction-censorship-detection.md index 726e9e64a2..7d42b4c6a4 100644 --- a/@i18n/ja/docs/concepts/networks-and-servers/transaction-censorship-detection.md +++ b/@i18n/ja/docs/concepts/networks-and-servers/transaction-censorship-detection.md @@ -74,6 +74,6 @@ LedgerConsensus:ERR Potential Censorship: Eligible tx E08D6E9754025BA2534A787076 - [信頼できるトランザクションの送信](../transactions/reliable-transaction-submission.md) - [ログメッセージについて](../../infrastructure/troubleshooting/understanding-log-messages.md) - **リファレンス:** - - [トランザクションの結果](../../references/protocol/transactions/transaction-results/transaction-results.md) + - [トランザクションの結果](../../references/protocol/transactions/transaction-results/index.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/concepts/payment-types/direct-xrp-payments.md b/@i18n/ja/docs/concepts/payment-types/direct-xrp-payments.md index be61acf0a4..88bbfaf07c 100644 --- a/@i18n/ja/docs/concepts/payment-types/direct-xrp-payments.md +++ b/@i18n/ja/docs/concepts/payment-types/direct-xrp-payments.md @@ -84,7 +84,7 @@ XRP Ledgerでは、支払いを受け取ることができるアドレスは永 - [WebSocketを使用した着信ペイメントの監視](../../tutorials/http-websocket-apis/monitor-incoming-payments-with-websocket.md) - **リファレンス:** - [Paymentトランザクション][] - - [トランザクションの結果](../../references/protocol/transactions/transaction-results/transaction-results.md) + - [トランザクションの結果](../../references/protocol/transactions/transaction-results/index.md) - [account_infoメソッド][] - XRP残高を確認します。 {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/concepts/payment-types/partial-payments.md b/@i18n/ja/docs/concepts/payment-types/partial-payments.md index d5e79a3d56..30aebe2c1a 100644 --- a/@i18n/ja/docs/concepts/payment-types/partial-payments.md +++ b/@i18n/ja/docs/concepts/payment-types/partial-payments.md @@ -51,7 +51,7 @@ Partial Paymentには次の制限事項があります。 - Partial Paymentでは、XRP間の直接決済はできません。この場合、[結果コード][]`temBAD_SEND_XRP_PARTIAL`が返されます。 - ただし、イシュアンスからXRPへの支払またはXRPからイシュアンスへの支払は、Partial Paymentが可能です。 -[結果コード]: ../../references/protocol/transactions/transaction-results/transaction-results.md +[結果コード]: ../../references/protocol/transactions/transaction-results/index.md ### `delivered_amount`フィールド diff --git a/@i18n/ja/docs/concepts/transactions/finality-of-results/index.md b/@i18n/ja/docs/concepts/transactions/finality-of-results/index.md index 40b92e8348..fd1b63f65a 100644 --- a/@i18n/ja/docs/concepts/transactions/finality-of-results/index.md +++ b/@i18n/ja/docs/concepts/transactions/finality-of-results/index.md @@ -27,7 +27,7 @@ labels: ## 未確定の結果はどのように変更できますか? -最初にトランザクションを送信すると、`rippled`サーバーはそのトランザクションを現在のオープンレジャーに暫定的に適用し、その結果から暫定的な[トランザクションの結果](../../../references/protocol/transactions/transaction-results/transaction-results.md)を返します。ただし、トランザクションの最終結果は、暫定的な結果とは大きく異なる場合があります。考えられる理由を以下に示します。 +最初にトランザクションを送信すると、`rippled`サーバーはそのトランザクションを現在のオープンレジャーに暫定的に適用し、その結果から暫定的な[トランザクションの結果](../../../references/protocol/transactions/transaction-results/index.md)を返します。ただし、トランザクションの最終結果は、暫定的な結果とは大きく異なる場合があります。考えられる理由を以下に示します。 - トランザクションは、後のレジャーバージョンまで延期されるか、検証済みレジャーに取り込まれない場合があります。ほとんどの場合、XRP Ledgerでは、すべての有効なトランザクションをできるだけ早く処理するという原則に従います。ただし、次のような例外があります。 @@ -55,6 +55,6 @@ labels: ## 関連項目 - [トランザクションの結果の確認](look-up-transaction-results.md) -- [トランザクション結果のリファレンス](../../../references/protocol/transactions/transaction-results/transaction-results.md) +- [トランザクション結果のリファレンス](../../../references/protocol/transactions/transaction-results/index.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md b/@i18n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md index c8aaad9690..abcfd0b0c7 100644 --- a/@i18n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md +++ b/@i18n/ja/docs/concepts/transactions/finality-of-results/look-up-transaction-results.md @@ -63,7 +63,7 @@ XRP Ledgerは共有システムとなっていて、すべてのデータが公 } ``` -この例では、rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpnというアドレスを持つ[アカウント](../../accounts/index.md)が、[シーケンス番号][] 376を使用して、[AccountSetトランザクション][]を送信したことを示しています。トランザクションの[識別用ハッシュ][]は`017DED8F5E20F0335C6F56E3D5EE7EF5F7E83FB81D2904072E665EEA69402567`で、その[結果](../../../references/protocol/transactions/transaction-results/transaction-results.md)は`tesSUCCESS`です。トランザクションは、検証済みのレジャーバージョン46447423に記録されたため、結果は最終的なものです。 +この例では、rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpnというアドレスを持つ[アカウント](../../accounts/index.md)が、[シーケンス番号][] 376を使用して、[AccountSetトランザクション][]を送信したことを示しています。トランザクションの[識別用ハッシュ][]は`017DED8F5E20F0335C6F56E3D5EE7EF5F7E83FB81D2904072E665EEA69402567`で、その[結果](../../../references/protocol/transactions/transaction-results/index.md)は`tesSUCCESS`です。トランザクションは、検証済みのレジャーバージョン46447423に記録されたため、結果は最終的なものです。 ### ケース: 検証済みレジャーに記録されていない @@ -75,7 +75,7 @@ XRP Ledgerは共有システムとなっていて、すべてのデータが公 ### ケース: 検証済みレジャーに記録されている -トランザクションが検証済みレジャーに記録 _されている_ 場合、[トランザクションメタデータ](../../../references/protocol/transactions/metadata.md)にはトランザクションの処理結果として、レジャーの状態に対して行われたすべての変更を網羅したレポートが含まれます。メタデータの`TransactionResult`フィールドには、以下のような、結果を要約した[トランザクション結果コード](../../../references/protocol/transactions/transaction-results/transaction-results.md)が含まれます。 +トランザクションが検証済みレジャーに記録 _されている_ 場合、[トランザクションメタデータ](../../../references/protocol/transactions/metadata.md)にはトランザクションの処理結果として、レジャーの状態に対して行われたすべての変更を網羅したレポートが含まれます。メタデータの`TransactionResult`フィールドには、以下のような、結果を要約した[トランザクション結果コード](../../../references/protocol/transactions/transaction-results/index.md)が含まれます。 - コード`tesSUCCESS`は、トランザクションが、おおよそ成功したことを示します。 - `tec`-クラスコードは、トランザクションが失敗したことを示します。このことがレジャーの状態に及ぼす影響は、XRP[トランザクションコスト](../transaction-cost.md)を消却し、場合によっては[有効期限切れのオファー](../../tokens/decentralized-exchange/offers.md#オファーの有効期限)の削除および[Payment Channelの閉鎖](../../payment-types/payment-channels.md#payment-channelのライフサイクル)などのブックキーピングを行うことだけです。 @@ -450,6 +450,6 @@ TrustSetトランザクションは、[`RippleState`オブジェクト](../../.. - **リファレンス:** - [レジャーオブジェクトタイプのリファレンス](../../../references/protocol/ledger-data/ledger-entry-types/index.md) - レジャーオブジェクトの使用可能なすべてのタイプのフィールド - [トランザクションのメタデータ](../../../references/protocol/transactions/metadata.md) - メタデータフォーマットとメタデータに表示されるフィールドの概要 - - [トランザクションの結果](../../../references/protocol/transactions/transaction-results/transaction-results.md) - トランザクションのすべての結果コードを掲載した表一覧 + - [トランザクションの結果](../../../references/protocol/transactions/transaction-results/index.md) - トランザクションのすべての結果コードを掲載した表一覧 {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/concepts/transactions/finality-of-results/transaction-malleability.md b/@i18n/ja/docs/concepts/transactions/finality-of-results/transaction-malleability.md index 1df39fb291..5d291e5db6 100644 --- a/@i18n/ja/docs/concepts/transactions/finality-of-results/transaction-malleability.md +++ b/@i18n/ja/docs/concepts/transactions/finality-of-results/transaction-malleability.md @@ -143,7 +143,7 @@ XRP Ledgerとのインフターフェイスに使用するソフトウェアか - **リファレンス:** - [基本的なデータ型 - ハッシュ](../../../references/protocol/data-types/basic-data-types.md#ハッシュ) - [トランザクションの共通フィールド](../../../references/protocol/transactions/common-fields.md#グローバルフラグ) - - [トランザクションの結果](../../../references/protocol/transactions/transaction-results/transaction-results.md) + - [トランザクションの結果](../../../references/protocol/transactions/transaction-results/index.md) - [シリアル化フォーマット](../../../references/protocol/binary-format.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/concepts/transactions/index.md b/@i18n/ja/docs/concepts/transactions/index.md index b6a7ad636c..5f9b92a8b4 100644 --- a/@i18n/ja/docs/concepts/transactions/index.md +++ b/@i18n/ja/docs/concepts/transactions/index.md @@ -63,7 +63,7 @@ XRP Ledgerにトランザクションを送信するには、いくつかの手 3. `rippled`サーバーにトランザクションを送信します。トランザクションが適切に作成されている場合、サーバーはそのトランザクションを現行バージョンのレジャーに暫定的に適用し、そのトランザクションをピアツーピアネットワークの他のメンバーに中継します。 4. [コンセンサスプロセス](../consensus-protocol/index.md)によって、次の検証済みレジャーに含まれる暫定的なトランザクションが決定されます。 5. `rippled`サーバーはそれらのトランザクションを正規順序で前のレジャーに適用し、それらの結果を共有します。 -6. 十分に[信頼できるバリデータ](../networks-and-servers/rippled-server-modes.md#バリデータ)がまったく同じレジャーを作成した場合、そのレジャーは _検証済み_ であると宣言され、そのレジャーの[トランザクションの結果](../../references/protocol/transactions/transaction-results/transaction-results.md)は不変となります。 +6. 十分に[信頼できるバリデータ](../networks-and-servers/rippled-server-modes.md#バリデータ)がまったく同じレジャーを作成した場合、そのレジャーは _検証済み_ であると宣言され、そのレジャーの[トランザクションの結果](../../references/protocol/transactions/transaction-results/index.md)は不変となります。 XRP決済の送信に関する対話型チュートリアルについては、[Send XRP](../../tutorials/how-tos/send-xrp.md)を参照してください。 diff --git a/@i18n/ja/docs/concepts/transactions/transaction-cost.md b/@i18n/ja/docs/concepts/transactions/transaction-cost.md index b8d08846fc..7ee762f216 100644 --- a/@i18n/ja/docs/concepts/transactions/transaction-cost.md +++ b/@i18n/ja/docs/concepts/transactions/transaction-cost.md @@ -133,7 +133,7 @@ XRP LedgerをスパムやDoS攻撃から守るため、各トランザクショ ## トランザクションコストと失敗したトランザクション -トランザクションコストの目的はXRP Ledgerピアツーピアネットワークを過度な負荷から保護することであるため、トランザクションが成功するかどうかにかかわらず、ネットワークに分散されるすべてのトランザクションにコストが適用されます。ただし、共有のグローバルレジャーに作用するため、トランザクションを検証済みレジャーに含める必要があります。したがって、`rippled`サーバーは[`tec`ステータスコード](../../references/protocol/transactions/transaction-results/transaction-results.md)（「tec」は「トランザクションエンジン - 請求手数料のみ」（Transaction Engine - Claimed fee only）を表します）で、失敗したトランザクションをレジャーに含めようとします。 +トランザクションコストの目的はXRP Ledgerピアツーピアネットワークを過度な負荷から保護することであるため、トランザクションが成功するかどうかにかかわらず、ネットワークに分散されるすべてのトランザクションにコストが適用されます。ただし、共有のグローバルレジャーに作用するため、トランザクションを検証済みレジャーに含める必要があります。したがって、`rippled`サーバーは[`tec`ステータスコード](../../references/protocol/transactions/transaction-results/index.md)（「tec」は「トランザクションエンジン - 請求手数料のみ」（Transaction Engine - Claimed fee only）を表します）で、失敗したトランザクションをレジャーに含めようとします。 トランザクションコストは、トランザクションが実際に検証済みレジャーに含められた場合に、送信者のXRP残高から差し引かれるだけです。このことは、トランザクションが成功するか`tec`コードとともに失敗するかにかかわらず適用されます。 diff --git a/@i18n/ja/docs/concepts/transactions/transaction-queue.md b/@i18n/ja/docs/concepts/transactions/transaction-queue.md index 2ba8b0d6d7..69429034b7 100644 --- a/@i18n/ja/docs/concepts/transactions/transaction-queue.md +++ b/@i18n/ja/docs/concepts/transactions/transaction-queue.md @@ -66,7 +66,7 @@ labels: キュー内のトランザクションの数が次のレジャーバージョンの予期サイズを超える場合には、キュー内のトランザクションの正確な順序に基づいて、次の処理レジャーバージョンに追加されるトランザクションが決定します。トランザクションの順序は**検証済みレジャー内でのトランザクションの実行順序には影響しません**。各検証済みレジャーバージョンでは、そのバージョンのトランザクションセットが[正規の順序](../consensus-protocol/consensus-structure.md#検証の計算と共有)で実行されます。 -**注記:**`rippled`がトランザクションをキューに入れるときに付与される暫定的な[トランザクションレスポンスコード](../../references/protocol/transactions/transaction-results/transaction-results.md)は`terQUEUED`です。つまり、トランザクションは今後のレジャーバージョンで成功する見込みです。すべての暫定的なレスポンスコードと同様に、トランザクションが検証済みレジャーに追加されるか、または[完全に無効であると示される](finality-of-results/index.md)までは、トランザクションの結果は最終的ではありません。 +**注記:**`rippled`がトランザクションをキューに入れるときに付与される暫定的な[トランザクションレスポンスコード](../../references/protocol/transactions/transaction-results/index.md)は`terQUEUED`です。つまり、トランザクションは今後のレジャーバージョンで成功する見込みです。すべての暫定的なレスポンスコードと同様に、トランザクションが検証済みレジャーに追加されるか、または[完全に無効であると示される](finality-of-results/index.md)までは、トランザクションの結果は最終的ではありません。 ## 関連項目 diff --git a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index b2c6d39110..634d857851 100644 --- a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md +++ b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md @@ -83,7 +83,7 @@ labels: * `server` - `rippled`サーバーのステータス（ネットワーク接続など）が変更されるたびにメッセージを送信します。 * `ledger` - コンセンサスプロセスで新しい検証済みレジャーが宣言されるたびにメッセージを送信します。 * `transactions` - 決済済みレジャーにトランザクションが追加されるたびにメッセージを送信します。 -* `transactions_proposed` - 決済済みレジャーにトランザクションが追加される場合や、検証済みレジャーにまだ追加されておらず、今後も追加される見込みのない一部のトランザクションが決済済みレジャーに追加される場合に、メッセージを送信します。提案されたすべてのトランザクションが検証前に表示されるわけではありません。**注記:** 検証済みレジャーには[失敗したトランザクションも記録されます](../../../protocol/transactions/transaction-results/transaction-results.md)。これは、このようなトランザクションにはスパム対策のトランザクション手数料が課されるためです。 +* `transactions_proposed` - 決済済みレジャーにトランザクションが追加される場合や、検証済みレジャーにまだ追加されておらず、今後も追加される見込みのない一部のトランザクションが決済済みレジャーに追加される場合に、メッセージを送信します。提案されたすべてのトランザクションが検証前に表示されるわけではありません。**注記:** 検証済みレジャーには[失敗したトランザクションも記録されます](../../../protocol/transactions/transaction-results/index.md)。これは、このようなトランザクションにはスパム対策のトランザクション手数料が課されるためです。 * `validations` - サーバーがバリデータを信頼しているか否かにかかわらず、サーバーが検証メッセージを受信するたびに、メッセージを送信します。（個々の`rippled`は、サーバーが少なくとも定数の信頼できるバリデータから検証メッセージを受信した時点で、レジャーが検証済みであると宣言します。） * `consensus` - サーバーがコンセンサスサイクルのフェーズ（open、establish、acceptedなど）を変更するたびにメッセージを送信します。 * `peer_status` - **（管理者専用）** 接続しているピア`rippled`サーバーに関する情報（特にコンセンサスプロセスに関する情報）。 @@ -354,8 +354,8 @@ labels: | `Field`　　　　　　　　　| 型　　　　　　　　　　　　　| 説明 　　　　　 | |:------------------------|:--------------------------|:-----------------------| | `type` | 文字列 | `transaction`は、トランザクションの通知であることを示します。この通知はさまざまなストリームから送信される可能性があります。 | -| `engine_result` | 文字列 | 文字列の[トランザクション結果コード](../../../protocol/transactions/transaction-results/transaction-results.md) | -| `engine_result_code` | 数値 | 数値の[トランザクションレスポンスコード](../../../protocol/transactions/transaction-results/transaction-results.md)（該当する場合） | +| `engine_result` | 文字列 | 文字列の[トランザクション結果コード](../../../protocol/transactions/transaction-results/index.md) | +| `engine_result_code` | 数値 | 数値の[トランザクションレスポンスコード](../../../protocol/transactions/transaction-results/index.md)（該当する場合） | | `engine_result_message` | 文字列 | 人間が読み取れる形式のトランザクションレスポンスの説明 | | `ledger_current_index` | 数値 - [レジャーインデックス][] | _（未検証のトランザクションのみ）_ このトランザクションが現在提案されている現在進行中の[レジャーバージョン](../../../../concepts/ledgers/index.md)のレジャーインデックス。 | | `ledger_hash` | 文字列 - [ハッシュ][] | _（検証済みのトランザクションのみ）_ このトランザクションを含む レジャーバージョンの識別用ハッシュ。 | diff --git a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md index 596cb69f0d..81f4123e7c 100644 --- a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md +++ b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md @@ -272,7 +272,7 @@ Connecting to 127.0.0.1:5005 | `tx_blob` | 文字列 | トランザクション全体の16進文字列表現 | | `tx_json` | オブジェクト | トランザクション全体のJSON表現 | -**注意:** WebSocketのレスポンスに`"status":"success"`が含まれていても、これはコマンドが正常に受け付けられたことを示すものであり、トランザクションが正常に実行されたことを示しているわけでは _ありません_ 。トランザクションは、さまざまな状況で正常に処理されない可能性があります。例えば、ペイメントの2つのアカウントを接続するトラストラインの欠落や、トランザクション生成後のレジャーの状態の変化などです。問題が特にない場合も、トランザクションが含まれているバージョンのレジャーを閉鎖し検証するまでに数秒かかることがあります。詳細は、[トランザクションのレスポンスの完全なリスト](../../../protocol/transactions/transaction-results/transaction-results.md)を参照してください。トランザクションの結果は、検証済みバージョンのレジャーにトランザクションが表示されるまで、最終的なものと考えないでください。 +**注意:** WebSocketのレスポンスに`"status":"success"`が含まれていても、これはコマンドが正常に受け付けられたことを示すものであり、トランザクションが正常に実行されたことを示しているわけでは _ありません_ 。トランザクションは、さまざまな状況で正常に処理されない可能性があります。例えば、ペイメントの2つのアカウントを接続するトラストラインの欠落や、トランザクション生成後のレジャーの状態の変化などです。問題が特にない場合も、トランザクションが含まれているバージョンのレジャーを閉鎖し検証するまでに数秒かかることがあります。詳細は、[トランザクションのレスポンスの完全なリスト](../../../protocol/transactions/transaction-results/index.md)を参照してください。トランザクションの結果は、検証済みバージョンのレジャーにトランザクションが表示されるまで、最終的なものと考えないでください。 **注意:** このコマンドの結果としてエラーメッセージが表示された場合、リクエストから取得されたシークレットキーがメッセージの中に記述されている可能性があります。（リクエストに含まれているものが署名済みのtx_blobである場合は問題ありません）。これらのエラーが他者から見えない状態であることを確認してください。 diff --git a/@i18n/ja/docs/references/protocol/binary-format.md b/@i18n/ja/docs/references/protocol/binary-format.md index 85203cff9c..ffd8b69329 100644 --- a/@i18n/ja/docs/references/protocol/binary-format.md +++ b/@i18n/ja/docs/references/protocol/binary-format.md @@ -82,7 +82,7 @@ curated_anchors: | `TYPES` | フィールドIDの作成と正規順序でのフィールドのソートのためのデータタイプからその[「タイプコード」](#タイプコード)へのマップ。1未満のコードは実際のデータには含まれません。10000を超えるコードは、他のオブジェクト内部ではシリアル化できない「トランザクション」などの特殊な「上位」オブジェクトタイプを表します。各タイプのシリアル化方法についての詳細は、[タイプリスト](#タイプリスト)を参照してください。 | | `LEDGER_ENTRY_TYPES` | [レジャーオブジェクト](ledger-data/ledger-entry-types/index.md)から対応するデータタイプへのマップ。これはレジャー状態データと、処理されたトランザクションの[メタデータ](transactions/metadata.md)の「affected nodes」セクションに含まれます。 | | `FIELDS` | トランザクション、レジャーオブジェクト、あるいはその他のデータに含まれる可能性があるすべてのフィールドを表すタプルからなるソート済み配列。各タプルの1番目のメンバーはフィールドの文字列名であり、2番目のメンバーはそのフィールドのプロパティーが含まれているオブジェクトです。（これらのフィールドの定義については、以下の「フィールドプロパティー」の表を参照してください。） | -| `TRANSACTION_RESULTS` | [トランザクション結果コード](transactions/transaction-results/transaction-results.md)から対応する数値へのマップ。レジャーに含まれない結果タイプにはマイナスの値が含まれています。`tesSUCCESS`に数値0が含まれています。[`tec`クラスコード](transactions/transaction-results/tec-codes.md)は、レジャーに含まれている失敗を示しています。 | +| `TRANSACTION_RESULTS` | [トランザクション結果コード](transactions/transaction-results/index.md)から対応する数値へのマップ。レジャーに含まれない結果タイプにはマイナスの値が含まれています。`tesSUCCESS`に数値0が含まれています。[`tec`クラスコード](transactions/transaction-results/tec-codes.md)は、レジャーに含まれている失敗を示しています。 | | `TRANSACTION_TYPES` | [トランザクションのタイプ](transactions/types/index.md)から対応する数値へのマップ。 | 署名と送信のためにトランザクションをシリアル化するという目的から、`FIELDS`、`TYPES`、および`TRANSACTION_TYPES`フィールドが必要です。 diff --git a/@i18n/ja/docs/references/protocol/transactions/transaction-results/transaction-results.md b/@i18n/ja/docs/references/protocol/transactions/transaction-results/index.md similarity index 100% rename from @i18n/ja/docs/references/protocol/transactions/transaction-results/transaction-results.md rename to @i18n/ja/docs/references/protocol/transactions/transaction-results/index.md diff --git a/@i18n/ja/docs/references/protocol/transactions/types/accountdelete.md b/@i18n/ja/docs/references/protocol/transactions/types/accountdelete.md index 1eb83a51b7..205126d2f9 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/accountdelete.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/accountdelete.md @@ -39,7 +39,7 @@ AccountDeleteトランザクションは、XRP Ledgerで[アカウント](../../ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-----------|:------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammbid.md b/@i18n/ja/docs/references/protocol/transactions/types/ammbid.md index 04ce4e1c63..d10ff7150a 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammbid.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammbid.md @@ -126,7 +126,7 @@ R = B × (1 - t) ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:------------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammcreate.md b/@i18n/ja/docs/references/protocol/transactions/types/ammcreate.md index 8d8abae6e2..390a154874 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammcreate.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammcreate.md @@ -53,7 +53,7 @@ AMMを表す[AMMエントリ][]と[特殊なAccountRootエントリ](../../ledge ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:--------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammdelete.md b/@i18n/ja/docs/references/protocol/transactions/types/ammdelete.md index 784263b65e..3be9b7b655 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammdelete.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammdelete.md @@ -46,7 +46,7 @@ _([AMM amendment][] {% not-enabled /%} が必要です)_ ## エラーケース -AMMCreateトランザクションでは、すべてのトランザクションで発生する可能性のあるエラーの他に、以下の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +AMMCreateトランザクションでは、すべてのトランザクションで発生する可能性のあるエラーの他に、以下の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:--------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammdeposit.md b/@i18n/ja/docs/references/protocol/transactions/types/ammdeposit.md index a1446bff36..9c84ab2e2b 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammdeposit.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammdeposit.md @@ -122,7 +122,7 @@ AMMDepositトランザクションは、以下のような[`Flags`フィール ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:------------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammvote.md b/@i18n/ja/docs/references/protocol/transactions/types/ammvote.md index c6fbb2fdf8..dae6b3fa3a 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammvote.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammvote.md @@ -44,7 +44,7 @@ _([AMM amendment][] {% not-enabled /%}が必要です。)_ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:------------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ammwithdraw.md b/@i18n/ja/docs/references/protocol/transactions/types/ammwithdraw.md index 604e06e77b..e777b3a69b 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ammwithdraw.md @@ -107,7 +107,7 @@ AMMWithdrawトランザクションは、以下のように[`Flags`フィール ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-------------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/clawback.md b/@i18n/ja/docs/references/protocol/transactions/types/clawback.md index 034a174525..cf5bf66349 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/clawback.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/clawback.md @@ -41,7 +41,7 @@ Clawback機能はデフォルトで無効になっています。使用するに ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-----------|:------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/diddelete.md b/@i18n/ja/docs/references/protocol/transactions/types/diddelete.md index 6c9d4a4545..a36d12abe3 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/diddelete.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/diddelete.md @@ -34,7 +34,7 @@ _([DID Amendment][] {% not-enabled /%} が必要です。)_ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーの他に、{% $frontmatter.seo.title %}トランザクションでは以下の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります： +すべてのトランザクションで発生する可能性のあるエラーの他に、{% $frontmatter.seo.title %}トランザクションでは以下の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります： | エラーコード | 説明 | |:--------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/didset.md b/@i18n/ja/docs/references/protocol/transactions/types/didset.md index 6dbef15dee..f0478317bc 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/didset.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/didset.md @@ -45,7 +45,7 @@ _([DID Amendment][] {% not-enabled /%} が必要です。)_ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:--------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/@i18n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md index a547970943..ba9aca8bb0 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -90,7 +90,7 @@ _([NonFungibleTokensV1_1 amendment][]により追加されました)_ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-----------------------------------|:----------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/nftokenburn.md b/@i18n/ja/docs/references/protocol/transactions/types/nftokenburn.md index bbcca425fb..7732cadacb 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/nftokenburn.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/nftokenburn.md @@ -39,7 +39,7 @@ _([NonFungibleTokensV1_1 amendment][]により追加されました)_ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-------------------|:--------------------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md b/@i18n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md index 5f65d75644..4a55cc9266 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -49,7 +49,7 @@ IDが[NFTokenOffer](../../ledger-data/ledger-entry-types/nftokenoffer.md)オブ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-------------------|:--------------------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md b/@i18n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md index 487a598eb1..e70fb854f0 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -50,7 +50,7 @@ NFTokenCreateOfferタイプのトランザクションは、以下のように[` ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:---------------------------------|:------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/nftokenmint.md b/@i18n/ja/docs/references/protocol/transactions/types/nftokenmint.md index 83bfca1492..0ce4f6898d 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/nftokenmint.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/nftokenmint.md @@ -103,7 +103,7 @@ NFTokenMint型のトランザクションでは、以下のように[`Flags`フ ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:------------------------------|:---------------------------------------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/offercreate.md b/@i18n/ja/docs/references/protocol/transactions/types/offercreate.md index 7bb227b8ed..9891ff96b2 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/offercreate.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/offercreate.md @@ -49,8 +49,8 @@ OfferCreate型のトランザクションについては、[`Flags`フィール | フラグ名 | 16進数 | 10進数 | 説明 | |:----------------------|:-------------|:--------------|:-------------------| | `tfPassive` | `0x00010000` | 65536 | 有効な場合、オファーはオファーが完全に約定するオファーを消費せず、代わりにレジャーのOfferオブジェクトになります。それはまだクロスしたオファーを消費します。 | -| `tfImmediateOrCancel` | `0x00020000` | 131072 | オファーを[IOC注文](http://en.wikipedia.org/wiki/Immediate_or_cancel)として扱います。有効な場合、オファーはレジャーオブジェクトにはなりません。レジャー内の既存のオファーと約定させようとするだけです。即時にオファーがどのオファーとも約定しない場合、どの通貨とも取引せずに「正常に」実行します。この場合、トランザクションは`tesSUCCESS`の[結果コード](../transaction-results/transaction-results.md)を返しますが、レジャー内には、[Offerオブジェクト](../../ledger-data/ledger-entry-types/offer.md)を作成しません。 | -| `tfFillOrKill` | `0x00040000` | 262144 | オファーを[FOK注文](http://en.wikipedia.org/wiki/Fill_or_kill)として扱います。レジャー内の既存のオファーのみを約定しようとします。またこれは、全`TakerPays`の数量が取得できる場合に限られます。[fix1578 amendment][]が有効な場合でオファーを配置した時に実行できない場合、トランザクションは`tecKILLED`の[結果コード](../transaction-results/transaction-results.md)を返します。そうでない場合は、トランザクションは、どの通貨とも取り引きせずにキャンセルされた場合でも`tesSUCCESS`の結果コードを返します。 | +| `tfImmediateOrCancel` | `0x00020000` | 131072 | オファーを[IOC注文](http://en.wikipedia.org/wiki/Immediate_or_cancel)として扱います。有効な場合、オファーはレジャーオブジェクトにはなりません。レジャー内の既存のオファーと約定させようとするだけです。即時にオファーがどのオファーとも約定しない場合、どの通貨とも取引せずに「正常に」実行します。この場合、トランザクションは`tesSUCCESS`の[結果コード](../transaction-results/index.md)を返しますが、レジャー内には、[Offerオブジェクト](../../ledger-data/ledger-entry-types/offer.md)を作成しません。 | +| `tfFillOrKill` | `0x00040000` | 262144 | オファーを[FOK注文](http://en.wikipedia.org/wiki/Fill_or_kill)として扱います。レジャー内の既存のオファーのみを約定しようとします。またこれは、全`TakerPays`の数量が取得できる場合に限られます。[fix1578 amendment][]が有効な場合でオファーを配置した時に実行できない場合、トランザクションは`tecKILLED`の[結果コード](../transaction-results/index.md)を返します。そうでない場合は、トランザクションは、どの通貨とも取り引きせずにキャンセルされた場合でも`tesSUCCESS`の結果コードを返します。 | | `tfSell` | `0x00080000` | 524288 | 取引所で`TakerPays`Amountよりも多く取得することになっても、`TakerGets` Amountを交換します。 | ## エラーケース diff --git a/@i18n/ja/docs/references/protocol/transactions/types/payment.md b/@i18n/ja/docs/references/protocol/transactions/types/payment.md index ec2a5045a1..68568882a1 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/payment.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/payment.md @@ -126,7 +126,7 @@ XRP Ledgerでは、ある通貨での入金額と別の通貨での出金額の [*tfLimitQuality*フラグ](#paymentのフラグ)を使用すると、実行する変換のクオリティについて下限を設定できます。このクオリティの制限は、宛先の`Amount`を`SendMax`の金額（通貨にかかわらず金額のみ）で除算することによって定義します。設定した場合、支払い処理エンジンは、クオリティの制限よりもクオリティ（為替レート）が低い（数値が小さい）パスの使用を回避します。 -tfLimitQualityフラグは、それ自体、トランザクションが成功する状況を減少させるものになります。具体的には、好ましくない変換が支払いの一部で使用されている場合、支払いにおける変換の*平均*的なクオリティが全体としてクオリティの制限と同一か、それ以上であっても、支払いが拒否されます。支払いがこの形で拒否される場合、[トランザクションの結果](../transaction-results/transaction-results.md)は`tecPATH_DRY`です。 +tfLimitQualityフラグは、それ自体、トランザクションが成功する状況を減少させるものになります。具体的には、好ましくない変換が支払いの一部で使用されている場合、支払いにおける変換の*平均*的なクオリティが全体としてクオリティの制限と同一か、それ以上であっても、支払いが拒否されます。支払いがこの形で拒否される場合、[トランザクションの結果](../transaction-results/index.md)は`tecPATH_DRY`です。 次の例を考えてみます。100人民元（`Amount` = 100人民元）を最大20米ドル（`SendMax` = 20米ドル）と引き換えに相手方に送金しようとする場合、クオリティの制限は`5`です。あるトレーダーが15米ドルと引き換えに95人民元をオファーしているものの（米ドルあたり約`6.3`人民元の比率）、市場の次善のオファーが2ドルに対して5人民元であるとします（米ドルあたり`2.5`人民元の比率）。両方のオファーを受諾して相手方に100人民元を送金する場合、送信元が負担するコストは17米ドルであり、平均のクオリティは約`5.9`です。 diff --git a/@i18n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md b/@i18n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md index bf028a3fa5..759e2c7aa7 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -37,7 +37,7 @@ PaymentChannelFundの例: ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:-----------|:------------| diff --git a/@i18n/ja/docs/references/protocol/transactions/types/ticketcreate.md b/@i18n/ja/docs/references/protocol/transactions/types/ticketcreate.md index 33e7d08268..b75b2355bc 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/ticketcreate.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/ticketcreate.md @@ -39,7 +39,7 @@ TicketCreateトランザクションは、1つまたは複数の[シーケンス ## エラーケース -すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/transaction-results.md)が発生する可能性があります。 +すべてのトランザクションで発生する可能性のあるエラーに加えて、{% $frontmatter.seo.title %}トランザクションでは、次の[トランザクション結果コード](../transaction-results/index.md)が発生する可能性があります。 | エラーコード | 説明 | |:--------------------------|:-------------------------------------------------| diff --git a/@i18n/ja/docs/tutorials/tasks/index.md b/@i18n/ja/docs/tutorials/how-tos/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/index.md rename to @i18n/ja/docs/tutorials/how-tos/index.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md similarity index 98% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md index 4e0badcf4b..860ddbde37 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md +++ b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md @@ -498,6 +498,6 @@ else: - 結果が0でない場合は `lsfDisableMaster` の値と等しく、 **マスターキーが正常に無効化されたこと** を示します。 - 結果が0の場合は、そのアカウントのマスターキーが無効になっていないことを示します。 -結果が予想と異なる場合は、前の手順で送信したトランザクションが正常に実行されたかどうかを確認してください。それは、その口座のトランザクション履歴（[account_tx メソッド][]）の中で最も新しいもので、結果コード `tesSUCCESS` がついているはずです。それ以外の[結果コード](../../../references/protocol/transactions/transaction-results/transaction-results.md)が表示された場合、そのトランザクションは正常に実行されませんでした。エラーの原因によっては、これらの手順を最初からやり直した方がよいかもしれません。 +結果が予想と異なる場合は、前の手順で送信したトランザクションが正常に実行されたかどうかを確認してください。それは、その口座のトランザクション履歴（[account_tx メソッド][]）の中で最も新しいもので、結果コード `tesSUCCESS` がついているはずです。それ以外の[結果コード](../../../references/protocol/transactions/transaction-results/index.md)が表示された場合、そのトランザクションは正常に実行されませんでした。エラーの原因によっては、これらの手順を最初からやり直した方がよいかもしれません。 {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/index.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/index.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/index.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/offline-account-setup.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/offline-account-setup.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/require-destination-tags.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/require-destination-tags.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/send-a-multi-signed-transaction.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/send-a-multi-signed-transaction.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction.md diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md similarity index 95% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md index f666e4cb27..a7d95fe43c 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md +++ b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md @@ -140,7 +140,7 @@ Connecting to 127.0.0.1:5005 } ``` -[トランザクションの結果](../../../references/protocol/transactions/transaction-results/transaction-results.md)が[**tesSUCCESS**](../../../references/protocol/transactions/transaction-results/tes-success.md)であることを確認します。それ以外の場合、トランザクションは失敗しています。スタンドアロンモードまたは本番環境以外のネットワークで問題が発生した場合は、[マルチシグが有効であること](../../../infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md#新しいジェネシスレジャーの設定)を確認してください。 +[トランザクションの結果](../../../references/protocol/transactions/transaction-results/index.md)が[**tesSUCCESS**](../../../references/protocol/transactions/transaction-results/tes-success.md)であることを確認します。それ以外の場合、トランザクションは失敗しています。スタンドアロンモードまたは本番環境以外のネットワークで問題が発生した場合は、[マルチシグが有効であること](../../../infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md#新しいジェネシスレジャーの設定)を確認してください。 **注記:** [MultiSignReserve Amendment][]が有効ではない場合は、SignerListのメンバーの増加に応じて、アドレスの[所有者準備金](../../../concepts/accounts/reserves.md#所有者準備金)のXRP額を増加する必要があります。アドレスに十分なXRPがないと、トランザクションは[tecINSUFFICIENT_RESERVE](../../../references/protocol/transactions/transaction-results/tec-codes.md)で失敗します。[MultiSignReserve Amendment][]が有効な場合は、SignerListの署名者の数に関係なく[所有者準備金](../../../concepts/accounts/reserves.md#所有者準備金)として必要なXRPは5 XRPです。関連項目: [SignerListと準備金](../../../references/protocol/ledger-data/ledger-entry-types/signerlist.md#signerlistと準備金) diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/use-tickets.md b/@i18n/ja/docs/tutorials/how-tos/manage-account-settings/use-tickets.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/manage-account-settings/use-tickets.md rename to @i18n/ja/docs/tutorials/how-tos/manage-account-settings/use-tickets.md diff --git a/@i18n/ja/docs/tutorials/tasks/send-xrp.md b/@i18n/ja/docs/tutorials/how-tos/send-xrp.md similarity index 99% rename from @i18n/ja/docs/tutorials/tasks/send-xrp.md rename to @i18n/ja/docs/tutorials/how-tos/send-xrp.md index 3e0d37010e..aae9f39db0 100644 --- a/@i18n/ja/docs/tutorials/tasks/send-xrp.md +++ b/@i18n/ja/docs/tutorials/how-tos/send-xrp.md @@ -177,7 +177,7 @@ xrpl.jsの[Wallet.sign()メソッド](https://js.xrpl.org/classes/Wallet.html#si - トランザクションの送信に必要なTest Net XRPが十分にあるか。送金できるXRPの額は、[必要準備金](../../concepts/accounts/reserves.md)によって制限されています。現時点では、20XRPに加えて、レジャー内に保有している各「オブジェクト」につき5XRPずつ追加となります。（Test Net Faucetを使用して新しいアドレスを生成した場合は、保有するオブジェクトはありません。） - テストネットワークのサーバーに接続しているか。 -他の可能性については、[トランザクション結果](../../references/protocol/transactions/transaction-results/transaction-results.md)の完全なリストを参照してください。 +他の可能性については、[トランザクション結果](../../references/protocol/transactions/transaction-results/index.md)の完全なリストを参照してください。 {% interactive-block label="Submit" steps=$frontmatter.steps %} diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/index.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/index.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/index.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cancel-a-check.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cancel-a-check.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cancel-a-check.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cancel-a-check.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md similarity index 96% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md index 696d8f783e..f9f96b7c78 100644 --- a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md +++ b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md @@ -137,7 +137,7 @@ Checkを変動金額で換金するためのトランザクションを準備す ### エラー処理 -[](../../../../references/protocol/transactions/transaction-results/transaction-results.md)Checkの換金が`tec`クラスコードで失敗した場合は、[すべてのトランザクションレスポンスのリスト](../../../../references/protocol/transactions/transaction-results/transaction-results.md)でコードを確認し、適切に対処してください。CheckCashトランザクションでよく返される結果コードの一部を次に示します。 +[](../../../../references/protocol/transactions/transaction-results/index.md)Checkの換金が`tec`クラスコードで失敗した場合は、[すべてのトランザクションレスポンスのリスト](../../../../references/protocol/transactions/transaction-results/index.md)でコードを確認し、適切に対処してください。CheckCashトランザクションでよく返される結果コードの一部を次に示します。 | 結果コード | 意味 | 対処 | |-------------|---------|----------------| diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/look-up-checks-by-recipient.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks-by-recipient.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/look-up-checks-by-recipient.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks-by-recipient.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/send-a-check.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/send-a-check.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/send-a-check.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/send-a-check.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/use-checks.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/use-checks.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-checks/use-checks.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/use-checks.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/cancel-an-expired-escrow.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/cancel-an-expired-escrow.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/cancel-an-expired-escrow.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/cancel-an-expired-escrow.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/index.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/index.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/index.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/look-up-escrows.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/look-up-escrows.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/look-up-escrows.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/look-up-escrows.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md similarity index 98% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md index 1fb00e5408..6bdcfbd67d 100644 --- a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md +++ b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md @@ -128,7 +128,7 @@ print(cancel_after) `FinishAfter`の時刻が経過した後で資金のリリースを実行する[EscrowFinishトランザクション][]に[署名して送信](../../../../concepts/transactions/index.md#トランザクションへの署名とトランザクションの送信)します。トランザクションの`Owner`フィールドにEscrowCreateトランザクションの`Account`アドレスを設定し、`OfferSequence` にEscrowCreateトランザクションの`Sequence`番号を設定します。`Condition`フィールドと`Fulfillment`フィールドに、ステップ1で生成した条件値とフルフィルメント値をそれぞれ16進数で設定します。フルフィルメントのサイズ（バイト数）に基づいて`Fee`（[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)）の値を設定します。条件付きEscrowFinishでは、少なくとも330 drop（XRP）と、フルフィルメントのサイズで16バイトごとに10 dropが必要です。 -**注記:** EscrowCreateトランザクションに`FinishAfter`フィールドが含まれている場合、Escrowの条件として正しいフルフィルメントを指定しても、この時刻よりも前の時点ではこのトランザクションを実行できません。前に閉鎖されたレジャーの閉鎖時刻が`FinishAfter`の時刻よりも前である場合、EscrowFinishトランザクションは[結果コード](../../../../references/protocol/transactions/transaction-results/transaction-results.md)`tecNO_PERMISSION`で失敗します。 +**注記:** EscrowCreateトランザクションに`FinishAfter`フィールドが含まれている場合、Escrowの条件として正しいフルフィルメントを指定しても、この時刻よりも前の時点ではこのトランザクションを実行できません。前に閉鎖されたレジャーの閉鎖時刻が`FinishAfter`の時刻よりも前である場合、EscrowFinishトランザクションは[結果コード](../../../../references/protocol/transactions/transaction-results/index.md)`tecNO_PERMISSION`で失敗します。 Escrowが有効期限切れの場合は、[Escrowの取消し](cancel-an-expired-escrow.md)だけが可能です。 diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/send-a-time-held-escrow.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-time-held-escrow.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/send-a-time-held-escrow.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-time-held-escrow.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md b/@i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-payment-channels/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md rename to @i18n/ja/docs/tutorials/how-tos/use-specialized-payment-types/use-payment-channels/index.md diff --git a/@i18n/ja/docs/tutorials/tasks/use-tokens/index.md b/@i18n/ja/docs/tutorials/how-tos/use-tokens/index.md similarity index 100% rename from @i18n/ja/docs/tutorials/tasks/use-tokens/index.md rename to @i18n/ja/docs/tutorials/how-tos/use-tokens/index.md diff --git a/@i18n/ja/docs/tutorials/http-websocket-apis/monitor-incoming-payments-with-websocket.md b/@i18n/ja/docs/tutorials/http-websocket-apis/monitor-incoming-payments-with-websocket.md index 33bb7ee44c..03f7048ae0 100644 --- a/@i18n/ja/docs/tutorials/http-websocket-apis/monitor-incoming-payments-with-websocket.md +++ b/@i18n/ja/docs/tutorials/http-websocket-apis/monitor-incoming-payments-with-websocket.md @@ -343,7 +343,7 @@ WS_HANDLERS["transaction"] = log_tx - **`validated`フィールド**は、トランザクションの結果が[最終的である](../../concepts/transactions/finality-of-results/index.md)ことを示します。これは、`accounts`をサブスクライブする場合に常に当てはまりますが、`accounts_proposed`または`transactions_proposed`ストリーム _も_ サブスクライブしている場合は、サーバーは未確認のトランザクションに関して同様のメッセージを同じ接続で送信します。予防策として、`validated`フィールドを常に確認することをお勧めします。 -- **`meta.TransactionResult`フィールド**は、[トランザクションの結果](../../references/protocol/transactions/transaction-results/transaction-results.md)です。結果が`tesSUCCESS`でない場合は、トランザクションは失敗したため、値を送信できません。 +- **`meta.TransactionResult`フィールド**は、[トランザクションの結果](../../references/protocol/transactions/transaction-results/index.md)です。結果が`tesSUCCESS`でない場合は、トランザクションは失敗したため、値を送信できません。 - **`transaction.Account`** フィールドはトランザクションの送信元です。他の人が送信したトランザクションのみを探している場合は、このフィールドがあなたのアドレスと一致するトランザクションを無視できます（自身に対するクロスカレンシー支払いが _可能である_ 点に注意してください）。 @@ -508,6 +508,6 @@ $("#tx_read").click((event) => { - **リファレンス:** - [トランザクションのタイプ](../../references/protocol/transactions/types/index.md) - [トランザクションのメタデータ](../../references/protocol/transactions/metadata.md) - メタデータフォーマットとメタデータに表示されるフィールドの概要 - - [トランザクションの結果](../../references/protocol/transactions/transaction-results/transaction-results.md) - トランザクションのすべての結果コードを掲載した表一覧 + - [トランザクションの結果](../../references/protocol/transactions/transaction-results/index.md) - トランザクションのすべての結果コードを掲載した表一覧 {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@i18n/ja/resources/contribute-code/create-custom-transactors.md b/@i18n/ja/resources/contribute-code/create-custom-transactors.md index ee2a9ca510..212ef5418f 100644 --- a/@i18n/ja/resources/contribute-code/create-custom-transactors.md +++ b/@i18n/ja/resources/contribute-code/create-custom-transactors.md @@ -81,7 +81,7 @@ public: - [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp) - [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp) --` rippled` はトランザクションの結果を結果コードで表します。[トランザクションの結果](../../docs/references/protocol/transactions/transaction-results/transaction-results.md)をご覧ください。 +-` rippled` はトランザクションの結果を結果コードで表します。[トランザクションの結果](../../docs/references/protocol/transactions/transaction-results/index.md)をご覧ください。 ```c++ CreateCheck::preflight(PreflightContext const& ctx) diff --git a/@i18n/ja/resources/known-amendments.md b/@i18n/ja/resources/known-amendments.md index 9c7a936d8e..555d5615a0 100644 --- a/@i18n/ja/resources/known-amendments.md +++ b/@i18n/ja/resources/known-amendments.md @@ -1111,7 +1111,7 @@ XRP Ledgerの分散型取引所において、オファーの掛け合わせの 署名者は資金供給のあるアドレスでも資金供給のないアドレスでも可能です。署名者リストのうち資金供給のあるアドレスは、レギュラーキー（定義済みの場合）またはマスターキー（無効でない場合）を使用して署名できます。資金供給のないアドレスは、マスターキーを使用して署名できます。マルチシグトランザクションは、レギュラーキーで署名されたトランザクションと同じ権限を持ちます。 -SignerListを持つアドレスは、レギュラーキーが定義されていなくてもマスターキーを無効にすることができます。また、SignerListを持つアドレスは、マスターキーが無効な場合でもレギュラーキーを削除することができます。`tecMASTER_DISABLED`トランザクション結果コードは`tecNO_ALTERNATIVE_KEY`に名前が変更されます。`tecNO_REGULAR_KEY`トランザクション結果コードは廃止となり、`tecNO_ALTERNATIVE_KEY`に代わります。さらに、この修正は以下の新しい[トランザクション結果コード](../docs/references/protocol/transactions/transaction-results/transaction-results.md)を追加します。 +SignerListを持つアドレスは、レギュラーキーが定義されていなくてもマスターキーを無効にすることができます。また、SignerListを持つアドレスは、マスターキーが無効な場合でもレギュラーキーを削除することができます。`tecMASTER_DISABLED`トランザクション結果コードは`tecNO_ALTERNATIVE_KEY`に名前が変更されます。`tecNO_REGULAR_KEY`トランザクション結果コードは廃止となり、`tecNO_ALTERNATIVE_KEY`に代わります。さらに、この修正は以下の新しい[トランザクション結果コード](../docs/references/protocol/transactions/transaction-results/index.md)を追加します。 * `temBAD_SIGNER` * `temBAD_QUORUM` diff --git a/_code-samples/create-amm/README.md b/_code-samples/create-amm/README.md index 4b8518ef2d..a29de875e9 100644 --- a/_code-samples/create-amm/README.md +++ b/_code-samples/create-amm/README.md @@ -1,3 +1,3 @@ # Create AMM -Code samples for the [Create an Automated Market Maker tutorial](../../docs/tutorials/tasks/use-tokens/create-an-automated-market-maker.md), showing how to make set up a new AMM. \ No newline at end of file +Code samples for the [Create an Automated Market Maker tutorial](../../docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md), showing how to make set up a new AMM. diff --git a/blog/2024/get-ready-for-amm.md b/blog/2024/get-ready-for-amm.md new file mode 100644 index 0000000000..b85cfd93a5 --- /dev/null +++ b/blog/2024/get-ready-for-amm.md @@ -0,0 +1,29 @@ +# Get Ready for AMM + +The [AMM Amendment](/resources/known-amendments#amm) to the XRP Ledger protocol, which adds Automated Market Maker functionality, is on track to become enabled on Mainnet on 2024-03-22. If it maintains support from a supermajority of validators and becomes enabled as expected, this represents the culmination of a 2-year project to bring AMM to the XRPL, starting from the XLS-30 draft specification proposed by Aanchal Malhotra and David Schwartz of Ripple and incorporating the work and feedback of numerous contributors in the XRPL community during that time. + +Any server that is currently working on Mainnet should continue to work after AMM gets enabled, since the Clawback amendment from the same release went live on 2024-02-08. However, it's still a good idea to update to the latest version, [`rippled` 2.1.0](./rippled-2.1.0.md), to take advantage of performance improvements, bug fixes, and to be ready for other amendments that are currently open for voting. + + + +## Background + +The XRP Ledger has included a central limit order book decentralized exchange (CLOB DEX) since its inception, but other blockchains largely moved in the direction of facilitating currency exchanges through Automated Market Makers (AMMs), often using a "constant product" algorithm. In both systems, users offer some of their assets for exchange on-ledger, and the blockchain matches those with users trying to acquire specific assets; the users providing the assets take on _currency risk_, the possibility that exchange rates will move not in their favor. In the CLOB DEX, users explicitly set the price they're willing to exchange, whereas in an AMM a mathematical formula sets the price based on the supply and demand of currencies involved. In both cases, the market works most efficiently when there is a high volume being supplied and exchanged. + +Advantages of a CLOB DEX include fine-grained control over amounts and prices, and unlike with an AMM, the offered funds aren't locked up while waiting for a match. (For example, using the CLOB DEX, one trader can offer up the same $100 for EUR, CAD, JPY, and so on, giving some or all of it to whoever comes first.) Advantages of an AMM include the simplicity of not needing to manually update exchange rates or add new offers as volume flows back and forth. (For example, if the flows between two assets are mostly one-sided, the price to exchange via the AMM will get steadily more expensive to reflect the imbalance of supply and demand, whereas in the CLOB DEX the traders would have to explicitly cancel their old offers and place new ones at higher prices.) + +The AMM amendment adds Automated Market Makers that are designed to synergize with the CLOB DEX to bring traders the flexibility to provide liquidity in whatever method suits them best. Currency trades can automatically use a combination of the AMM and CLOB DEX to achieve the best rate. Also, unlike the AMMs on other blockchains, the XRP Ledger's AMM comes with a fee auction mechanism where liquidity providers can bid on the opportunity to trade against the AMM with reduced fees. + +## Action Needed + +If you run a tool that parses full ledgers or transaction metadata, you need to be ready for AMM-related data types to start appearing on Mainnet after the amendment becomes enabled. New data to look out for include 6 new AMM-related [transaction types](../../docs/references/protocol/transactions/types/index.md), a new [AMM ledger entry type](../../docs/references/protocol/ledger-data/ledger-entry-types/amm.md), a new `AMMID` field in some `AccountRoot` ledger entries, and several new [transaction result codes](../../docs/references/protocol/transactions/transaction-results/index.md) that the new transaction types can produce. + +## Using AMM + +If you want to use AMM after the amendment goes live, the first step is to [Create an Automated Maker](../../docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md) for the currency pair you want to trade. Only the first user for any given currency pair needs to do this, though; other users can deposit to the existing AMM to get in on the action. + +There are no special steps to use an AMM when trading currencies on the XRP Ledger. If you follow the standard steps to [Trade in the DEX](../../docs/tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md), and there's an AMM for the currency pair you're trading, your transaction automatically uses the AMM when doing so produces a better rate than consuming orders from the order book. + +## Further Reading + +For an overview of how the XRP Ledger's AMM works in greater detail, see [What Is An Automated Market Maker?](../../docs/concepts/tokens/decentralized-exchange/automated-market-makers.md). diff --git a/blog/sidebars.yaml b/blog/sidebars.yaml index 21d0f90767..d14af2f9e0 100644 --- a/blog/sidebars.yaml +++ b/blog/sidebars.yaml @@ -5,6 +5,7 @@ - group: '2024' expanded: false items: + - page: 2024/get-ready-for-amm.md - page: 2024/verifyed.md - page: 2024/how-to-mint-nfts.md - page: 2024/rippled-2.1.0.md diff --git a/docs/_snippets/common-links.md b/docs/_snippets/common-links.md index 7cfbb24af9..c87417a201 100644 --- a/docs/_snippets/common-links.md +++ b/docs/_snippets/common-links.md @@ -609,7 +609,7 @@ [random method]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md [random メソッド]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md [randomメソッド]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md -[result code]: /docs/references/protocol/transactions/transaction-results/transaction-results.md +[result code]: /docs/references/protocol/transactions/transaction-results/index.md [ripple-lib]: https://github.com/XRPLF/xrpl.js [ripple_path_find command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md [ripple_path_find method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md diff --git a/docs/_snippets/data_types/address.md b/docs/_snippets/data_types/address.md index c0163b8140..9db407e60f 100644 --- a/docs/_snippets/data_types/address.md +++ b/docs/_snippets/data_types/address.md @@ -1,4 +1,4 @@ -Accounts in the XRP Ledger are identified by an address in the XRP Ledger's [base58][] format. The address is derived from the account's master [public key](https://en.wikipedia.org/wiki/Public-key_cryptography), which is in turn derived from a secret key. An address is represented as a string in JSON and has the following characteristics: +Accounts in the XRP Ledger are identified by an address in the XRP Ledger's [base58](../../references/protocol/data-types/base58-encodings.md) format. The address is derived from the account's master [public key](https://en.wikipedia.org/wiki/Public-key_cryptography), which is in turn derived from a secret key. An address is represented as a string in JSON and has the following characteristics: * Between 25 and 35 characters in length * Starts with the character `r` diff --git a/docs/_snippets/tx-metadata-field-table.md b/docs/_snippets/tx-metadata-field-table.md index 4e348e1ef7..c9e99deee5 100644 --- a/docs/_snippets/tx-metadata-field-table.md +++ b/docs/_snippets/tx-metadata-field-table.md @@ -3,5 +3,5 @@ | `AffectedNodes` | Array | List of [ledger entries](../references/protocol/ledger-data/ledger-entry-types/index.md) that were created, deleted, or modified by this transaction, and specific changes to each. | | `DeliveredAmount` | [Currency Amount][] | _(May be omitted)_ For a [partial payment](../concepts/payment-types/partial-payments.md), this field records the amount of currency actually delivered to the destination. To avoid errors when reading transactions, instead use the `delivered_amount` field, which is provided for all Payment transactions, partial or not. | | `TransactionIndex` | Unsigned Integer | The transaction's position within the ledger that included it. This is zero-indexed. (For example, the value `2` means it was the 3rd transaction in that ledger.) | -| `TransactionResult` | String | A [result code](../references/protocol/transactions/transaction-results/transaction-results.md) indicating whether the transaction succeeded or how it failed. | +| `TransactionResult` | String | A [result code](../references/protocol/transactions/transaction-results/index.md) indicating whether the transaction succeeded or how it failed. | | [`delivered_amount`](../references/protocol/transactions/metadata.md#delivered_amount) | [Currency Amount][] | _(Omitted for non-Payment transactions)_ The [Currency Amount][] actually received by the `Destination` account. Use this field to determine how much was delivered, regardless of whether the transaction is a [partial payment](../concepts/payment-types/partial-payments.md). See [this description](../references/protocol/transactions/metadata.md#delivered_amount) for details. | diff --git a/docs/concepts/consensus-protocol/consensus-structure.md b/docs/concepts/consensus-protocol/consensus-structure.md index 7a92e06d0e..790f235b91 100644 --- a/docs/concepts/consensus-protocol/consensus-structure.md +++ b/docs/concepts/consensus-protocol/consensus-structure.md @@ -51,7 +51,7 @@ _Figure 3: Transactions Applied to Ledger Version_ The set of transactions included in a ledger instance are recorded in that ledger and allow audits of the XRP Ledger history. If an account balance is different in ledger N+1 than it was in ledger N, then ledger N+1 contains the transaction(s) responsible for the change. -Transactions that appear in a validated ledger may have succeeded in changing the ledger, or may have been processed without doing the requested action. Successful transactions have the **`tesSUCCESS`** [result code](../../references/protocol/transactions/transaction-results/transaction-results.md) which indicates the requested changes are applied to the ledger. Failed transactions in the ledger have **`tec`** class result codes.1 +Transactions that appear in a validated ledger may have succeeded in changing the ledger, or may have been processed without doing the requested action. Successful transactions have the **`tesSUCCESS`** [result code](../../references/protocol/transactions/transaction-results/index.md) which indicates the requested changes are applied to the ledger. Failed transactions in the ledger have **`tec`** class result codes.1 All transactions included in a ledger destroy some XRP as a [transaction cost](../transactions/transaction-cost.md), regardless of whether they had a **`tes`** or **`tec`** code. The exact amount of XRP to destroy is defined by the signed transaction instructions. diff --git a/docs/concepts/networks-and-servers/transaction-censorship-detection.md b/docs/concepts/networks-and-servers/transaction-censorship-detection.md index 84f4f861e3..a98ccf70eb 100644 --- a/docs/concepts/networks-and-servers/transaction-censorship-detection.md +++ b/docs/concepts/networks-and-servers/transaction-censorship-detection.md @@ -74,6 +74,6 @@ Here are some scenarios that could cause the detector to issue false positive me - [Reliable Transaction Submission](../transactions/reliable-transaction-submission.md) - [Understanding Log Messages](../../infrastructure/troubleshooting/understanding-log-messages.md) - **References:** - - [Transaction Results](../../references/protocol/transactions/transaction-results/transaction-results.md) + - [Transaction Results](../../references/protocol/transactions/transaction-results/index.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/payment-types/direct-xrp-payments.md b/docs/concepts/payment-types/direct-xrp-payments.md index 3a7cc47a0c..0d1c267a2e 100644 --- a/docs/concepts/payment-types/direct-xrp-payments.md +++ b/docs/concepts/payment-types/direct-xrp-payments.md @@ -43,7 +43,7 @@ The basis of any financial system is transferring value. The quickest and simple - [Monitor Incoming Payments with WebSocket](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md) - **References:** - [Payment transaction][] - - [Transaction Results](../../references/protocol/transactions/transaction-results/transaction-results.md) + - [Transaction Results](../../references/protocol/transactions/transaction-results/index.md) - [account_info method][] - for checking XRP balances {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/payment-types/partial-payments.md b/docs/concepts/payment-types/partial-payments.md index bc3db771ad..74ab323264 100644 --- a/docs/concepts/payment-types/partial-payments.md +++ b/docs/concepts/payment-types/partial-payments.md @@ -53,7 +53,7 @@ Partial Payments have the following limitations: - Direct XRP-to-XRP payments cannot be partial payments; this case returns the [result code][] `temBAD_SEND_XRP_PARTIAL`. - However, cross-currency payments that involve XRP as one of the currencies _can_ be partial payments. -[result code]: ../../references/protocol/transactions/transaction-results/transaction-results.md +[result code]: ../../references/protocol/transactions/transaction-results/index.md ### The `delivered_amount` Field diff --git a/docs/concepts/transactions/finality-of-results/index.md b/docs/concepts/transactions/finality-of-results/index.md index 1707ecf438..35a18e0bba 100644 --- a/docs/concepts/transactions/finality-of-results/index.md +++ b/docs/concepts/transactions/finality-of-results/index.md @@ -27,7 +27,7 @@ Any other transaction result is potentially not final. In that case, the transac ## How can non-final results change? -When you initially submit a transaction, the `rippled` server tentatively applies that transaction to its current open ledger, then returns the tentative [transaction results](../../../references/protocol/transactions/transaction-results/transaction-results.md) from doing so. However, the transaction's final result may be very different than its tentative results, for several reasons: +When you initially submit a transaction, the `rippled` server tentatively applies that transaction to its current open ledger, then returns the tentative [transaction results](../../../references/protocol/transactions/transaction-results/index.md) from doing so. However, the transaction's final result may be very different than its tentative results, for several reasons: - The transaction may be delayed until a later ledger version, or may never be included in a validated ledger. For the most part, the XRP Ledger follows a principle that all valid transactions should be processed as soon as possible. However, there are exceptions, including: @@ -55,6 +55,6 @@ When you initially submit a transaction, the `rippled` server tentatively applie ## See Also - [Look up Transaction Results](look-up-transaction-results.md) -- [Transaction Results Reference](../../../references/protocol/transactions/transaction-results/transaction-results.md) +- [Transaction Results Reference](../../../references/protocol/transactions/transaction-results/index.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} 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 737917eaad..b86d5295af 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 @@ -63,7 +63,7 @@ The following example shows a successful transaction, as returned by the [tx met } ``` -This example shows an [AccountSet transaction][] sent by the [account](../../accounts/index.md) with address `rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn`, using [Sequence number][] 376. The transaction's [identifying hash][] is `017DED8F5E20F0335C6F56E3D5EE7EF5F7E83FB81D2904072E665EEA69402567` and its [result](../../../references/protocol/transactions/transaction-results/transaction-results.md) is `tesSUCCESS`. The transaction was included in ledger version 46447423, which has been validated, so these results are final. +This example shows an [AccountSet transaction][] sent by the [account](../../accounts/index.md) with address `rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn`, using [Sequence number][] 376. The transaction's [identifying hash][] is `017DED8F5E20F0335C6F56E3D5EE7EF5F7E83FB81D2904072E665EEA69402567` and its [result](../../../references/protocol/transactions/transaction-results/index.md) is `tesSUCCESS`. The transaction was included in ledger version 46447423, which has been validated, so these results are final. ### Case: Not Included in a Validated Ledger @@ -75,7 +75,7 @@ If the transaction's failure is not final, it may still become included in a _fu ### Case: Included in a Validated Ledger -If the transaction _is_ included in a validated ledger, then the [transaction metadata](../../../references/protocol/transactions/metadata.md) contains a full report of all changes that were made to the ledger state as a result of processing the transaction. The metadata's `TransactionResult` field contains a [transaction result code](../../../references/protocol/transactions/transaction-results/transaction-results.md) that summarizes the outcome: +If the transaction _is_ included in a validated ledger, then the [transaction metadata](../../../references/protocol/transactions/metadata.md) contains a full report of all changes that were made to the ledger state as a result of processing the transaction. The metadata's `TransactionResult` field contains a [transaction result code](../../../references/protocol/transactions/transaction-results/index.md) that summarizes the outcome: - The code `tesSUCCESS` indicates that the transaction was, more or less, successful. - A `tec`-class code indicates that the transaction failed, and its only effects on the ledger state are to destroy the XRP [transaction cost](../transaction-cost.md) and possibly perform some bookkeeping like removing [expired Offers](../../tokens/decentralized-exchange/offers.md#offer-expiration) and [closed payment channels](../../payment-types/payment-channels.md#payment-channel-lifecycle). @@ -450,6 +450,6 @@ Most other transactions create a specific type of ledger entry and [adjust the s - **References:** - [Ledger Entry Types Reference](../../../references/protocol/ledger-data/ledger-entry-types/index.md) - All possible fields of all types of ledger entries - [Transaction Metadata](../../../references/protocol/transactions/metadata.md) - Summary of the metadata format and fields that appear in metadata - - [Transaction Results](../../../references/protocol/transactions/transaction-results/transaction-results.md) - Tables of all possible result codes for transactions. + - [Transaction Results](../../../references/protocol/transactions/transaction-results/index.md) - Tables of all possible result codes for transactions. {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/transactions/finality-of-results/transaction-malleability.md b/docs/concepts/transactions/finality-of-results/transaction-malleability.md index c4f5ba2549..e321d891c8 100644 --- a/docs/concepts/transactions/finality-of-results/transaction-malleability.md +++ b/docs/concepts/transactions/finality-of-results/transaction-malleability.md @@ -143,7 +143,7 @@ The process to exploit a vulnerable system follows a series of steps like the fo - **References:** - [Basic Data Types - Hashes](../../../references/protocol/data-types/basic-data-types.md#hashes) - [Transaction Common Fields - Global Flags](../../../references/protocol/transactions/common-fields.md#global-flags) - - [Transaction Results](../../../references/protocol/transactions/transaction-results/transaction-results.md) + - [Transaction Results](../../../references/protocol/transactions/transaction-results/index.md) - [Serialization Format](../../../references/protocol/binary-format.md) {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/concepts/transactions/index.md b/docs/concepts/transactions/index.md index d27cb8f34a..b960176b76 100644 --- a/docs/concepts/transactions/index.md +++ b/docs/concepts/transactions/index.md @@ -63,7 +63,7 @@ Sending a transaction to the XRP Ledger involves several steps: 3. Submit a transaction to an XRP Ledger server (usually a [`rippled` instance](../networks-and-servers/index.md)). If the transaction is properly formed, the server provisionally applies the transaction to its current version of the ledger and relays the transaction to other members of the peer-to-peer network. 4. The [consensus process](../consensus-protocol/index.md) determines which provisional transactions get included in the next validated ledger. 5. The servers apply those transactions to the previous ledger in a canonical order and share their results. -6. If enough [trusted validators](../networks-and-servers/rippled-server-modes.md#validators) created the exact same ledger, that ledger is declared _validated_ and the [results of the transactions](../../references/protocol/transactions/transaction-results/transaction-results.md) in that ledger are immutable. +6. If enough [trusted validators](../networks-and-servers/rippled-server-modes.md#validators) created the exact same ledger, that ledger is declared _validated_ and the [results of the transactions](../../references/protocol/transactions/transaction-results/index.md) in that ledger are immutable. See [Send XRP](../../tutorials/how-tos/send-xrp.md) for an interactive tutorial in sending XRP payments. diff --git a/docs/concepts/transactions/transaction-cost.md b/docs/concepts/transactions/transaction-cost.md index abeb13b3bb..ac1d457fc0 100644 --- a/docs/concepts/transactions/transaction-cost.md +++ b/docs/concepts/transactions/transaction-cost.md @@ -131,7 +131,7 @@ The `Fee` field is one of the things that can be [auto-filled](../../references/ ## Transaction Costs and Failed Transactions -Since the purpose of the transaction cost is to protect the XRP Ledger peer-to-peer network from excessive load, it should apply to any transaction that gets distributed to the network, regardless of whether or not that transaction succeeds. However, to affect the shared global ledger, a transaction must be included in a validated ledger. Thus, `rippled` servers try to include failed transactions in ledgers, with [`tec` status codes](../../references/protocol/transactions/transaction-results/transaction-results.md) ("tec" stands for "Transaction Engine - Claimed fee only"). +Since the purpose of the transaction cost is to protect the XRP Ledger peer-to-peer network from excessive load, it should apply to any transaction that gets distributed to the network, regardless of whether or not that transaction succeeds. However, to affect the shared global ledger, a transaction must be included in a validated ledger. Thus, `rippled` servers try to include failed transactions in ledgers, with [`tec` status codes](../../references/protocol/transactions/transaction-results/index.md) ("tec" stands for "Transaction Engine - Claimed fee only"). The transaction cost is only debited from the sender's XRP balance when the transaction actually becomes included in a validated ledger. This is true whether the transaction is considered successful or fails with a `tec` code. diff --git a/docs/concepts/transactions/transaction-queue.md b/docs/concepts/transactions/transaction-queue.md index b403c1b8a1..2bbd3a56bc 100644 --- a/docs/concepts/transactions/transaction-queue.md +++ b/docs/concepts/transactions/transaction-queue.md @@ -64,7 +64,7 @@ Within the transaction queue, transactions are ranked so that transactions payin The precise order of transactions in the queue decides which transactions get added to the next in-progress ledger version in cases where there are more transactions in the queue than the expected size of the next ledger version. The order of the transactions **does not affect the order the transactions are executed within a validated ledger**. In each validated ledger version, the transaction set for that version executes in [canonical order](../consensus-protocol/consensus-structure.md#calculate-and-share-validations). -**Note:** When `rippled` queues a transaction, the provisional [transaction response code](../../references/protocol/transactions/transaction-results/transaction-results.md) is `terQUEUED`. This means that the transaction is likely to succeed in a future ledger version. As with all provisional response codes, the outcome of the transaction is not final until the transaction is either included in a validated ledger, or [rendered permanently invalid](finality-of-results/index.md). +**Note:** When `rippled` queues a transaction, the provisional [transaction response code](../../references/protocol/transactions/transaction-results/index.md) is `terQUEUED`. This means that the transaction is likely to succeed in a future ledger version. As with all provisional response codes, the outcome of the transaction is not final until the transaction is either included in a validated ledger, or [rendered permanently invalid](finality-of-results/index.md). ## See Also 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 47df59075c..4984c19d30 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 @@ -86,7 +86,7 @@ The `streams` parameter provides access to the following default streams of info - `peer_status` - **(Admin only)** Information about connected peer `rippled` servers, especially with regards to the consensus process. - `transactions` - Sends a message whenever a transaction is included in a closed ledger. - `transactions_proposed` - Sends a message whenever a transaction is included in a closed ledger, as well as some transactions that have not yet been included in a validated ledger and may never be. Not all proposed transactions appear before validation. - **Note:** [Even some transactions that don't succeed are included](../../../protocol/transactions/transaction-results/transaction-results.md) in validated ledgers, because they take the anti-spam transaction fee. + **Note:** [Even some transactions that don't succeed are included](../../../protocol/transactions/transaction-results/index.md) in validated ledgers, because they take the anti-spam transaction fee. - `server` - Sends a message whenever the status of the `rippled` server (for example, network connectivity) changes. - `validations` - Sends a message whenever the server receives a validation message, regardless of if the server trusts the validator. (An individual `rippled` declares a ledger validated when the server receives validation messages from at least a quorum of trusted validators.) @@ -361,8 +361,8 @@ Transaction stream messages have the following fields: | `Field` | Type | Description | |:------------------------|:--------------------------|:-----------------------| | `type` | String | `transaction` indicates this is the notification of a transaction, which could come from several possible streams. | -| `engine_result` | String | String [Transaction result code](../../../protocol/transactions/transaction-results/transaction-results.md) | -| `engine_result_code` | Number | Numeric [transaction response code](../../../protocol/transactions/transaction-results/transaction-results.md), if applicable. | +| `engine_result` | String | String [Transaction result code](../../../protocol/transactions/transaction-results/index.md) | +| `engine_result_code` | Number | Numeric [transaction response code](../../../protocol/transactions/transaction-results/index.md), if applicable. | | `engine_result_message` | String | Human-readable explanation for the transaction response | | `ledger_current_index` | Number - [Ledger Index][] | _(Unvalidated transactions only)_ The ledger index of the current in-progress [ledger version](../../../../concepts/ledgers/index.md) for which this transaction is currently proposed. | | `ledger_hash` | String - [Hash][] | _(Validated transactions only)_ The identifying hash of the ledger version that includes this transaction | diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md index f7bb82363d..c36c1ad680 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md @@ -293,8 +293,8 @@ The response follows the [standard format][], with a successful result containin | `Field` | Type | Description | |:------------------------|:--------|:-----------------------------------------| -| `engine_result` | String | Text [result code](../../../protocol/transactions/transaction-results/transaction-results.md) indicating the preliminary result of the transaction, for example `tesSUCCESS` | -| `engine_result_code` | Integer | Numeric version of the [result code](../../../protocol/transactions/transaction-results/transaction-results.md). **Not recommended.** | +| `engine_result` | String | Text [result code](../../../protocol/transactions/transaction-results/index.md) indicating the preliminary result of the transaction, for example `tesSUCCESS` | +| `engine_result_code` | Integer | Numeric version of the [result code](../../../protocol/transactions/transaction-results/index.md). **Not recommended.** | | `engine_result_message` | String | Human-readable explanation of the transaction's preliminary result | | `tx_blob` | String | The complete transaction in hex string format | | `tx_json` | Object | The complete transaction in JSON format | @@ -308,7 +308,7 @@ The response follows the [standard format][], with a successful result containin | `open_ledger_cost` | String | _(Omitted in sign-and-submit mode)_ The current [open ledger cost](../../../../concepts/transactions/transaction-cost.md#open-ledger-cost) before processing this transaction. Transactions with a lower cost are likely to be [queued](../../../../concepts/transactions/transaction-queue.md). | | `validated_ledger_index` | Integer | _(Omitted in sign-and-submit mode)_ The [ledger index][] of the newest validated ledger at the time of submission. This provides a lower bound on the ledger versions that the transaction can appear in as a result of this request. (The transaction could only have been validated in this ledger version or earlier if it had already been submitted before.) | -**Warning:** Even if the WebSocket response has `"status":"success"`, indicating that the command was successfully received, that does _not_ indicate that the transaction executed successfully. Many situations can prevent a transaction from processing successfully, such as a lack of trust lines connecting the two accounts in a payment, or changes in the state of the ledger since the time the transaction was constructed. Even if nothing is wrong, it may take several seconds to close and validate the ledger version that includes the transaction. See the [full list of transaction responses](../../../protocol/transactions/transaction-results/transaction-results.md) for details, and do not consider the transaction's results final until they appear in a validated ledger version. +**Warning:** Even if the WebSocket response has `"status":"success"`, indicating that the command was successfully received, that does _not_ indicate that the transaction executed successfully. Many situations can prevent a transaction from processing successfully, such as a lack of trust lines connecting the two accounts in a payment, or changes in the state of the ledger since the time the transaction was constructed. Even if nothing is wrong, it may take several seconds to close and validate the ledger version that includes the transaction. See the [full list of transaction responses](../../../protocol/transactions/transaction-results/index.md) for details, and do not consider the transaction's results final until they appear in a validated ledger version. **Caution:** If this command results in an error message, the message can contain the secret key from the request. (This can only happen in sign-and-submit mode.) Make sure that these errors are not visible to others. diff --git a/docs/references/protocol/binary-format.md b/docs/references/protocol/binary-format.md index 7307478d2d..08fe1e59c9 100644 --- a/docs/references/protocol/binary-format.md +++ b/docs/references/protocol/binary-format.md @@ -82,7 +82,7 @@ The following table defines the top-level fields from the definitions file: | `TYPES` | Map of data types to their ["type code"](#type-codes) for constructing field IDs and sorting fields in canonical order. Codes below 1 should not appear in actual data; codes above 10000 represent special "high-level" object types such as "Transaction" that cannot be serialized inside other objects. See the [Type List](#type-list) for details of how to serialize each type. | | `LEDGER_ENTRY_TYPES` | Map of [ledger objects](ledger-data/ledger-entry-types/index.md) to their data type. These appear in ledger state data, and in the "affected nodes" section of processed transactions' [metadata](transactions/metadata.md). | | `FIELDS` | A sorted array of tuples representing all fields that may appear in transactions, ledger objects, or other data. The first member of each tuple is the string name of the field and the second member is an object with that field's properties. (See the "Field properties" table below for definitions of those fields.) | -| `TRANSACTION_RESULTS` | Map of [transaction result codes](transactions/transaction-results/transaction-results.md) to their numeric values. Result types not included in ledgers have negative values; `tesSUCCESS` has numeric value 0; [`tec`-class codes](transactions/transaction-results/tec-codes.md) represent failures that are included in ledgers. | +| `TRANSACTION_RESULTS` | Map of [transaction result codes](transactions/transaction-results/index.md) to their numeric values. Result types not included in ledgers have negative values; `tesSUCCESS` has numeric value 0; [`tec`-class codes](transactions/transaction-results/tec-codes.md) represent failures that are included in ledgers. | | `TRANSACTION_TYPES` | Map of all [transaction types](transactions/types/index.md) to their numeric values. | For purposes of serializing transactions for signing and submitting, the `FIELDS`, `TYPES`, and `TRANSACTION_TYPES` fields are necessary. diff --git a/docs/references/protocol/transactions/transaction-results/transaction-results.md b/docs/references/protocol/transactions/transaction-results/index.md similarity index 100% rename from docs/references/protocol/transactions/transaction-results/transaction-results.md rename to docs/references/protocol/transactions/transaction-results/index.md diff --git a/docs/references/protocol/transactions/types/accountdelete.md b/docs/references/protocol/transactions/types/accountdelete.md index c84bf779e1..d5d16f4c50 100644 --- a/docs/references/protocol/transactions/types/accountdelete.md +++ b/docs/references/protocol/transactions/types/accountdelete.md @@ -47,7 +47,7 @@ The transaction cost always applies when a transaction is included in a validate ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:-----------|:------------| diff --git a/docs/references/protocol/transactions/types/ammbid.md b/docs/references/protocol/transactions/types/ammbid.md index 760c43db64..b827e85415 100644 --- a/docs/references/protocol/transactions/types/ammbid.md +++ b/docs/references/protocol/transactions/types/ammbid.md @@ -126,7 +126,7 @@ As a special case, during the final (20th) interval of the auction slot, the ref ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:------------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ammcreate.md b/docs/references/protocol/transactions/types/ammcreate.md index c513af9b18..2d27bf99c5 100644 --- a/docs/references/protocol/transactions/types/ammcreate.md +++ b/docs/references/protocol/transactions/types/ammcreate.md @@ -53,7 +53,7 @@ Since each AMM instance involves an AccountRoot ledger entry, an AMM ledger entr ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ammdelete.md b/docs/references/protocol/transactions/types/ammdelete.md index 63191346a8..ded54c50a3 100644 --- a/docs/references/protocol/transactions/types/ammdelete.md +++ b/docs/references/protocol/transactions/types/ammdelete.md @@ -46,7 +46,7 @@ Normally, an [AMMWithdraw transaction][] automatically deletes an AMM and all as ## Error Cases -Besides errors that can occur for all transactions, AMMCreate transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, AMMCreate transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ammdeposit.md b/docs/references/protocol/transactions/types/ammdeposit.md index 5fbc061b2f..45bc0f4483 100644 --- a/docs/references/protocol/transactions/types/ammdeposit.md +++ b/docs/references/protocol/transactions/types/ammdeposit.md @@ -122,7 +122,7 @@ You must specify **exactly one** of these flags, plus any [global flags](../comm ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:------------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ammvote.md b/docs/references/protocol/transactions/types/ammvote.md index 028c9e2428..4d530845b4 100644 --- a/docs/references/protocol/transactions/types/ammvote.md +++ b/docs/references/protocol/transactions/types/ammvote.md @@ -44,7 +44,7 @@ Vote on the trading fee for an [Automated Market Maker](../../../../concepts/tok ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:------------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ammwithdraw.md b/docs/references/protocol/transactions/types/ammwithdraw.md index 9d9353bb27..e6a7031672 100644 --- a/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/docs/references/protocol/transactions/types/ammwithdraw.md @@ -107,7 +107,7 @@ You must specify **exactly one** of these flags, plus any [global flags](../comm ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:------------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/clawback.md b/docs/references/protocol/transactions/types/clawback.md index 853b36249f..f2130788f7 100644 --- a/docs/references/protocol/transactions/types/clawback.md +++ b/docs/references/protocol/transactions/types/clawback.md @@ -41,7 +41,7 @@ Clawback is disabled by default. To use clawback, you must send an [AccountSet t ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:-----------|:------------| diff --git a/docs/references/protocol/transactions/types/diddelete.md b/docs/references/protocol/transactions/types/diddelete.md index fdf9a14d72..2e7457bac5 100644 --- a/docs/references/protocol/transactions/types/diddelete.md +++ b/docs/references/protocol/transactions/types/diddelete.md @@ -34,7 +34,7 @@ Delete the [DID ledger entry](../../ledger-data/ledger-entry-types/did.md) assoc ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/didset.md b/docs/references/protocol/transactions/types/didset.md index 5b41541a60..52093998ae 100644 --- a/docs/references/protocol/transactions/types/didset.md +++ b/docs/references/protocol/transactions/types/didset.md @@ -45,7 +45,7 @@ You must include either `Data`, `DIDDocument`, or `URI` when you submit the `DID ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/docs/references/protocol/transactions/types/nftokenacceptoffer.md index 36cb175f3a..4881928dfd 100644 --- a/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -90,7 +90,7 @@ In brokered mode, the offers referenced by `NFTokenBuyOffer` and `NFTokenSellOff ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:-----------------------------------|:----------------------------------------| diff --git a/docs/references/protocol/transactions/types/nftokenburn.md b/docs/references/protocol/transactions/types/nftokenburn.md index a6a015a990..6b9660bf14 100644 --- a/docs/references/protocol/transactions/types/nftokenburn.md +++ b/docs/references/protocol/transactions/types/nftokenburn.md @@ -42,7 +42,7 @@ _(Added by the [NonFungibleTokensV1_1 amendment][].)_ ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:-------------------|:--------------------------------------------------------| diff --git a/docs/references/protocol/transactions/types/nftokencanceloffer.md b/docs/references/protocol/transactions/types/nftokencanceloffer.md index 16e976fec9..bdb4b6ba81 100644 --- a/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -51,7 +51,7 @@ The transaction fails with an error if one of the IDs points to an object that d ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:-------------------|:--------------------------------------------------------| diff --git a/docs/references/protocol/transactions/types/nftokencreateoffer.md b/docs/references/protocol/transactions/types/nftokencreateoffer.md index 85a4c0197b..d082883ef1 100644 --- a/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -51,7 +51,7 @@ Transactions of the NFTokenCreateOffer type support additional values in the [`F ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:---------------------------------|:------------------------------------------| diff --git a/docs/references/protocol/transactions/types/nftokenmint.md b/docs/references/protocol/transactions/types/nftokenmint.md index 347c800989..061aa67d04 100644 --- a/docs/references/protocol/transactions/types/nftokenmint.md +++ b/docs/references/protocol/transactions/types/nftokenmint.md @@ -103,7 +103,7 @@ This transaction assumes that the issuer, `rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2`, ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:------------------------------|:---------------------------------------------| diff --git a/docs/references/protocol/transactions/types/offercreate.md b/docs/references/protocol/transactions/types/offercreate.md index 6574f893dc..c5dbd86e69 100644 --- a/docs/references/protocol/transactions/types/offercreate.md +++ b/docs/references/protocol/transactions/types/offercreate.md @@ -51,7 +51,7 @@ Transactions of the OfferCreate type support additional values in the [`Flags` f | Flag Name | Hex Value | Decimal Value | Description | |:----------------------|:-------------|:--------------|:----------------------| | `tfPassive` | `0x00010000` | 65536 | If enabled, the Offer does not consume Offers that exactly match it, and instead becomes an Offer object in the ledger. It still consumes Offers that cross it. | -| `tfImmediateOrCancel` | `0x00020000` | 131072 | Treat the Offer as an [Immediate or Cancel order](http://en.wikipedia.org/wiki/Immediate_or_cancel). The Offer never creates an [Offer object][] in the ledger: it only trades as much as it can by consuming existing Offers at the time the transaction is processed. If no Offers match, it executes "successfully" without trading anything. In this case, the transaction still uses the [result code](../transaction-results/transaction-results.md) `tesSUCCESS`. | +| `tfImmediateOrCancel` | `0x00020000` | 131072 | Treat the Offer as an [Immediate or Cancel order](http://en.wikipedia.org/wiki/Immediate_or_cancel). The Offer never creates an [Offer object][] in the ledger: it only trades as much as it can by consuming existing Offers at the time the transaction is processed. If no Offers match, it executes "successfully" without trading anything. In this case, the transaction still uses the [result code](../transaction-results/index.md) `tesSUCCESS`. | | `tfFillOrKill` | `0x00040000` | 262144 | Treat the offer as a [Fill or Kill order](http://en.wikipedia.org/wiki/Fill_or_kill). The Offer never creates an [Offer object][] in the ledger, and is canceled 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. | diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index dcb000aa55..48612e198b 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -128,7 +128,7 @@ The XRP Ledger defines the "quality" of a currency exchange as the ratio of the The [`tfLimitQuality` flag](#payment-flags) allows you to set a minimum quality of conversions that you are willing to take. This limit quality is defined as the destination `Amount` divided by the `SendMax` amount (the numeric amounts only, regardless of currency). When set, the payment processing engine avoids using any paths whose quality (conversion rate) is worse (numerically lower) than the limit quality. -By itself, the `tfLimitQuality` flag reduces the number of situations in which a transaction can succeed. Specifically, it rejects payments where some part of the payment uses an unfavorable conversion, even if the overall *average* quality of conversions in the payment is equal or better than the limit quality. If a payment is rejected in this way, the [transaction result](../transaction-results/transaction-results.md) is `tecPATH_DRY`. +By itself, the `tfLimitQuality` flag reduces the number of situations in which a transaction can succeed. Specifically, it rejects payments where some part of the payment uses an unfavorable conversion, even if the overall *average* quality of conversions in the payment is equal or better than the limit quality. If a payment is rejected in this way, the [transaction result](../transaction-results/index.md) is `tecPATH_DRY`. Consider the following example. If I am trying to send you 100 Chinese Yuan (`Amount` = 100 CNY) for 20 United States dollars (`SendMax` = 20 USD) or less, then the limit quality is `5`. Imagine one trader is offering ¥95 for $15 (a ratio of about `6.3` CNY per USD), but the next best offer in the market is ¥5 for $2 (a ratio of `2.5` CNY per USD). If I were to take both offers to send you 100 CNY, then it would cost me 17 USD, for an average quality of about `5.9`. diff --git a/docs/references/protocol/transactions/types/paymentchannelfund.md b/docs/references/protocol/transactions/types/paymentchannelfund.md index e909e4a58d..0e8b779ff9 100644 --- a/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -38,7 +38,7 @@ Example PaymentChannelFund: ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------------|:-------------------------------------------------| diff --git a/docs/references/protocol/transactions/types/ticketcreate.md b/docs/references/protocol/transactions/types/ticketcreate.md index 32537ce3d0..f4752640ff 100644 --- a/docs/references/protocol/transactions/types/ticketcreate.md +++ b/docs/references/protocol/transactions/types/ticketcreate.md @@ -41,7 +41,7 @@ If the transaction cannot create _all_ of the requested Tickets (either due to t ## Error Cases -Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/transaction-results.md): +Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md): | Error Code | Description | |:--------------------------|:-------------------------------------------------| diff --git a/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md b/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md index 9a25a9955c..2733b329c6 100644 --- a/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md +++ b/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md @@ -678,12 +678,12 @@ An example of a successful response: {% /tabs %} -If the transaction fails with the following [result codes](../../../references/protocol/transactions/transaction-results/transaction-results.md), here are some things to check: +If the transaction fails with the following [result codes](../../../references/protocol/transactions/transaction-results/index.md), here are some things to check: - **`tefBAD_AUTH`**: The regular key you signed your test transaction with doesn't match the regular key you set in the previous step. Check that the secret and address for your regular key pair match and double-check which values you used in each step. - **`tefBAD_AUTH_MASTER`** or **`temBAD_AUTH_MASTER`**: Your account doesn't have a regular key assigned. Check that the SetRegularKey transaction executed successfully. You can also use the [account_info method][] to confirm that your regular key is set in the `RegularKey` field as expected. -For possible causes of other result codes, see [Transaction Results](../../../references/protocol/transactions/transaction-results/transaction-results.md). +For possible causes of other result codes, see [Transaction Results](../../../references/protocol/transactions/transaction-results/index.md). ## See Also diff --git a/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md b/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md index 373bf6e18a..9129c7d958 100644 --- a/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md +++ b/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair.md @@ -497,6 +497,6 @@ This operation has only two possible outcomes: - A nonzero result, equal to the `lsfDisableMaster` value, indicates **the master key has been successfully disabled**. - A zero result indicates the account's master key is not disabled. -If the result does not match your expectations, check whether the transaction you sent in the previous steps has executed successfully. It should be the most recent entry in the account's transaction history ([account_tx method][]) and it should have the result code `tesSUCCESS`. If you see any other [result code](../../../references/protocol/transactions/transaction-results/transaction-results.md), the transaction was not executed successfully. Depending on the cause of the error, you may want to restart these steps from the beginning. +If the result does not match your expectations, check whether the transaction you sent in the previous steps has executed successfully. It should be the most recent entry in the account's transaction history ([account_tx method][]) and it should have the result code `tesSUCCESS`. If you see any other [result code](../../../references/protocol/transactions/transaction-results/index.md), the transaction was not executed successfully. Depending on the cause of the error, you may want to restart these steps from the beginning. {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md b/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md index 365c714491..0a8649f432 100644 --- a/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md +++ b/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing.md @@ -140,7 +140,7 @@ Connecting to 127.0.0.1:5005 } ``` -Make sure that the [Transaction Result](../../../references/protocol/transactions/transaction-results/transaction-results.md) is [**`tesSUCCESS`**](../../../references/protocol/transactions/transaction-results/tes-success.md). Otherwise, the transaction failed. If you have a problem in stand-alone mode or a non-production network, check that [multi-sign is enabled](../../../infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md#settings-in-new-genesis-ledgers). +Make sure that the [Transaction Result](../../../references/protocol/transactions/transaction-results/index.md) is [**`tesSUCCESS`**](../../../references/protocol/transactions/transaction-results/tes-success.md). Otherwise, the transaction failed. If you have a problem in stand-alone mode or a non-production network, check that [multi-sign is enabled](../../../infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md#settings-in-new-genesis-ledgers). **Note:** Without the [MultiSignReserve amendment][], the more members in the signer list, the more XRP your address must have for purposes of the [owner reserve](../../../concepts/accounts/reserves.md#owner-reserves). If your address does not have enough XRP, the transaction fails with [`tecINSUFFICIENT_RESERVE`](../../../references/protocol/transactions/transaction-results/tec-codes.md). With the [MultiSignReserve amendment][] enabled, the XRP your address must have for purposes of the [owner reserve](../../../concepts/accounts/reserves.md#owner-reserves) is 5 XRP, regardless of the number of members in the signer list. See also: [Signer Lists and Reserves](../../../references/protocol/ledger-data/ledger-entry-types/signerlist.md#signer-lists-and-reserves). diff --git a/docs/tutorials/how-tos/send-xrp.md b/docs/tutorials/how-tos/send-xrp.md index 652dc7141e..e405f1de25 100644 --- a/docs/tutorials/how-tos/send-xrp.md +++ b/docs/tutorials/how-tos/send-xrp.md @@ -247,7 +247,7 @@ If you see any other result, you should check the following: - Do you have enough Test XRP to send the transaction? The amount of XRP you can send is limited by the [reserve requirement](../../concepts/accounts/reserves.md), which is currently 10 XRP with an additional 2 XRP for each "object" you own in the ledger. (If you generated a new address with the Testnet Faucet, you don't own any objects.) - Are you connected to a server on the test network? -See the full list of [transaction results](../../references/protocol/transactions/transaction-results/transaction-results.md) for more possibilities. +See the full list of [transaction results](../../references/protocol/transactions/transaction-results/index.md) for more possibilities. {% interactive-block label="Submit" steps=$frontmatter.steps %} diff --git a/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md b/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md index d86f7050c9..bc479ae7c9 100644 --- a/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md +++ b/docs/tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md @@ -135,7 +135,7 @@ Use the [tx method][] with the CheckCash transaction's identifying hash to check ### Handling Errors -If cashing the Check failed with a `tec`-class code, look up the code in the [Full Transaction Response List](../../../../references/protocol/transactions/transaction-results/transaction-results.md) and respond accordingly. Some common possibilities for CheckCash transactions: +If cashing the Check failed with a `tec`-class code, look up the code in the [Full Transaction Response List](../../../../references/protocol/transactions/transaction-results/index.md) and respond accordingly. Some common possibilities for CheckCash transactions: | Result Code | Meaning | How to Respond | |-------------|---------|----------------| diff --git a/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md b/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md index 6919f9ca44..939410203f 100644 --- a/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md +++ b/docs/tutorials/how-tos/use-specialized-payment-types/use-escrows/send-a-conditionally-held-escrow.md @@ -148,7 +148,7 @@ Response: [Sign and submit](../../../../concepts/transactions/index.md#signing-and-submitting-transactions) an [EscrowFinish transaction][] to execute the release of the funds after the `FinishAfter` time has passed. Set the `Owner` field of the transaction to the `Account` address from the EscrowCreate transaction, and the `OfferSequence` to the `Sequence` number from the EscrowCreate transaction. Set the `Condition` and `Fulfillment` fields to the condition and fulfillment values, in hexadecimal, that you generated in step 1. Set the `Fee` ([transaction cost](../../../../concepts/transactions/transaction-cost.md)) value based on the size of the fulfillment in bytes: a conditional EscrowFinish requires at least 330 drops of XRP plus 10 drops per 16 bytes in the size of the fulfillment. -**Note:** If you included a `FinishAfter` field in the EscrowCreate transaction, you cannot execute it before that time has passed, even if you provide the correct fulfillment for the Escrow's condition. The EscrowFinish transaction fails with the [result code](../../../../references/protocol/transactions/transaction-results/transaction-results.md) `tecNO_PERMISSION` if the previously-closed ledger's close time is before the `FinishAfter` time. +**Note:** If you included a `FinishAfter` field in the EscrowCreate transaction, you cannot execute it before that time has passed, even if you provide the correct fulfillment for the Escrow's condition. The EscrowFinish transaction fails with the [result code](../../../../references/protocol/transactions/transaction-results/index.md) `tecNO_PERMISSION` if the previously-closed ledger's close time is before the `FinishAfter` time. If the escrow has expired, you can only [cancel the escrow](cancel-an-expired-escrow.md) instead. diff --git a/docs/tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md b/docs/tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md index da23fa39e0..b8fbcc5208 100644 --- a/docs/tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md +++ b/docs/tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md @@ -344,7 +344,7 @@ WS_HANDLERS["transaction"] = log_tx When you subscribe to an account, you get messages for _all transactions to or from the account_, as well as _transactions that affect the account indirectly_, such as trading its [tokens](../../../concepts/tokens/index.md). If your goal is to recognize when the account has received incoming payments, you must filter the transactions stream and process the payments based on the amount they actually delivered. Look for the following information: - The **`validated` field** indicates that the transaction's outcome is [final](../../../concepts/transactions/finality-of-results/index.md). This should always be the case when you subscribe to `accounts`, but if you _also_ subscribe to `accounts_proposed` or the `transactions_proposed` stream then the server sends similar messages on the same connection for unconfirmed transactions. As a precaution, it's best to always check the `validated` field. -- The **`meta.TransactionResult` field** is the [transaction result](../../../references/protocol/transactions/transaction-results/transaction-results.md). If the result is not `tesSUCCESS`, the transaction failed and cannot have delivered any value. +- The **`meta.TransactionResult` field** is the [transaction result](../../../references/protocol/transactions/transaction-results/index.md). If the result is not `tesSUCCESS`, the transaction failed and cannot have delivered any value. - The **`transaction.Account`** field is the sender of the transaction. If you are only looking for transactions sent by others, you can ignore any transactions where this field matches your account's address. (Keep in mind, it _is_ possible to make a cross-currency payment to yourself.) - The **`transaction.TransactionType` field** is the type of transaction. The transaction types that can possibly deliver currency to an account are as follows: - **[Payment transactions][]** can deliver XRP or [tokens](../../../concepts/tokens/index.md). Filter these by the `transaction.Destination` field, which contains the address of the recipient, and always use the `meta.delivered_amount` to see how much the payment actually delivered. XRP amounts are [formatted as strings](../../../references/protocol/data-types/basic-data-types.md#specifying-currency-amounts). @@ -511,6 +511,6 @@ Many programming languages have libraries for sending and receiving data over a - **References:** - [Transaction Types](../../../references/protocol/transactions/types/index.md) - [Transaction Metadata](../../../references/protocol/transactions/metadata.md) - Summary of the metadata format and fields that appear in metadata - - [Transaction Results](../../../references/protocol/transactions/transaction-results/transaction-results.md) - Tables of all possible result codes for transactions. + - [Transaction Results](../../../references/protocol/transactions/transaction-results/index.md) - Tables of all possible result codes for transactions. {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/package-lock.json b/package-lock.json index f937410211..67fcf22c79 100644 --- a/package-lock.json +++ b/package-lock.json @@ -12,7 +12,7 @@ "@codemirror/state": "6.3.3", "@codemirror/view": "^6.22.2", "@lezer/highlight": "^1.2.0", - "@redocly/realm": "^0.78.4", + "@redocly/realm": "^0.78.6", "@uiw/codemirror-themes": "4.21.21", "@uiw/react-codemirror": "^4.21.21", "@xrplf/isomorphic": "^1.0.0-beta.1", @@ -497,9 +497,9 @@ } }, "node_modules/@babel/runtime-corejs3": { - "version": "7.24.0", - "resolved": "https://registry.npmjs.org/@babel/runtime-corejs3/-/runtime-corejs3-7.24.0.tgz", - "integrity": "sha512-HxiRMOncx3ly6f3fcZ1GVKf+/EROcI9qwPgmij8Czqy6Okm/0T37T4y2ZIlLUuEUFjtM7NRsfdCO8Y3tAiJZew==", + "version": "7.24.1", + "resolved": "https://registry.npmjs.org/@babel/runtime-corejs3/-/runtime-corejs3-7.24.1.tgz", + "integrity": "sha512-T9ko/35G+Bkl+win48GduaPlhSlOjjE5s1TeiEcD+QpxlLQnoEfb/nO/T+TQqkm+ipFwORn+rB8w14iJ/uD0bg==", "dependencies": { "core-js-pure": "^3.30.2", "regenerator-runtime": "^0.14.0" @@ -1769,9 +1769,9 @@ } }, "node_modules/@redocly/config": { - "version": "0.1.2", - "resolved": "https://registry.npmjs.org/@redocly/config/-/config-0.1.2.tgz", - "integrity": "sha512-5U2GXa7SQ9IrbynOryc/GrW05a+WheeN2JcIUNcbYc9UCIbkNNIUqcibvN0KDI4fH2rEJUSEGWdBSdGK9IPxfw==" + "version": "0.1.4", + "resolved": "https://registry.npmjs.org/@redocly/config/-/config-0.1.4.tgz", + "integrity": "sha512-OEdCW1HRpFiZaZNrXQq8LoBxX3APijZaa/Xyoc6r44LnyAPWkjQqvPoBxE7IRqSvMihf8bl+ZRc1gtc1KuFLHw==" }, "node_modules/@redocly/graphql-docs": { "version": "0.6.39", @@ -1834,11 +1834,12 @@ } }, "node_modules/@redocly/openapi-core": { - "version": "1.10.3", - "resolved": "https://registry.npmjs.org/@redocly/openapi-core/-/openapi-core-1.10.3.tgz", - "integrity": "sha512-4SnIWh8r3EM1ylcoHIJSnQnuvqRTpQMnf2RU3BfVdcCBa0A1uEyH6XSxgcO5ehxfQGuGGpUXJ+vPh32PUaQDkA==", + "version": "1.10.4", + "resolved": "https://registry.npmjs.org/@redocly/openapi-core/-/openapi-core-1.10.4.tgz", + "integrity": "sha512-GzvAuoVtHk75q/HqaRNqRUTZWYKpZ16HCOWIrx2txAvZrMoWCUNRVsELY91W/ilH/Cepj6t/Nh+bpJ7o/mcN/g==", "dependencies": { "@redocly/ajv": "^8.11.0", + "@redocly/config": "^0.1.1", "colorette": "^1.2.0", "js-levenshtein": "^1.1.6", "js-yaml": "^4.1.0", @@ -1889,16 +1890,16 @@ } }, "node_modules/@redocly/openapi-docs": { - "version": "3.0.0-alpha.87", - "resolved": "https://registry.npmjs.org/@redocly/openapi-docs/-/openapi-docs-3.0.0-alpha.87.tgz", - "integrity": "sha512-TnM0kCZ4SIe378xfTTnzWMSOCtO0qn+W5LYBj2tiJNOtWFIgEUliwJPrFyqk2upratXPeXJxFVi4QszI4ShAIg==", + "version": "3.0.0-alpha.88", + "resolved": "https://registry.npmjs.org/@redocly/openapi-docs/-/openapi-docs-3.0.0-alpha.88.tgz", + "integrity": "sha512-hi5kZmvgB5WXvQJxc0dlBp8xDLzTIGeY7yuTqvRa2/rQ8MLILDo/1A5+0532jQM9NCr0H3Z3XuYovSwe0/VHfg==", "dependencies": { "@codemirror/lang-json": "^6.0.1", "@codemirror/lint": "^6.4.2", "@codemirror/state": "^6.4.1", "@lezer/highlight": "^1.1.6", "@markdoc/markdoc": "0.4.0", - "@redocly/openapi-core": "1.10.3", + "@redocly/openapi-core": "1.10.4", "@redocly/vscode-json-languageservice": "3.4.9", "@uiw/codemirror-theme-material": "^4.21.20", "@uiw/react-codemirror": "^4.21.24", @@ -1949,31 +1950,31 @@ "integrity": "sha512-QkEyUiLhsJoZkbumGZlswmAhA7CBU02Wrz7zvH4SrcifbsqwlXShVXg65f3v/ts57W3dqyamEriMhij1Z3Zz4A==" }, "node_modules/@redocly/portal-plugin-mock-server": { - "version": "0.1.7", - "resolved": "https://registry.npmjs.org/@redocly/portal-plugin-mock-server/-/portal-plugin-mock-server-0.1.7.tgz", - "integrity": "sha512-9KUQAlgSpbZKBb9J6uJIQ5GUFdNUD2navX9n018G0Ch4KZ3YwOzmDC5kcRv7E9InPCNCawR1Au48djTz1xp4TA==", + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/@redocly/portal-plugin-mock-server/-/portal-plugin-mock-server-0.1.9.tgz", + "integrity": "sha512-0zzZTKAJKZEVGfRL1a1uF32M/Kgz8ci3fZ9OM9zckReFrC7Wr8ioW7nwXCHyuRyE492YRYUYpKsJ9KVy6S3Nvg==", "dependencies": { - "@redocly/config": "0.1.2", + "@redocly/config": "0.1.4", "@redocly/mock-server": "0.0.8", - "@redocly/openapi-core": "1.10.3", - "@redocly/openapi-docs": "3.0.0-alpha.87" + "@redocly/openapi-core": "1.10.4", + "@redocly/openapi-docs": "3.0.0-alpha.88" } }, "node_modules/@redocly/realm": { - "version": "0.78.4", - "resolved": "https://registry.npmjs.org/@redocly/realm/-/realm-0.78.4.tgz", - "integrity": "sha512-AjtFVcwKzMRIbIKzoIEzAUoCMWMyPDAfZCmv+xbqNYljxey1q9iYQ1MzdjIKAK44Udu84swi81PmGzFaaDm/cQ==", + "version": "0.78.6", + "resolved": "https://registry.npmjs.org/@redocly/realm/-/realm-0.78.6.tgz", + "integrity": "sha512-Jq+Th1LSnKsRwO7ZJdsidpwDgWi/FZfMs1tbrbR2ntUUCdGr33+B46P6EvARCy2J8ME9C2bmDvrD0L+RveHT3w==", "dependencies": { "@babel/core": "^7.23.3", "@cocalc/ansi-to-react": "7.0.0", "@markdoc/markdoc": "0.4.0", "@redocly/ajv": "^8.11.0", - "@redocly/config": "0.1.2", + "@redocly/config": "0.1.4", "@redocly/graphql-docs": "0.6.39", - "@redocly/openapi-core": "1.10.3", - "@redocly/openapi-docs": "3.0.0-alpha.87", - "@redocly/portal-plugin-mock-server": "^0.1.7", - "@redocly/theme": "0.35.3", + "@redocly/openapi-core": "1.10.4", + "@redocly/openapi-docs": "3.0.0-alpha.88", + "@redocly/portal-plugin-mock-server": "^0.1.9", + "@redocly/theme": "0.35.5", "@redocly/xml-crypto": "~3.0.1", "@tanstack/react-query": "4.0.5", "@wojtekmaj/react-datetimerange-picker": "^5.0.1", @@ -2040,11 +2041,11 @@ } }, "node_modules/@redocly/theme": { - "version": "0.35.3", - "resolved": "https://registry.npmjs.org/@redocly/theme/-/theme-0.35.3.tgz", - "integrity": "sha512-LljYbwbZXg9JejAVkdB6W4kOH9JxpxWtZK5d57XtYDrjylNtEzLZzIbGwIulawAJQvVNB32DluNU1DQx6N2ouA==", + "version": "0.35.5", + "resolved": "https://registry.npmjs.org/@redocly/theme/-/theme-0.35.5.tgz", + "integrity": "sha512-3RAAJoFAqkcY7PfD5M/B7WcMrx1oO3Yv9UHwXtGXx6D3DWVVaPo5OPfGJ9e35pb+XtXvZDHJVq5fbT7KWZdCzA==", "dependencies": { - "@redocly/config": "0.1.2", + "@redocly/config": "0.1.4", "copy-to-clipboard": "^3.3.3", "highlight-words-core": "^1.2.2", "hotkeys-js": "^3.10.1", @@ -4030,9 +4031,9 @@ } }, "node_modules/core-js": { - "version": "3.36.0", - "resolved": "https://registry.npmjs.org/core-js/-/core-js-3.36.0.tgz", - "integrity": "sha512-mt7+TUBbTFg5+GngsAxeKBTl5/VS0guFeJacYge9OmHb+m058UwwIm41SE9T4Den7ClatV57B6TYTuJ0CX1MAw==", + "version": "3.36.1", + "resolved": "https://registry.npmjs.org/core-js/-/core-js-3.36.1.tgz", + "integrity": "sha512-BTvUrwxVBezj5SZ3f10ImnX2oRByMxql3EimVqMysepbC9EeMUOpLwdy6Eoili2x6E4kf+ZUB5k/+Jv55alPfA==", "hasInstallScript": true, "peer": true, "funding": { @@ -4041,9 +4042,9 @@ } }, "node_modules/core-js-pure": { - "version": "3.36.0", - "resolved": "https://registry.npmjs.org/core-js-pure/-/core-js-pure-3.36.0.tgz", - "integrity": "sha512-cN28qmhRNgbMZZMc/RFu5w8pK9VJzpb2rJVR/lHuZJKwmXnoWOpXmMkxqBB514igkp1Hu8WGROsiOAzUcKdHOQ==", + "version": "3.36.1", + "resolved": "https://registry.npmjs.org/core-js-pure/-/core-js-pure-3.36.1.tgz", + "integrity": "sha512-NXCvHvSVYSrewP0L5OhltzXeWFJLo2AL2TYnj6iLV3Bw8mM62wAQMNgUCRI6EBu6hVVpbCxmOPlxh1Ikw2PfUA==", "hasInstallScript": true, "funding": { "type": "opencollective", @@ -4375,9 +4376,9 @@ } }, "node_modules/detect-libc": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.0.2.tgz", - "integrity": "sha512-UX6sGumvvqSaXgdKGUsgZWqcUyIXZ/vZTrlRT/iobiKhGL0zL4d3osHj3uqllWJK+i+sixDS/3COVEOFbupFyw==", + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.0.3.tgz", + "integrity": "sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw==", "optional": true, "engines": { "node": ">=8" @@ -4457,9 +4458,9 @@ } }, "node_modules/dompurify": { - "version": "2.4.7", - "resolved": "https://registry.npmjs.org/dompurify/-/dompurify-2.4.7.tgz", - "integrity": "sha512-kxxKlPEDa6Nc5WJi+qRgPbOAbgTpSULL+vI3NUXsZMlkJxTqYI9wg5ZTay2sFrdZRWHPWNi+EdAhcJf81WtoMQ==" + "version": "2.4.8", + "resolved": "https://registry.npmjs.org/dompurify/-/dompurify-2.4.8.tgz", + "integrity": "sha512-O90eQdAQOiLZoE9pEgPz3JfqXh5yrhJHv0/LzOv3wWFLTWUqAKaISD1aWASQTLshLM+jziuSerbtUESKK8Jibw==" }, "node_modules/domutils": { "version": "3.1.0", @@ -7508,9 +7509,9 @@ } }, "node_modules/jotai": { - "version": "2.7.0", - "resolved": "https://registry.npmjs.org/jotai/-/jotai-2.7.0.tgz", - "integrity": "sha512-4qsyFKu4MprI39rj2uoItyhu24NoCHzkOV7z70PQr65SpzV6CSyhQvVIfbNlNqOIOspNMdf5OK+kTXLvqe63Jw==", + "version": "2.7.1", + "resolved": "https://registry.npmjs.org/jotai/-/jotai-2.7.1.tgz", + "integrity": "sha512-bsaTPn02nFgWNP6cBtg/htZhCu4s0wxqoklRHePp6l/vlsypR9eLn7diRliwXYWMXDpPvW/LLA2afI8vwgFFaw==", "engines": { "node": ">=12.20.0" }, @@ -9151,9 +9152,9 @@ } }, "node_modules/react-hook-form": { - "version": "7.51.0", - "resolved": "https://registry.npmjs.org/react-hook-form/-/react-hook-form-7.51.0.tgz", - "integrity": "sha512-BggOy5j58RdhdMzzRUHGOYhSz1oeylFAv6jUSG86OvCIvlAvS7KvnRY7yoAf2pfEiPN7BesnR0xx73nEk3qIiw==", + "version": "7.51.1", + "resolved": "https://registry.npmjs.org/react-hook-form/-/react-hook-form-7.51.1.tgz", + "integrity": "sha512-ifnBjl+kW0ksINHd+8C/Gp6a4eZOdWyvRv0UBaByShwU8JbVx5hTcTWEcd5VdybvmPTATkVVXk9npXArHmo56w==", "engines": { "node": ">=12.22.0" }, diff --git a/package.json b/package.json index 5ff42dd604..e8d99c9144 100644 --- a/package.json +++ b/package.json @@ -15,7 +15,7 @@ "@codemirror/state": "6.3.3", "@codemirror/view": "^6.22.2", "@lezer/highlight": "^1.2.0", - "@redocly/realm": "^0.78.4", + "@redocly/realm": "^0.78.6", "@uiw/codemirror-themes": "4.21.21", "@uiw/react-codemirror": "^4.21.21", "@xrplf/isomorphic": "^1.0.0-beta.1", diff --git a/redirects.yaml b/redirects.yaml index a04b1f6e5f..435fe9e648 100644 --- a/redirects.yaml +++ b/redirects.yaml @@ -1,3 +1,6 @@ +'/docs/references/protocol/transactions/transaction-results/transaction-results/': + to: /docs/references/protocol/transactions/transaction-results/ + type: 301 xrp-ledger-rpc-tool.html: to: /resources/dev-tools/rpc-tool type: 301 diff --git a/resources/contribute-code/create-custom-transactors.md b/resources/contribute-code/create-custom-transactors.md index 5514f6857a..98673c4594 100644 --- a/resources/contribute-code/create-custom-transactors.md +++ b/resources/contribute-code/create-custom-transactors.md @@ -81,7 +81,7 @@ The `preflight` function checks for errors in the transaction itself before acce - [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp) - [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp) -- `rippled` summarizes transaction results with result codes. See: [Transaction Results](../../docs/references/protocol/transactions/transaction-results/transaction-results.md) +- `rippled` summarizes transaction results with result codes. See: [Transaction Results](../../docs/references/protocol/transactions/transaction-results/index.md) ```c++ CreateCheck::preflight(PreflightContext const& ctx) diff --git a/resources/known-amendments.md b/resources/known-amendments.md index 1a52792291..824088a23d 100644 --- a/resources/known-amendments.md +++ b/resources/known-amendments.md @@ -1114,7 +1114,7 @@ This amendment allows addresses to have a list of signers who can authorize tran Signers can be funded or unfunded addresses. Funded addresses in a signer list can sign using a regular key (if defined) or master key (unless disabled). Unfunded addresses can sign with a master key. Multi-signed transactions have the same permissions as transactions signed with a regular key. -An address with a SignerList can disable the master key even if a regular key is not defined. An address with a SignerList can also remove a regular key even if the master key is disabled. The `tecMASTER_DISABLED` transaction result code is renamed `tecNO_ALTERNATIVE_KEY`. The `tecNO_REGULAR_KEY` transaction result is retired and replaced with `tecNO_ALTERNATIVE_KEY`. Additionally, this amendment adds the following new [transaction result codes](../docs/references/protocol/transactions/transaction-results/transaction-results.md): +An address with a SignerList can disable the master key even if a regular key is not defined. An address with a SignerList can also remove a regular key even if the master key is disabled. The `tecMASTER_DISABLED` transaction result code is renamed `tecNO_ALTERNATIVE_KEY`. The `tecNO_REGULAR_KEY` transaction result is retired and replaced with `tecNO_ALTERNATIVE_KEY`. Additionally, this amendment adds the following new [transaction result codes](../docs/references/protocol/transactions/transaction-results/index.md): * `temBAD_SIGNER` * `temBAD_QUORUM` diff --git a/sidebars.yaml b/sidebars.yaml index 970a3c8534..0f8cfc16c9 100644 --- a/sidebars.yaml +++ b/sidebars.yaml @@ -374,7 +374,7 @@ - page: docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md - page: docs/references/protocol/transactions/pseudo-transaction-types/setfee.md - page: docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md - - page: docs/references/protocol/transactions/transaction-results/transaction-results.md + - page: docs/references/protocol/transactions/transaction-results/index.md expanded: false items: - page: docs/references/protocol/transactions/transaction-results/tec-codes.md