From 91ed27a9088e30294d5c5d9e4f14d9ac08627e2e Mon Sep 17 00:00:00 2001 From: Amarantha Kulkarni Date: Wed, 7 Feb 2024 10:45:56 -0800 Subject: [PATCH] Update links after renaming accounts.md to index.md --- @i18n/ja/concepts/accounts/account-types.md | 2 +- @i18n/ja/concepts/accounts/addresses.md | 2 +- @i18n/ja/concepts/accounts/cryptographic-keys.md | 4 ++-- @i18n/ja/concepts/accounts/deleting-accounts.md | 2 +- @i18n/ja/concepts/accounts/depositauth.md | 2 +- .../ja/concepts/consensus-protocol/consensus-structure.md | 2 +- .../ja/concepts/consensus-protocol/invariant-checking.md | 4 ++-- @i18n/ja/concepts/payment-types/direct-xrp-payments.md | 4 ++-- @i18n/ja/concepts/tokens/decentralized-exchange/index.md | 2 +- @i18n/ja/concepts/tokens/fungible-tokens/index.md | 2 +- .../concepts/tokens/nfts/guaranteeing-a-fixed-supply.md | 2 +- .../finality-of-results/look-up-transaction-results.md | 4 ++-- .../concepts/transactions/source-and-destination-tags.md | 2 +- @i18n/ja/docs/_snippets/data_types/account_sequence.md | 2 +- @i18n/ja/docs/introduction/transactions-and-requests.md | 2 +- .../key-generation-methods/wallet_propose.md | 2 +- .../public-api-methods/account-methods/account_offers.md | 2 +- @i18n/ja/docs/references/protocol/binary-format.md | 4 ++-- .../references/protocol/data-types/base58-encodings.md | 2 +- .../references/protocol/data-types/basic-data-types.md | 2 +- .../references/protocol/data-types/currency-formats.md | 2 +- .../ledger-data/ledger-entry-types/accountroot.md | 4 ++-- .../protocol/ledger-data/ledger-entry-types/ticket.md | 2 +- .../references/protocol/transactions/common-fields.md | 2 +- .../transactions/transaction-results/tem-codes.md | 2 +- .../references/protocol/transactions/types/checkcreate.md | 4 ++-- .../references/protocol/transactions/types/payment.md | 2 +- .../manage-account-settings/disable-master-key-pair.md | 4 ++-- .../manage-account-settings/offline-account-setup.md | 8 ++++---- .../manage-account-settings/require-destination-tags.md | 2 +- .../tasks/manage-account-settings/set-up-multi-signing.md | 4 ++-- @i18n/ja/docs/tutorials/tasks/send-xrp.md | 2 +- .../use-payment-channels/index.md | 2 +- @i18n/ja/docs/use-cases/defi/list-xrp-as-an-exchange.md | 2 +- .../docs/use-cases/payments/peer-to-peer-payments-uc.md | 2 +- @i18n/ja/resources/known-amendments.md | 4 ++-- docs/_snippets/data_types/account_sequence.md | 2 +- docs/concepts/accounts/account-types.md | 2 +- docs/concepts/accounts/addresses.md | 2 +- docs/concepts/accounts/cryptographic-keys.md | 4 ++-- docs/concepts/accounts/deleting-accounts.md | 2 +- docs/concepts/accounts/depositauth.md | 2 +- docs/concepts/consensus-protocol/consensus-structure.md | 2 +- docs/concepts/consensus-protocol/invariant-checking.md | 4 ++-- docs/concepts/tokens/decentralized-exchange/index.md | 2 +- docs/concepts/tokens/fungible-tokens/index.md | 2 +- docs/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md | 2 +- .../finality-of-results/look-up-transaction-results.md | 4 ++-- docs/concepts/transactions/source-and-destination-tags.md | 2 +- docs/introduction/transactions-and-requests.md | 2 +- .../key-generation-methods/wallet_propose.md | 2 +- .../public-api-methods/account-methods/account_offers.md | 2 +- .../public-api-methods/subscription-methods/subscribe.md | 2 +- docs/references/protocol/binary-format.md | 4 ++-- docs/references/protocol/data-types/base58-encodings.md | 2 +- docs/references/protocol/data-types/basic-data-types.md | 2 +- docs/references/protocol/data-types/currency-formats.md | 2 +- .../ledger-data/ledger-entry-types/accountroot.md | 4 ++-- .../protocol/ledger-data/ledger-entry-types/ticket.md | 2 +- docs/references/protocol/transactions/common-fields.md | 2 +- .../transactions/transaction-results/tem-codes.md | 2 +- .../references/protocol/transactions/types/checkcreate.md | 4 ++-- docs/references/protocol/transactions/types/payment.md | 2 +- docs/tutorials/java/get-started.md | 4 ++-- docs/tutorials/javascript/get-started.md | 2 +- docs/tutorials/php/get-started.md | 4 ++-- docs/tutorials/python/get-started.md | 4 ++-- .../manage-account-settings/assign-a-regular-key-pair.md | 2 +- .../change-or-remove-a-regular-key-pair.md | 2 +- .../manage-account-settings/disable-master-key-pair.md | 4 ++-- .../manage-account-settings/offline-account-setup.md | 8 ++++---- .../manage-account-settings/require-destination-tags.md | 2 +- .../tasks/manage-account-settings/set-up-multi-signing.md | 4 ++-- docs/tutorials/tasks/send-xrp.md | 2 +- .../use-escrows/use-an-escrow-as-a-smart-contract.md | 4 ++-- .../use-payment-channels/index.md | 2 +- ...payment-channel-to-enable-an-inter-exchange-network.md | 2 +- docs/use-cases/defi/list-xrp-as-an-exchange.md | 4 ++-- docs/use-cases/payments/peer-to-peer-payments-uc.md | 2 +- resources/known-amendments.md | 4 ++-- 80 files changed, 110 insertions(+), 110 deletions(-) diff --git a/@i18n/ja/concepts/accounts/account-types.md b/@i18n/ja/concepts/accounts/account-types.md index 62a40e4292..4899b14219 100644 --- a/@i18n/ja/concepts/accounts/account-types.md +++ b/@i18n/ja/concepts/accounts/account-types.md @@ -70,7 +70,7 @@ labels: ## 関連項目 - **コンセプト:** - - [アカウント](accounts.md) + - [アカウント](index.md) - [暗号鍵](cryptographic-keys.md) - **チュートリアル:** - [レギュラーキーペアの割り当て](../../tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md) diff --git a/@i18n/ja/concepts/accounts/addresses.md b/@i18n/ja/concepts/accounts/addresses.md index dbca036472..f60959dfc4 100644 --- a/@i18n/ja/concepts/accounts/addresses.md +++ b/@i18n/ja/concepts/accounts/addresses.md @@ -10,7 +10,7 @@ labels: {% partial file="/docs/_snippets/data_types/address.md" /%} -有効なアドレスであれば、資金を入金することで[XRP Ledgerのアカウントになる](accounts.md#creating-accounts)ことができます。また、[レギュラーキー](cryptographic-keys.md)や[署名者リスト](multi-signing.md)のメンバーとして、資金提供されていないアドレスを使用することもできます。資金を供給されたアカウントだけがトランザクションの送信者になることができます。 +有効なアドレスであれば、資金を入金することで[XRP Ledgerのアカウントになる](index.md#creating-accounts)ことができます。また、[レギュラーキー](cryptographic-keys.md)や[署名者リスト](multi-signing.md)のメンバーとして、資金提供されていないアドレスを使用することもできます。資金を供給されたアカウントだけがトランザクションの送信者になることができます。 キーペアの生成を始めとする有効なアドレスの作成は、厳密には数学的な作業です。キーペアの生成とアドレスの計算は、XRP Ledgerや他のいかなる第三者とも通信することなく、完全にオフラインで行うことができます。公開鍵からアドレスへの変換には一方向ハッシュ関数が使用されるため、公開鍵とアドレスの一致を確認することは可能ですが、アドレスのみから公開鍵を導き出すことは不可能です。(これが署名付きトランザクションに公開鍵と送信者のアドレスを含める理由の一部です)。 diff --git a/@i18n/ja/concepts/accounts/cryptographic-keys.md b/@i18n/ja/concepts/accounts/cryptographic-keys.md index 5a4a3bbd4b..f87d3da1d5 100644 --- a/@i18n/ja/concepts/accounts/cryptographic-keys.md +++ b/@i18n/ja/concepts/accounts/cryptographic-keys.md @@ -62,14 +62,14 @@ XRP Ledgerのトランザクションには、ネットワークがトランザ ### アカウントIDとアドレス -**アカウントID**は、[アカウント](accounts.md)またはキーペアの中核となる識別子です。これは公開鍵から派生します。XRP Ledgerのプロトコルでは、アカウントIDは20バイトのバイナリデータです。ほとんどのXRP Ledger APIは、アカウントIDをアドレスとして表現し、次の2つのフォーマットのうちの1つで表現します。 +**アカウントID**は、[アカウント](index.md)またはキーペアの中核となる識別子です。これは公開鍵から派生します。XRP Ledgerのプロトコルでは、アカウントIDは20バイトのバイナリデータです。ほとんどのXRP Ledger APIは、アカウントIDをアドレスとして表現し、次の2つのフォーマットのうちの1つで表現します。 - 「クラシックアドレス」は、[base58][]にチェックサム付きでアカウントIDを書きます。[wallet_proposeメソッド][]のレスポンスでは、これが`account_id`の値となります。 - 「X-Address」は、アカウントIDと[宛先タグ](../transactions/source-and-destination-tags.md)を組み合わせ、チェックサムとともに[base58][]にその値を書き込みます。 どちらの形式でもチェックサムがあるため、わずかな変更でアドレスが無効になり、他の有効なアカウントと入れ替わる可能性はありません。これにより、タイプミスや送信エラーが発生しても、間違った場所に送金されることはありません。 -すべてのアカウントID（またはアドレス）が台帳のアカウントを参照しているわけではないことを知っておくことが重要です。キーとアドレスの導出は、純粋に数学的な操作です。アカウントがXRP Ledgerに情報を持つには、[XRPの支払いを受け](accounts.md#creating-accounts)、[準備金](reserves.md)を満たす必要があります。アカウントは、資金が供給されるまでトランザクションを送信することはできません。 +すべてのアカウントID（またはアドレス）が台帳のアカウントを参照しているわけではないことを知っておくことが重要です。キーとアドレスの導出は、純粋に数学的な操作です。アカウントがXRP Ledgerに情報を持つには、[XRPの支払いを受け](index.md#creating-accounts)、[準備金](reserves.md)を満たす必要があります。アカウントは、資金が供給されるまでトランザクションを送信することはできません。 アカウントIDやアドレスが資金提供されたアカウントを指していない場合でも、そのアカウントIDやアドレスを使用して、[レギュラーキーペア](#レギュラーキーペア)や[署名者リストのメンバー](multi-signing.md)を表すことはできます。 diff --git a/@i18n/ja/concepts/accounts/deleting-accounts.md b/@i18n/ja/concepts/accounts/deleting-accounts.md index 8fb6ad6a1c..97296709be 100644 --- a/@i18n/ja/concepts/accounts/deleting-accounts.md +++ b/@i18n/ja/concepts/accounts/deleting-accounts.md @@ -11,7 +11,7 @@ labels: アカウントの所有者は[AccountDeleteトランザクション][]を送信することで、レジャーからアカウントと関連するエントリーを削除し、アカウントの残りのXRP残高のほとんどを別のアカウントに送ることができます。アカウントの無駄な作成と削除を抑止するため、アカウントの削除には[トランザクションコスト](../transactions/transaction-cost.md)として通常よりも多くのXRPをバーンする必要があります。 いくつかの種類のレジャーエントリーを保有している場合、アカウントの削除がブロックされます。たとえば、(代替可能)トークンの発行者は、そのトークンの発行残高がゼロでなければ、削除することはできません。 -アカウントは削除した後、通常の[アカウントの作成方法](accounts.md#creating-accounts)によって再作成できます。削除後に再作成されたアカウントと、初めて作成されたアカウントに違いはありません。 +アカウントは削除した後、通常の[アカウントの作成方法](index.md#creating-accounts)によって再作成できます。削除後に再作成されたアカウントと、初めて作成されたアカウントに違いはありません。 diff --git a/@i18n/ja/concepts/accounts/depositauth.md b/@i18n/ja/concepts/accounts/depositauth.md index 61a647a363..b5eecf2474 100644 --- a/@i18n/ja/concepts/accounts/depositauth.md +++ b/@i18n/ja/concepts/accounts/depositauth.md @@ -11,7 +11,7 @@ labels: _（[DepositAuth Amendment][]により追加されました。）_ -Deposit Authorizationは、XRP Ledgerの[アカウント](accounts.md)のオプション機能です。Deposit Authorizationが有効な場合、トランザクションはそのトランザクションの送信者がアカウント自体でない限り、アカウントへはどのような資産も送信できません。Deposit Authorizationのアカウントは、次の2つの方法でのみ入金することができます。 +Deposit Authorizationは、XRP Ledgerの[アカウント](index.md)のオプション機能です。Deposit Authorizationが有効な場合、トランザクションはそのトランザクションの送信者がアカウント自体でない限り、アカウントへはどのような資産も送信できません。Deposit Authorizationのアカウントは、次の2つの方法でのみ入金することができます。 - [事前承認](#事前承認)されたアカウントから。 - トランザクションを送信して資金を受け取ることにより。例えば、Deposit Authorizationが設定されたアカウントは、他のアカウントによって開始された[エスクロー](../payment-types/escrow.md)を完了することができます。 diff --git a/@i18n/ja/concepts/consensus-protocol/consensus-structure.md b/@i18n/ja/concepts/consensus-protocol/consensus-structure.md index 8bafcd37e1..cbfa476a5d 100644 --- a/@i18n/ja/concepts/consensus-protocol/consensus-structure.md +++ b/@i18n/ja/concepts/consensus-protocol/consensus-structure.md @@ -19,7 +19,7 @@ XRP Ledger上でアプリケーションを構築する場合は、XRP Ledger AP ピアツーピアサーバーのXRP Ledgerネットワークは世界で共有されている台帳であり、ここから、アプリケーションはこの台帳の内容の状態に関して信頼できる情報を得ることができます。この状態に関する情報には以下の内容が含まれます。 -- 各[アカウント](../accounts/accounts.md)の設定 +- 各[アカウント](../accounts/index.md)の設定 - XRPおよび[トークン](../tokens/index.md)の残高 - 分散型取引所でのオファー（注文） - ネットワーク設定（例: [トランザクションコスト](../transactions/transaction-cost.md)と[準備金](../accounts/reserves.md)の金額） diff --git a/@i18n/ja/concepts/consensus-protocol/invariant-checking.md b/@i18n/ja/concepts/consensus-protocol/invariant-checking.md index 9d2f985279..5f0af96400 100644 --- a/@i18n/ja/concepts/consensus-protocol/invariant-checking.md +++ b/@i18n/ja/concepts/consensus-protocol/invariant-checking.md @@ -90,7 +90,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての ### アカウントルートが削除されていない - **不変条件:** - - [アカウント](../accounts/accounts.md)は、[AccountDeleteトランザクション][]によってのみレジャーから削除することができます。 + - [アカウント](../accounts/index.md)は、[AccountDeleteトランザクション][]によってのみレジャーから削除することができます。 - AccountDelete が成功すると、常にちょうど1つのアカウントが削除されます。 @@ -129,7 +129,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての - **不変条件:** - 新しい[アカウントルート](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md)は、支払いの結果でなければなりません。 - 新しいアカウントルートは、正しい開始[シーケンス](../../references/protocol/data-types/basic-data-types.md#アカウントシーケンス)を持たなければなりません。 - - 1つのトランザクションで複数の新しい[アカウント](../accounts/accounts.md)を作成してはいけません。 + - 1つのトランザクションで複数の新しい[アカウント](../accounts/index.md)を作成してはいけません。 ## 関連項目 diff --git a/@i18n/ja/concepts/payment-types/direct-xrp-payments.md b/@i18n/ja/concepts/payment-types/direct-xrp-payments.md index 1e419ed21d..36eedc1da2 100644 --- a/@i18n/ja/concepts/payment-types/direct-xrp-payments.md +++ b/@i18n/ja/concepts/payment-types/direct-xrp-payments.md @@ -32,7 +32,7 @@ XRP間の直接支払いではPartial Paymentは使用できませんが、Parti XRP Ledgerにそのアドレスの記録が事前に存在していなくても、支払いで[口座準備金](../accounts/reserves.md)の最少額を満たすのに十分なXRPが送金されれば、数学的に有効なアドレスで支払いを受け取ることができます。支払いで十分なXRPを送金できない場合は失敗します。 -詳細は、[アカウント](../accounts/accounts.md#アカウントの作成)を参照してください。 +詳細は、[アカウント](../accounts/index.md#アカウントの作成)を参照してください。 ## アドレスの再利用 @@ -49,7 +49,7 @@ XRP Ledgerでは、支払いを受け取ることができるアドレスは永 1. [Paymentトランザクション][]のパラメータを検証します。トランザクションがXRPを送信、送金するように構成されている場合、トランザクション処理エンジンはそのトランザクションをXRP間の直接支払いとして認識します。検証チェックは次のように行います。 - すべてのフィールドが正しいフォーマットであることを確認します。たとえば、XRPによる直接支払いの場合、`Amount`フィールドは[XRPのdrop数][]でなければなりません。 - - 送信元アドレスがXRP Ledgerの資金供給された[アカウント](../accounts/accounts.md)であることを確認します。 + - 送信元アドレスがXRP Ledgerの資金供給された[アカウント](../accounts/index.md)であることを確認します。 - 指定された署名がすべて、送信元アドレスに対して有効であることを確認します。 - 宛先アドレスと送金元アドレスが異なることを確認します。（[宛先タグ](../transactions/source-and-destination-tags.md)が異なる同一アドレスに送金するだけでは不十分です。） - Paymentを送信するのに十分なXRP残高が送金元にあることを確認します。 diff --git a/@i18n/ja/concepts/tokens/decentralized-exchange/index.md b/@i18n/ja/concepts/tokens/decentralized-exchange/index.md index 44b8dab418..ff9966b740 100644 --- a/@i18n/ja/concepts/tokens/decentralized-exchange/index.md +++ b/@i18n/ja/concepts/tokens/decentralized-exchange/index.md @@ -51,7 +51,7 @@ XRP Ledgerのすべての変更がそうであるように、取引を行うに XRP Ledgerは、成行注文、指値注文、レバレッジ取引などの概念をネイティブに表現するものではありません。カスタムトークンやOfferのプロパティをクリエイティブに利用することで、いくつかは実現できるかもしれません。 -分散型システムであるXRP Ledgerは、取引に関わる[アカウント](../../accounts/accounts.md)の背後にいる実際の人々や組織に関する情報を一切持っていません。また、ユーザーや発行者は、様々な種類の裏付け資産を表すトークンの取引を規制するために、関連する法律に従う必要があります。[凍結](../fungible-tokens/freezes.md)や[認可トラストライン](../fungible-tokens/authorized-trust-lines.md)などの機能は、発行者が関連法規を順守できるよう意図しています。 +分散型システムであるXRP Ledgerは、取引に関わる[アカウント](../../accounts/index.md)の背後にいる実際の人々や組織に関する情報を一切持っていません。また、ユーザーや発行者は、様々な種類の裏付け資産を表すトークンの取引を規制するために、関連する法律に従う必要があります。[凍結](../fungible-tokens/freezes.md)や[認可トラストライン](../fungible-tokens/authorized-trust-lines.md)などの機能は、発行者が関連法規を順守できるよう意図しています。 ## 関連項目 diff --git a/@i18n/ja/concepts/tokens/fungible-tokens/index.md b/@i18n/ja/concepts/tokens/fungible-tokens/index.md index b4e77e250a..f4a9e3f3a2 100644 --- a/@i18n/ja/concepts/tokens/fungible-tokens/index.md +++ b/@i18n/ja/concepts/tokens/fungible-tokens/index.md @@ -18,7 +18,7 @@ labels: それぞれの「トラストライン」は、以下のような _双方向_ の関係から成り立っています。 -- トラストラインが接続する **2つの[アカウント](../../accounts/accounts.md)** の識別子 +- トラストラインが接続する **2つの[アカウント](../../accounts/index.md)** の識別子 - 一方のアカウントから見てプラス、他方のアカウントから見てマイナスとなる、単一の共有された**残高** - 残高がマイナスのアカウントは、一般的にトークンの「発行者」とみなされます。ただし、[API](../../../references/http-websocket-apis/index.md)では、`issuer`という名称はどちらを指すこともあるようです。 - 様々な **設定** とメタデータ。2つのアカウントの _それぞれ_ は、トラストライン上の設定を制御することができます。 diff --git a/@i18n/ja/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md b/@i18n/ja/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md index 22265e0445..c8f280b909 100644 --- a/@i18n/ja/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md +++ b/@i18n/ja/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md @@ -12,7 +12,7 @@ labels: 一定数のNFTを保証するためには、 -1. 新しいアカウント、_発行者_ を作成し、資金を提供します。このアカウントは、コレクション内のトークンの発行者となります。[アカウントの作成](../../accounts/accounts.md#アカウントの作成)を参照してください。 +1. 新しいアカウント、_発行者_ を作成し、資金を提供します。このアカウントは、コレクション内のトークンの発行者となります。[アカウントの作成](../../accounts/index.md#アカウントの作成)を参照してください。 1. `AccountSet`を使用して、自分の運用するウォレットを発行者の認可Minterとして割り当てます。[代理Mint](authorizing-another-minter.md)を参照してください。 1. 運用アカウントで`NFTokenMint`を使ってトークンをミントします。運用中のウォレットには、発行者のためにMintされたすべてのトークンが保管されます。[Mintのバッチ処理](batch-minting.md)をご覧ください 1. 発行者の認可Minterである自分の運用するウォレットを削除するために、`AccountSet`を使用します。 diff --git a/@i18n/ja/concepts/transactions/finality-of-results/look-up-transaction-results.md b/@i18n/ja/concepts/transactions/finality-of-results/look-up-transaction-results.md index 743a134786..d8cc271d04 100644 --- a/@i18n/ja/concepts/transactions/finality-of-results/look-up-transaction-results.md +++ b/@i18n/ja/concepts/transactions/finality-of-results/look-up-transaction-results.md @@ -63,7 +63,7 @@ XRP Ledgerは共有システムとなっていて、すべてのデータが公 } ``` -この例では、rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpnというアドレスを持つ[アカウント](../../accounts/accounts.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/transaction-results.md)は`tesSUCCESS`です。トランザクションは、検証済みのレジャーバージョン46447423に記録されたため、結果は最終的なものです。 ### ケース: 検証済みレジャーに記録されていない @@ -223,7 +223,7 @@ XRPの額は、`AccountRoot`オブジェクトの`Balance`フィールドで追 支払いでいくら支払われたかを確認するには、必ず[delivered_amountフィールド](../../payment-types/partial-payments.md#delivered_amountフィールド)を使用する必要があります。 -支払いにLedgerEntryTypeが`AccountRoot`の`CreatedNode`が含まれている場合は、その支払いによってレジャーの[新しいアカウントへの資金供給](../../accounts/accounts.md#アカウントの作成)が行われたことを意味します。 +支払いにLedgerEntryTypeが`AccountRoot`の`CreatedNode`が含まれている場合は、その支払いによってレジャーの[新しいアカウントへの資金供給](../../accounts/index.md#アカウントの作成)が行われたことを意味します。 #### トークンでの支払い diff --git a/@i18n/ja/concepts/transactions/source-and-destination-tags.md b/@i18n/ja/concepts/transactions/source-and-destination-tags.md index fe790bdcaa..ae946371d4 100644 --- a/@i18n/ja/concepts/transactions/source-and-destination-tags.md +++ b/@i18n/ja/concepts/transactions/source-and-destination-tags.md @@ -22,7 +22,7 @@ _送信元タグ_と_宛先タグ_は、XRP Ledgerの[支払い](../payment-type ## 理由 -他の分散型台帳では、顧客ごとに異なる入金アドレスを使用するのが一般的です。XRP Ledgerでは、支払いを受け取るためには、そのアドレスは入金され有効化済みの[アカウント](../accounts/accounts.md)でなければなりません。XRP Ledgerで他と同じアプローチを用いると、ネットワーク内の全てのサーバのリソースを無駄に消費し、各アドレスに対して[準備金](../accounts/reserves.md)の金額を無制限に確保しなければならな苦なり、大きなコストがかかります。 +他の分散型台帳では、顧客ごとに異なる入金アドレスを使用するのが一般的です。XRP Ledgerでは、支払いを受け取るためには、そのアドレスは入金され有効化済みの[アカウント](../accounts/index.md)でなければなりません。XRP Ledgerで他と同じアプローチを用いると、ネットワーク内の全てのサーバのリソースを無駄に消費し、各アドレスに対して[準備金](../accounts/reserves.md)の金額を無制限に確保しなければならな苦なり、大きなコストがかかります。 送信元タグと宛先タグは、入金と支払いを個別の顧客にマッピングする、より軽量な方法を提供します。 diff --git a/@i18n/ja/docs/_snippets/data_types/account_sequence.md b/@i18n/ja/docs/_snippets/data_types/account_sequence.md index d53e25a61e..1f64fd7331 100644 --- a/@i18n/ja/docs/_snippets/data_types/account_sequence.md +++ b/@i18n/ja/docs/_snippets/data_types/account_sequence.md @@ -1,6 +1,6 @@ シーケンス番号とは、32ビットの符号なし整数であり、指定された送金元からのトランザクションが正しい順序で1回だけ実行されるようにするために使用されます。 -すべての[XRP Ledgerアカウント](../../concepts/accounts/accounts.md)には、`Sequence`フィールドに1つのシーケンス番号があり、アカウントがトランザクションを送信し、そのトランザクションが[検証済みレジャー](../../concepts/ledgers/index.md)に記録されるたびに、1ずつ増加します。シーケンス番号は各[トランザクション](../../concepts/transactions/index.md)の`Sequence`フィールドにもあり、そのトランザクションが実行される際にアカウントの現在のシーケンス番号と一致している必要があります。各アカウントで、各シーケンス番号は番号順に一度だけ使用できます。 +すべての[XRP Ledgerアカウント](../../concepts/accounts/index.md)には、`Sequence`フィールドに1つのシーケンス番号があり、アカウントがトランザクションを送信し、そのトランザクションが[検証済みレジャー](../../concepts/ledgers/index.md)に記録されるたびに、1ずつ増加します。シーケンス番号は各[トランザクション](../../concepts/transactions/index.md)の`Sequence`フィールドにもあり、そのトランザクションが実行される際にアカウントの現在のシーケンス番号と一致している必要があります。各アカウントで、各シーケンス番号は番号順に一度だけ使用できます。 [DeletableAccounts Amendment](/resources/known-amendments.md#deletableaccounts) を適用する場合、アカウントの`Sequence`番号の始まりが、アカウントが作成されたレジャーバージョンの[レジャーインデックス][]と一致します。DeletableAccountsを適用しない場合、どのアカウントの`Sequence`番号も1で始まります。 diff --git a/@i18n/ja/docs/introduction/transactions-and-requests.md b/@i18n/ja/docs/introduction/transactions-and-requests.md index fde5c64ab4..f31086f7a3 100644 --- a/@i18n/ja/docs/introduction/transactions-and-requests.md +++ b/@i18n/ja/docs/introduction/transactions-and-requests.md @@ -110,6 +110,6 @@ ClioサーバはXRPL上の他のrippledサーバの負荷の一部を軽減し } } ``` -Accountのフィールドについては、[アカウント](../concepts/accounts/accounts.md)をご覧ください。 +Accountのフィールドについては、[アカウント](../concepts/accounts/index.md)をご覧ください。 次のページ: [ソフトウェアエコシステム](software-ecosystem.md) diff --git a/@i18n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md b/@i18n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md index 49d9da0596..6e6e87da45 100644 --- a/@i18n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md +++ b/@i18n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md @@ -10,7 +10,7 @@ labels: # wallet_propose [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") -`wallet_propose`メソッドを使用して、キーペアとXRP Ledgerアドレスを生成します。このコマンドは単にキーとアドレス値を生成し、XRP Ledger自体には何ら影響しません。レジャー上で資金供給済みのアドレスになるには、そのアドレスで、[必要準備金](../../../../concepts/accounts/reserves.md)を満たすのに十分なXRPの[Paymentトランザクションを受け取る](../../../../concepts/accounts/accounts.md#アカウントの作成)必要があります。 +`wallet_propose`メソッドを使用して、キーペアとXRP Ledgerアドレスを生成します。このコマンドは単にキーとアドレス値を生成し、XRP Ledger自体には何ら影響しません。レジャー上で資金供給済みのアドレスになるには、そのアドレスで、[必要準備金](../../../../concepts/accounts/reserves.md)を満たすのに十分なXRPの[Paymentトランザクションを受け取る](../../../../concepts/accounts/index.md#アカウントの作成)必要があります。 *`wallet_propose`メソッドは、権限のないユーザーは実行できない[管理メソッド](../index.md)です。*(このコマンドは、アカウントの機密情報を求めてネットワーク上の伝送情報をスニッフィングする人々から守るためにadminコマンドとされています。adminコマンドは通常、外部ネットワーク上で伝送されることはありません。） diff --git a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md index e5fd6d7e31..08087e0047 100644 --- a/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md +++ b/@i18n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md @@ -9,7 +9,7 @@ labels: # account_offers [[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") -`account_offers`メソッドは、特定の[アカウント](../../../../concepts/accounts/accounts.md)から出された[オファー](../../../../concepts/tokens/decentralized-exchange/offers.md)のうち、特定の[レジャーバージョン](../../../../concepts/ledgers/index.md)で未処理であったオファーのリストを取得します。 +`account_offers`メソッドは、特定の[アカウント](../../../../concepts/accounts/index.md)から出された[オファー](../../../../concepts/tokens/decentralized-exchange/offers.md)のうち、特定の[レジャーバージョン](../../../../concepts/ledgers/index.md)で未処理であったオファーのリストを取得します。 ## リクエストのフォーマット diff --git a/@i18n/ja/docs/references/protocol/binary-format.md b/@i18n/ja/docs/references/protocol/binary-format.md index ce418944de..b6f1f40efa 100644 --- a/@i18n/ja/docs/references/protocol/binary-format.md +++ b/@i18n/ja/docs/references/protocol/binary-format.md @@ -177,7 +177,7 @@ curated_anchors: | タイプ名 | タイプコード | ビット長 | [長さプレフィクスを付加する]? | 説明 | |:--------------|:----------|:-----------|:-------------------|----------------| -| [AccountID][] | 8 | 160 | はい | [アカウント](../../concepts/accounts/accounts.md)の一意のID。 | +| [AccountID][] | 8 | 160 | はい | [アカウント](../../concepts/accounts/index.md)の一意のID。 | | [Amount][] | 6 | 64または384 | いいえ | XRPまたはトークンの金額。フィールドの長さは、XRPの場合は64ビット、トークンの場合は384ビット（64+160+160）です。 | | [Blob][] | 7 | 可変 | はい | 任意のバイナリデータ。このようなフィールドの中で重要なフィールドとして、`TxnSignature`（トランザクションを承認する署名）があります。 | | [Hash128][] | 4 | 128 | いいえ | 128ビットの任意のバイナリ値。該当する唯一のフィールドは`EmailHash`です。これは、[Gravatar](https://www.gravatar.com/)を取得する目的でアカウント所有者のメールのMD-5ハッシュを保管するフィールドです。 | @@ -210,7 +210,7 @@ curated_anchors: ### AccountIDフィールド [AccountID]: #accountidフィールド -このタイプのフィールドには、XRP Ledger[アカウント](../../concepts/accounts/accounts.md)の160ビットのIDが含まれています。JSONではこれらのフィールドは[base58][] XRP Ledger「アドレス」および追加のチェックサムデータとして表示されます。このため、スペルミスが有効なアドレスとなることがありません。（このエンコードは「Base58Check」とも呼ばれ、誤ったアドレスへの送金を防止します。）これらのフィールドのバイナリフォーマットにはチェックサムデータは含まれておらず、また[アドレスのbase58エンコード](../../concepts/accounts/addresses.md#アドレスのエンコード)で使用される`0x00`「タイププレフィクス」も含まれていません。（ただし、バイナリフォーマットは主に署名済みトランザクションに使用されるため、署名済みトランザクションを転記する際にスペルミスなどのエラーが発生すると署名が無効となり、送金できなくなります。） +このタイプのフィールドには、XRP Ledger[アカウント](../../concepts/accounts/index.md)の160ビットのIDが含まれています。JSONではこれらのフィールドは[base58][] XRP Ledger「アドレス」および追加のチェックサムデータとして表示されます。このため、スペルミスが有効なアドレスとなることがありません。（このエンコードは「Base58Check」とも呼ばれ、誤ったアドレスへの送金を防止します。）これらのフィールドのバイナリフォーマットにはチェックサムデータは含まれておらず、また[アドレスのbase58エンコード](../../concepts/accounts/addresses.md#アドレスのエンコード)で使用される`0x00`「タイププレフィクス」も含まれていません。（ただし、バイナリフォーマットは主に署名済みトランザクションに使用されるため、署名済みトランザクションを転記する際にスペルミスなどのエラーが発生すると署名が無効となり、送金できなくなります。） スタンドアロンフィールドとして表示されるAccountID（`Account`や`Destination`など）の長さは固定長の160ビットですが、[長さプレフィクスが付加](#長さプレフィクスを付加する)されます。その結果、これらのフィールドの長さインディケーターは常に`0x14`バイトになります。特殊フィールドの子として示されるAccountID（[Amount `issuer`][Amount]、[PathSet `account`][PathSet]など）では長さプレフィクスは付加 _されません_ 。 diff --git a/@i18n/ja/docs/references/protocol/data-types/base58-encodings.md b/@i18n/ja/docs/references/protocol/data-types/base58-encodings.md index b46b1d465b..cc3e249a3d 100644 --- a/@i18n/ja/docs/references/protocol/data-types/base58-encodings.md +++ b/@i18n/ja/docs/references/protocol/data-types/base58-encodings.md @@ -21,7 +21,7 @@ XRP Ledgerにより、さまざまなタイプの値をエンコードする前 ¹ コンテンツのサイズでは1バイトのタイププレフィクスは除外されます。 -[アカウント]: ../../../concepts/accounts/accounts.md +[アカウント]: ../../../concepts/accounts/index.md ## 関連項目 diff --git a/@i18n/ja/docs/references/protocol/data-types/basic-data-types.md b/@i18n/ja/docs/references/protocol/data-types/basic-data-types.md index ca0f7b5a1b..a0762c9bf5 100644 --- a/@i18n/ja/docs/references/protocol/data-types/basic-data-types.md +++ b/@i18n/ja/docs/references/protocol/data-types/basic-data-types.md @@ -8,7 +8,7 @@ seo: さまざまなタイプのオブジェクトがそれぞれ異なる方法で一意に識別されます。 -[アカウント](../../../concepts/accounts/accounts.md)は`"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"`のような[アドレス][]で一意に識別されます。アドレスは常に「r」で始まります。`rippled`メソッドの多くは、16進数表記に対応しています。 +[アカウント](../../../concepts/accounts/index.md)は`"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"`のような[アドレス][]で一意に識別されます。アドレスは常に「r」で始まります。`rippled`メソッドの多くは、16進数表記に対応しています。 [トランザクション](../transactions/index.md)は、トランザクションのバイナリフォーマットの[ハッシュ][]で識別されます。また、トランザクションは送信アカウントと[シーケンス番号][]でも識別できます。 diff --git a/@i18n/ja/docs/references/protocol/data-types/currency-formats.md b/@i18n/ja/docs/references/protocol/data-types/currency-formats.md index 146aa0639e..2144321d21 100644 --- a/@i18n/ja/docs/references/protocol/data-types/currency-formats.md +++ b/@i18n/ja/docs/references/protocol/data-types/currency-formats.md @@ -57,7 +57,7 @@ XRPの金額は負になることはありません。 |:-----------|:---------------------|:-----------------------------------| | `currency` | 文字列 - [通貨コード][] | トークンの任意の通貨コード。`XRP`は使用できません。 | | `value` | [文字列フォーマット][] | トークンの金額を10進数で表します。1.23e11`は123,000,000,000を意味します。e` と `E` の両方を使用することができます。残高を表示する場合には負の値を指定することができますが、送信金額を指定する場合などには負の値を指定することはできません。 | -| `issuer` | 文字列 | 一般的には、このトークンを発行する[アカウント](../../../concepts/accounts/accounts.md)を指します。特殊なケースでは、トークンを保持しているアカウントを指します(例えば、[Clawback](../transactions/types/clawback.md)トランザクションの場合など)。 | +| `issuer` | 文字列 | 一般的には、このトークンを発行する[アカウント](../../../concepts/accounts/index.md)を指します。特殊なケースでは、トークンを保持しているアカウントを指します(例えば、[Clawback](../transactions/types/clawback.md)トランザクションの場合など)。 | [文字列フォーマット]: #文字列フォーマット diff --git a/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index 86fa8efed5..1a85a616b1 100644 --- a/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -10,7 +10,7 @@ labels: # AccountRoot [[ソース]](https://github.com/xrplf/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L27 "Source") -`AccountRoot`オブジェクトタイプは、1つの[アカウント](../../../../concepts/accounts/accounts.md)、そのアカウントの設定、XRP残高を記述します。 +`AccountRoot`オブジェクトタイプは、1つの[アカウント](../../../../concepts/accounts/index.md)、そのアカウントの設定、XRP残高を記述します。 ## {% $frontmatter.seo.title %} JSONの例 @@ -39,7 +39,7 @@ labels: | フィールド | JSONの型 | [内部の型][] | 必須？ | 説明 | |:------------------------------|:---------|:------------------|:------|:------| -| `Account` | 文字列 | AccountID | はい | この[アカウント](../../../../concepts/accounts/accounts.md)を識別するための（クラシック）アドレスです。 | +| `Account` | 文字列 | AccountID | はい | この[アカウント](../../../../concepts/accounts/index.md)を識別するための（クラシック）アドレスです。 | | `AccountTxnID` | 文字列 | Hash256 | いいえ | このアカウントから直近に送信されたトランザクションの識別ハッシュ。このフィールドは、[`AccountTxnID`トランザクションフィールド](../../transactions/common-fields.md#accounttxnid)を使うために有効になっていなければなりません。これを有効にするには、[`asfAccountTxnID`フラグを有効にしたAccountSetトランザクション](../../transactions/types/accountset.md#accountsetのフラグ)を送信してください。 | | `AMMID` | 文字列 | Hash256 | いいえ | _([AMM amendment][] {% not-enabled /%}が必要です。)_ 対応するAMMレジャーエントリのレジャーエントリID。アカウント作成時に設定します。AMM以外のアカウントでは常に省略されます。 | | `Balance` | 文字列 | Amount | いいえ | アカウントの現在の[drop単位のXRP残高][XRP、drop単位]で、文字列で表現されます。 | diff --git a/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md index b5c655dfa4..f3f25c2ef3 100644 --- a/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md +++ b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md @@ -35,7 +35,7 @@ _([TicketBatch amendment][]が必要です)_ | フィールド | JSONの型 | 内部の型 | 説明 　　　　 | |:--------------------|:----------|:--------------|:---------------------------| | `LedgerEntryType` | 文字列 | UInt16 | 文字列 `Ticket` にマッピングされた値 `0x0054` は、このオブジェクトが {% $frontmatter.seo.title %} オブジェクトであることを示しています。 | -| `Account` | 文字列 | AccountID | このチケットを所有する[アカウント](../../../../concepts/accounts/accounts.md)です。 | +| `Account` | 文字列 | AccountID | このチケットを所有する[アカウント](../../../../concepts/accounts/index.md)です。 | | `Flags` | Number | UInt32 | ブール値フラグのビットマップ。Ticketにはフラグが定義されていないため、この値は常に0です。 | | `OwnerNode` | 文字列 | UInt64 | 送金元の所有者ディレクトリが複数ページで構成されている場合に、このオブジェクトにリンクしているページを示すヒントです。注記: このオブジェクトには、オブジェクトを含む所有者ディレクトリへの直接リンクは含まれていません。これは、その値を`Account`から取得できるためです。 | | `PreviousTxnID` | 文字列 | Hash256 | 最後にこのオブジェクトを変更した[トランザクション](../../../../concepts/transactions/index.md)の識別用ハッシュ。 | diff --git a/@i18n/ja/docs/references/protocol/transactions/common-fields.md b/@i18n/ja/docs/references/protocol/transactions/common-fields.md index d24fccf6cf..c054e4c4b2 100644 --- a/@i18n/ja/docs/references/protocol/transactions/common-fields.md +++ b/@i18n/ja/docs/references/protocol/transactions/common-fields.md @@ -12,7 +12,7 @@ labels: | フィールド | JSONの型 | [内部の型][] | 説明 | |:-------------------|:-----------------|:------------------|:-----------------| -| Account | 文字列 | AccountID | _（必須）_ トランザクションを開始した[アカウント](../../../concepts/accounts/accounts.md)の一意アドレス。 | +| Account | 文字列 | AccountID | _（必須）_ トランザクションを開始した[アカウント](../../../concepts/accounts/index.md)の一意アドレス。 | | TransactionType | 文字列 | UInt16 | _（必須）_ トランザクションのタイプ。有効なタイプは、`Payment`、`OfferCreate`、`OfferCancel`、`TrustSet`、`AccountSet`、`SetRegularKey`、`SignerListSet`、`EscrowCreate`、`EscrowFinish`、`EscrowCancel`、`PaymentChannelCreate`、`PaymentChannelFund`、`PaymentChannelClaim`、`DepositPreauth`です。 | | Fee | 文字列 | Amount | _（必須。[自動入力可能][]）_ 整数で表したXRPの額（drop単位）。このトランザクションをネットワークに送信するためのコストとして消却されます。トランザクションのタイプによっては、最小要件が異なります。詳細は、[トランザクションコスト][]を参照してください。 | | Sequence | 符号なし整数 | UInt32 | _（必須。[自動入力可能][]）_ トランザクションを開始したアカウントに関連付けられた、トランザクションのシーケンス番号。トランザクションが有効とみなされるのは、その`Sequence`番号が、同一のアカウントの直前トランザクションよりも1大きい場合のみです。保留中のトランザクションを`Sequence`番号を使用して無効にする方法については、[トランザクションのキャンセルまたはスキップ](../../../concepts/transactions/finality-of-results/canceling-a-transaction.md)を参照してください。 | diff --git a/@i18n/ja/docs/references/protocol/transactions/transaction-results/tem-codes.md b/@i18n/ja/docs/references/protocol/transactions/transaction-results/tem-codes.md index cc8380936e..782bc57e63 100644 --- a/@i18n/ja/docs/references/protocol/transactions/transaction-results/tem-codes.md +++ b/@i18n/ja/docs/references/protocol/transactions/transaction-results/tem-codes.md @@ -31,7 +31,7 @@ labels: | `temBAD_SEND_XRP_PATHS` | [Paymentトランザクション][]で、XRP送金時の`Paths`が指定されていますが、XRP間の支払いは常に直接行われます。 | | `temBAD_SEQUENCE` | トランザクションは、トランザクション自体の`Sequence`番号よりも大きいシーケンス番号を参照します。例えば、取り消したいオファーは、そのオファーを取り消すトランザクションよりも後に置く必要があります。 | | `temBAD_SIGNATURE` | このトランザクションを承認するための署名がないか、または署名の形式が適切ではありません。（適切な形式の署名がアカウントで承認されない場合は、[tecNO_PERMISSION](tec-codes.md)を参照してください。） | -| `temBAD_SRC_ACCOUNT` | このトランザクションの送信元の`Account`（「支払元アカウント」）の[アカウント](../../../../concepts/accounts/accounts.md)アドレスは適切な形式ではありません。 | +| `temBAD_SRC_ACCOUNT` | このトランザクションの送信元の`Account`（「支払元アカウント」）の[アカウント](../../../../concepts/accounts/index.md)アドレスは適切な形式ではありません。 | | `temBAD_TRANSFER_RATE` | [AccountSetトランザクションの`TransferRate`フィールド](../types/accountset.md#transferrate)のフォーマットが適切ではないか、または許容範囲外です。 | | `temCANNOT_PREAUTH_SELF` | [DepositPreauthトランザクション][]の送信者は、事前承認対象のアカウントとしても指定されていました。自分自身を事前承認することはできません。 | | `temDST_IS_SRC` | トランザクションで宛先アドレスがトランザクションの送信元`Account`として誤って指定されていました。これにはトラストライン（支払先アドレスは`LimitAmount`の`issuer`フィールド）とPayment Channel（支払先アドレスは`Destination`フィールド）などがあります。 | diff --git a/@i18n/ja/docs/references/protocol/transactions/types/checkcreate.md b/@i18n/ja/docs/references/protocol/transactions/types/checkcreate.md index ec383e8e21..2f290a61aa 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/checkcreate.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/checkcreate.md @@ -33,7 +33,7 @@ _（[Checks Amendment][]が必要です）_ | フィールド | JSONの型 | [内部の型][] | 説明 | |:-----------------|:--------------------|:------------------|:----------------| -| `Destination` | 文字列 | AccountID | Checkを換金できる[アカウント](../../../../concepts/accounts/accounts.md)の一意アドレス。 | +| `Destination` | 文字列 | AccountID | Checkを換金できる[アカウント](../../../../concepts/accounts/index.md)の一意アドレス。 | | `SendMax` | [通貨額][] | Amount | Checkで送金元から引き落とすことができる送金元通貨の最大額（XRP以外の通貨の[送金手数料](../../../../concepts/tokens/transfer-fees.md)を含む）。Checkは同一通貨の送金先にのみ入金可能です（XRP以外の通貨の場合は同一イシュアーから）。XRP以外の金額の場合、入れ子フィールドの名前にはアルファベットの小文字のみ使用してください。 | | `DestinationTag` | 数値 | UInt32 | _（省略可）_ Checkの理由を明確にする任意のタグ、または支払先となる、ホスティングされている受取人。 | | `Expiration` | 数値 | UInt32 | _（省略可）_ Checkが無効になる時刻（[Rippleエポック以降の経過秒数][]）。 | @@ -43,7 +43,7 @@ _（[Checks Amendment][]が必要です）_ - `Destination`アカウントがCheckの着信をブロックしている場合、トランザクションは結果コード`tecNO_PERMISSION`で失敗します。 _([DisallowIncoming amendment][] {% not-enabled /%} が必要です。)_ - `Destination`がトランザクションの送信者である場合、トランザクションは結果コード`temREDUNDANT`で失敗します。 -- `Destination`[アカウント](../../../../concepts/accounts/accounts.md)がレジャーに存在していない場合、トランザクションは結果コード`tecNO_DST`で失敗します。 +- `Destination`[アカウント](../../../../concepts/accounts/index.md)がレジャーに存在していない場合、トランザクションは結果コード`tecNO_DST`で失敗します。 - `Destination`アカウントでRequireDestフラグが有効であるが、トランザクションに`DestinationTag`フィールドが含まれていない場合、トランザクションは結果コード`tecDST_TAG_NEEDED`で失敗します。 - `SendMax`に[凍結](../../../../concepts/tokens/fungible-tokens/freezes.md)されているトークンが指定されている場合、トランザクションは結果コード`tecFROZEN`で失敗します。 - トランザクションの`Expiration`が過去の日時である場合、トランザクションは結果コード`tecEXPIRED`で失敗します。 diff --git a/@i18n/ja/docs/references/protocol/transactions/types/payment.md b/@i18n/ja/docs/references/protocol/transactions/types/payment.md index e5f42398ba..e6ea413e84 100644 --- a/@i18n/ja/docs/references/protocol/transactions/types/payment.md +++ b/@i18n/ja/docs/references/protocol/transactions/types/payment.md @@ -82,7 +82,7 @@ Paymentトランザクションタイプは、いくつかの異なるタイプ Payment型のトランザクションでは、資金供給のないアドレスに対して十分なXRPを送金することで、XRP Ledgerに新規のアカウントを作成できます。資金供給のないアドレスに対するその他のトランザクションは、常に失敗します。 -詳細は、[アカウント](../../../../concepts/accounts/accounts.md#アカウントの作成)を参照してください。 +詳細は、[アカウント](../../../../concepts/accounts/index.md#アカウントの作成)を参照してください。 ## パス diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md index d43f1331fd..705e66f9ef 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md +++ b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md @@ -9,7 +9,7 @@ labels: --- # マスターキーペアの無効化 -このページでは、[アカウント](../../../concepts/accounts/accounts.md)のアドレスに数学的に関連付けられた[マスターキーペア](../../../concepts/accounts/cryptographic-keys.md)を無効化する方法について説明します。あなたのアカウントのマスターキーペアが漏洩した可能性がある場合、または[マルチシグ](../../../concepts/accounts/multi-signing.md)をあなたのアカウントからトランザクションを送信する _唯一_ の方法としたい場合、これを行う必要があります。 +このページでは、[アカウント](../../../concepts/accounts/index.md)のアドレスに数学的に関連付けられた[マスターキーペア](../../../concepts/accounts/cryptographic-keys.md)を無効化する方法について説明します。あなたのアカウントのマスターキーペアが漏洩した可能性がある場合、または[マルチシグ](../../../concepts/accounts/multi-signing.md)をあなたのアカウントからトランザクションを送信する _唯一_ の方法としたい場合、これを行う必要があります。 **注意:** マスターキーペアを無効にすると、[トランザクションの承認](../../../concepts/transactions/index.md#トランザクションの承認)の方法の1つが削除されます。マスターキーペアを無効にする前に、レギュラーキーやマルチ・サインなど、他のトランザクションの承認方法のいずれかを使用できることを確認する必要があります。(例えば、[レギュラーキーペアを割り当てた場合](assign-a-regular-key-pair.md)は、そのレギュラーキーで正常にトランザクションを送信できることを確認してください)。XRP Ledgerは分散型であるため、残りの取引承認方法を使用できない場合、誰もあなたのアカウントへのアクセスを回復することができません。 @@ -20,7 +20,7 @@ labels: アカウントのマスターキーペアを無効にするには、次の前提条件を満たしている必要があります。 -- XRP Ledger[アカウント](../../../concepts/accounts/accounts.md)を持ち、そのアカウントからマスターキーペアを用いてトランザクションの署名と提出ができることが必要です。[安全な署名の設定](../../../concepts/transactions/secure-signing.md) を参照してください。これには2つの一般的な方法があります。 +- XRP Ledger[アカウント](../../../concepts/accounts/index.md)を持ち、そのアカウントからマスターキーペアを用いてトランザクションの署名と提出ができることが必要です。[安全な署名の設定](../../../concepts/transactions/secure-signing.md) を参照してください。これには2つの一般的な方法があります。 - アカウントのマスターシード値を知っている。シード値は一般的に `sn3nxiW7v8KXzPzAqzyHXbSSKNuN9`のような "s" で始まる [base58][] 値で表されます。 - あるいは、シード値を知る必要がなく、安全に保存する[専用の署名デバイス](../../../concepts/transactions/secure-signing.md#専用の署名デバイスを使用する) を使用します - あなたのアカウントには、マスターキーペア以外のトランザクションを認証する方法が少なくとも1つ必要です。つまり、以下のいずれか、または両方を行う必要があります。 diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md index 95f4a3a2c7..96286a931b 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md +++ b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md @@ -9,7 +9,7 @@ labels: --- # オフラインでのアカウント設定のチュートリアル -きわめて安全な[署名構成](../../../concepts/transactions/secure-signing.md)では、XRP Ledger[アカウント](../../../concepts/accounts/accounts.md)の[暗号鍵](../../../concepts/accounts/cryptographic-keys.md)をオフラインの物理的に隔離されたマシンに安全に保管します。この構成を設定すると、さまざまなトランザクションに署名して、署名済みトランザクションのみをオンラインコンピューターに転送し、秘密鍵をオンラインにいる不正使用者に見せることなくそれらのトランザクションをXRP Ledgerネットワークに送信できます。 +きわめて安全な[署名構成](../../../concepts/transactions/secure-signing.md)では、XRP Ledger[アカウント](../../../concepts/accounts/index.md)の[暗号鍵](../../../concepts/accounts/cryptographic-keys.md)をオフラインの物理的に隔離されたマシンに安全に保管します。この構成を設定すると、さまざまなトランザクションに署名して、署名済みトランザクションのみをオンラインコンピューターに転送し、秘密鍵をオンラインにいる不正使用者に見せることなくそれらのトランザクションをXRP Ledgerネットワークに送信できます。 **注意:** オフラインマシンを保護するためには、適切な運用セキュリティ対策が必要です。例えば、オフラインマシンは信頼できない人がアクセスできない場所に物理的に設置する必要があり、信頼できるオペレーターはマシンに悪用されたソフトウェアを転送しないように注意する必要があります。（例えば、ネットワークに接続されたコンピューターに接続したことがあるUSBドライブは使用してはいけません。） @@ -70,7 +70,7 @@ Loading: "/etc/opt/ripple/rippled.cfg" 次の値をメモします。 -- **`account_id`**: これはキーペアに関連付けられているアドレスです。このアドレスは、XRPを供給（このプロセスの先で実行）した後に、XRP Ledgerでの **[アカウント](../../../concepts/accounts/accounts.md)アドレス**になります。`account_id`は公開しても安全です。 +- **`account_id`**: これはキーペアに関連付けられているアドレスです。このアドレスは、XRPを供給（このプロセスの先で実行）した後に、XRP Ledgerでの **[アカウント](../../../concepts/accounts/index.md)アドレス**になります。`account_id`は公開しても安全です。 - **`master_seed`**: これはキーペアの秘密シード値です。この値は、アカウントからのトランザクションに署名する際に使用します。最高レベルのセキュリティを実現するために、この値をオフラインマシンのディスクに書き込む前に暗号化してください。暗号化キーとして、人間のオペレーターが覚えやすい安全なパスフレーズや、物理的に安全な場所に書き留めたパスフレーズを使います。例えば、適切な重さのサイコロを使用して作成する[ダイスウェアパスフレーズ](https://theworld.com/~reinhold/diceware.html)などがあります。第2の要素として物理セキュリティキーを使用することもできます。この段階で取る対策の程度はご自身で決めてください。 - **`key_type`**: これは、このキーペアに使用する暗号化アルゴリズムです。有効なトランザクションに署名するには、どのようなタイプのキーペアを所有しているかを知る必要があります。デフォルトは`secp256k1`です。 @@ -80,7 +80,7 @@ Loading: "/etc/opt/ripple/rippled.cfg" ### 3.新しいアドレスへの資金の供給 -オンラインマシンから、ステップ1でメモした**アカウントアドレス** に十分なXRPを送金します。詳細は、[アカウントの作成](../../../concepts/accounts/accounts.md#アカウントの作成)を参照してください。 +オンラインマシンから、ステップ1でメモした**アカウントアドレス** に十分なXRPを送金します。詳細は、[アカウントの作成](../../../concepts/accounts/index.md#アカウントの作成)を参照してください。 **ヒント:** テストの目的で、[Testnet Faucet](/resources/dev-tools/xrp-faucets)を使用して、テスト用のXRPが入った新しいアカウントを取得できます。そのアカウントを使用して、オフラインで生成されたアドレスに資金を供給します。 @@ -325,7 +325,7 @@ Loading: "/etc/opt/ripple/rippled.cfg" ## 関連項目 - **コンセプト:** - - [アカウント](../../../concepts/accounts/accounts.md) + - [アカウント](../../../concepts/accounts/index.md) - [暗号鍵](../../../concepts/accounts/cryptographic-keys.md) - **チュートリアル:** - [安全な署名の設定](../../../concepts/transactions/secure-signing.md) diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md index 35c8fb462f..a89ac6c53f 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md +++ b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md @@ -79,7 +79,7 @@ Content-Type: application/json ## 関連項目 - **コンセプト:** - - [アカウント](../../../concepts/accounts/accounts.md) + - [アカウント](../../../concepts/accounts/index.md) - [送信元と宛先タグ](../../../concepts/transactions/source-and-destination-tags.md) - [トランザクションコスト](../../../concepts/transactions/transaction-cost.md) - [支払いタイプ](../../../concepts/payment-types/index.md) diff --git a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md index 1853502bb5..999617e6b1 100644 --- a/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md +++ b/@i18n/ja/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md @@ -8,14 +8,14 @@ labels: --- # マルチシグの設定 -[マルチシグ](../../../concepts/accounts/multi-signing.md)は、XRP Ledgerの[トランザクション](../../../concepts/transactions/index.md)を承認する3種類の方法の1つです。マルチシグの他に[レギュラーキーとマスターキー](../../../concepts/accounts/cryptographic-keys.md)で署名する方法があります。3種類のトランザクション承認方法を自由に組み合わせて使用できるように[アドレス](../../../concepts/accounts/accounts.md)を設定できます。 +[マルチシグ](../../../concepts/accounts/multi-signing.md)は、XRP Ledgerの[トランザクション](../../../concepts/transactions/index.md)を承認する3種類の方法の1つです。マルチシグの他に[レギュラーキーとマスターキー](../../../concepts/accounts/cryptographic-keys.md)で署名する方法があります。3種類のトランザクション承認方法を自由に組み合わせて使用できるように[アドレス](../../../concepts/accounts/index.md)を設定できます。 このチュートリアルでは、アドレスのマルチシグを有効にする方法を説明します。 ## 前提条件 -- トランザクションを送信するための十分なXRPが供給されていて、新しい署名者リストの[必要準備金](../../../concepts/accounts/reserves.md)を満たしている資金供給のあるXRP Ledger[アドレス](../../../concepts/accounts/accounts.md)が必要です。 +- トランザクションを送信するための十分なXRPが供給されていて、新しい署名者リストの[必要準備金](../../../concepts/accounts/reserves.md)を満たしている資金供給のあるXRP Ledger[アドレス](../../../concepts/accounts/index.md)が必要です。 - [MultiSignReserve Amendment][]が有効な場合、マルチシグを使用するには、使用する署名と署名者の数に関わらず、アカウントの準備金として2 XRPが必要です。（MultiSignReserve Amendmentは**2019年4月7日**以降、本番環境のXRP Ledgerで有効になっています。) diff --git a/@i18n/ja/docs/tutorials/tasks/send-xrp.md b/@i18n/ja/docs/tutorials/tasks/send-xrp.md index 0285fa822b..7865095e2e 100644 --- a/@i18n/ja/docs/tutorials/tasks/send-xrp.md +++ b/@i18n/ja/docs/tutorials/tasks/send-xrp.md @@ -287,7 +287,7 @@ System.out.println(generationResult.seed()); // Example: sp6JS7f14BuwFY8Mw6bTtLK **警告:** ローカルマシンで安全な方法で生成したアドレスとシークレットのみを使用してください。別のコンピューターでアドレスとシークレットを生成して、ネットワーク経由でそれらを自分に送信した場合は、ネットワーク上の他の人がその情報を見ることができる可能性があります。その情報見ることができる人は、あなたと同じようにあなたのXRPを操作できます。また、Test Netと本番で同じアドレスを使用しないことも推奨します。指定したパラメーターによっては、一方のネットワークに向けて作成したトランザクションが、もう一方のネットワークでも実行可能になるおそれがあるためです。 -アドレスとシークレットを生成しても、直接XRPを入手できるわけではありません。単に乱数を選択しているだけです。また、そのアドレスでXRPを受け取って[アカウントに資金供給](../../concepts/accounts/accounts.md#アカウントの作成)する必要があります。XRPを取得する方法として最も一般的なのは、取引所から購入し、所有しているアドレスに入れる方法です。詳細は、[XRP Overview](/about/xrp)を参照してください。 +アドレスとシークレットを生成しても、直接XRPを入手できるわけではありません。単に乱数を選択しているだけです。また、そのアドレスでXRPを受け取って[アカウントに資金供給](../../concepts/accounts/index.md#アカウントの作成)する必要があります。XRPを取得する方法として最も一般的なのは、取引所から購入し、所有しているアドレスに入れる方法です。詳細は、[XRP Overview](/about/xrp)を参照してください。 ### 本番XRP Ledgerへの接続 diff --git a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md b/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md index 99b7db86e1..b9b32907ce 100644 --- a/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md +++ b/@i18n/ja/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md @@ -11,7 +11,7 @@ labels: Payment Channelは、少額の単位に分割可能な「非同期」のXRPペイメントを送信し、後日決済する高度な機能です。このチュートリアルでは、全体的な[Payment Channel](../../../../concepts/payment-types/payment-channels.md)の使用方法を、ローカル`rippled`サーバーの[JSON-RPC API](../../../../references/http-websocket-apis/index.md)を使用する例を使って説明します。 -このチュートリアルを進めるにあたって[資金供給されているXRP Ledgerアカウント](../../../../concepts/accounts/accounts.md)を所有するユーザーが2名いれば理想的です。ただし、2つのXRP Ledgerアドレスを管理する1名のユーザーとしてこのチュートリアルを進めることもできます。 +このチュートリアルを進めるにあたって[資金供給されているXRP Ledgerアカウント](../../../../concepts/accounts/index.md)を所有するユーザーが2名いれば理想的です。ただし、2つのXRP Ledgerアドレスを管理する1名のユーザーとしてこのチュートリアルを進めることもできます。 ## サンプルの値 diff --git a/@i18n/ja/docs/use-cases/defi/list-xrp-as-an-exchange.md b/@i18n/ja/docs/use-cases/defi/list-xrp-as-an-exchange.md index db9229ac16..247bd89b9f 100644 --- a/@i18n/ja/docs/use-cases/defi/list-xrp-as-an-exchange.md +++ b/@i18n/ja/docs/use-cases/defi/list-xrp-as-an-exchange.md @@ -97,7 +97,7 @@ Rippleが推奨するベストプラクティスに従い、Alpha Exchangeは、 * [発行アドレスと運用アドレス](../../concepts/accounts/account-types.md) -* [アカウントの作成](../../concepts/accounts/accounts.md#アカウントの作成) +* [アカウントの作成](../../concepts/accounts/index.md#アカウントの作成) * [準備金](../../concepts/accounts/reserves.md) diff --git a/@i18n/ja/docs/use-cases/payments/peer-to-peer-payments-uc.md b/@i18n/ja/docs/use-cases/payments/peer-to-peer-payments-uc.md index ad55d98dfc..c40cf40219 100644 --- a/@i18n/ja/docs/use-cases/payments/peer-to-peer-payments-uc.md +++ b/@i18n/ja/docs/use-cases/payments/peer-to-peer-payments-uc.md @@ -20,7 +20,7 @@ XRP Ledgerを使用して直接支払いを処理する前に、使用するウ アカウントを作成する前に、XRP Ledgerのどのネットワークを使用するかを決定する必要があります。異なるユースケースのために複数のネットワークがありますが、ネイティブのXRPトランザクションは`Mainnet`でしか起こりません。[パラレルネットワーク](../../concepts/networks-and-servers/parallel-networks.md)をご覧ください。 -一般に公開されているウォレットのほとんどは、アカウントを作成する機能を提供しており、公開鍵と秘密鍵を生成することができます。そうでない場合でも、数学的に有効である限り、自分でアカウントを作成することができます。[アカウントの作成](../../concepts/accounts/accounts.md#creating-accounts)をご覧ください。 +一般に公開されているウォレットのほとんどは、アカウントを作成する機能を提供しており、公開鍵と秘密鍵を生成することができます。そうでない場合でも、数学的に有効である限り、自分でアカウントを作成することができます。[アカウントの作成](../../concepts/accounts/index.md#creating-accounts)をご覧ください。 ## アカウントを探す diff --git a/@i18n/ja/resources/known-amendments.md b/@i18n/ja/resources/known-amendments.md index 9b7e95ffe5..b5c24ae317 100644 --- a/@i18n/ja/resources/known-amendments.md +++ b/@i18n/ja/resources/known-amendments.md @@ -281,7 +281,7 @@ Clawbackはデフォルトでは無効になっています。Clawbackを使用 | デフォルトの投票(最新の安定版) | はい | | Amendment前の機能は廃止? | いいえ | -[アカウント](../docs/concepts/accounts/accounts.md)を削除できるようになります。 +[アカウント](../docs/concepts/accounts/index.md)を削除できるようになります。 この修正を適用しない場合、新しいアカウントは`Sequence`番号が必ず1で始まります。また、レジャーの状態データからアカウントを削除できません。 @@ -661,7 +661,7 @@ fix1623 Amendmentは、固定金額の[CheckCashトランザクション][]（`A | デフォルトの投票(最新の安定版) | はい | | Amendment前の機能は廃止? | いいえ | -Checksトランザクションがアカウントのメタデータに影響を及ぼす方法を変更し、Checksが受信アカウントの[アカウント](../docs/concepts/accounts/accounts.md)履歴に適切に追加されるようにします。（具体的には、受信アカウントの[AccountRootオブジェクト](../docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md)の`PreviousTxnID`フィールドと`PreviousTxnLedgerSeq`フィールドを更新します。これは、アカウントと、アカウントが所有するオブジェクトに影響を及ぼしたトランザクションの「スレッド」を追跡するために使用できます。） +Checksトランザクションがアカウントのメタデータに影響を及ぼす方法を変更し、Checksが受信アカウントの[アカウント](../docs/concepts/accounts/index.md)履歴に適切に追加されるようにします。（具体的には、受信アカウントの[AccountRootオブジェクト](../docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md)の`PreviousTxnID`フィールドと`PreviousTxnLedgerSeq`フィールドを更新します。これは、アカウントと、アカウントが所有するオブジェクトに影響を及ぼしたトランザクションの「スレッド」を追跡するために使用できます。） この修正を適用しない場合、Checksトランザクション（[CheckCreate][]、[CheckCash][]、および[CheckCancel][]）は送信者のアカウント履歴のみを更新します。この修正を適用した場合、これらのトランザクションは、送信アカウントにも受信アカウントにも影響します。この修正は、[Checks Amendment](#checks)も有効でないかぎり効果がありません。 diff --git a/docs/_snippets/data_types/account_sequence.md b/docs/_snippets/data_types/account_sequence.md index 45fcff9298..29da002553 100644 --- a/docs/_snippets/data_types/account_sequence.md +++ b/docs/_snippets/data_types/account_sequence.md @@ -1,6 +1,6 @@ A sequence number is a 32-bit unsigned integer that is used to make sure transactions from a given sender execute only once each, and in the correct order. -Every [account in the XRP Ledger](../../concepts/accounts/accounts.md) has a sequence number in its `Sequence` field, which increases by 1 whenever that account sends a transaction and that transaction gets included in a [validated ledger](../../concepts/ledgers/index.md). Each [transaction](../../concepts/transactions/index.md) also has a sequence number in its `Sequence` field, which must match the account's current sequence number when the transaction executes. For each account, each sequence number can only be used once, in numerical order. +Every [account in the XRP Ledger](../../concepts/accounts/index.md) has a sequence number in its `Sequence` field, which increases by 1 whenever that account sends a transaction and that transaction gets included in a [validated ledger](../../concepts/ledgers/index.md). Each [transaction](../../concepts/transactions/index.md) also has a sequence number in its `Sequence` field, which must match the account's current sequence number when the transaction executes. For each account, each sequence number can only be used once, in numerical order. [Tickets](../../concepts/accounts/tickets.md) make some exceptions from these rules so that it is possible to send transactions out of the normal order. Tickets represent sequence numbers reserved for later use; a transaction can use a Ticket instead of a normal sequence number. diff --git a/docs/concepts/accounts/account-types.md b/docs/concepts/accounts/account-types.md index 78dd4c2988..7e58a2d915 100644 --- a/docs/concepts/accounts/account-types.md +++ b/docs/concepts/accounts/account-types.md @@ -71,7 +71,7 @@ If a standby address is compromised, the consequences are like an operational ad ## See Also - **Concepts:** - - [Accounts](accounts.md) + - [Accounts](index.md) - [Cryptographic Keys](cryptographic-keys.md) - **Tutorials:** - [Assign a Regular Key Pair](../../tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md) diff --git a/docs/concepts/accounts/addresses.md b/docs/concepts/accounts/addresses.md index 1c4043882e..e9b7d8a432 100644 --- a/docs/concepts/accounts/addresses.md +++ b/docs/concepts/accounts/addresses.md @@ -10,7 +10,7 @@ labels: {% partial file="/docs/_snippets/data_types/address.md" /%} -Any valid address can [become an account in the XRP Ledger](accounts.md#creating-accounts) by being funded. You can also use an address that has not been funded to represent a [regular key](cryptographic-keys.md) or a member of a [signer list](multi-signing.md). Only a funded account can be the sender of a transaction. +Any valid address can [become an account in the XRP Ledger](index.md#creating-accounts) by being funded. You can also use an address that has not been funded to represent a [regular key](cryptographic-keys.md) or a member of a [signer list](multi-signing.md). Only a funded account can be the sender of a transaction. Creating a valid address is a strictly mathematical task starting with a key pair. You can generate a key pair and calculate its address entirely offline without communicating to the XRP Ledger or any other party. The conversion from a public key to an address involves a one-way hash function, so it is possible to confirm that a public key matches an address but it is impossible to derive the public key from the address alone. (This is part of the reason why signed transactions include the public key _and_ the address of the sender.) diff --git a/docs/concepts/accounts/cryptographic-keys.md b/docs/concepts/accounts/cryptographic-keys.md index d9d707c92e..61471905e9 100644 --- a/docs/concepts/accounts/cryptographic-keys.md +++ b/docs/concepts/accounts/cryptographic-keys.md @@ -62,14 +62,14 @@ Transactions in the XRP Ledger must include the public keys so that the network ### Account ID and Address -The **Account ID** is the core identifier for an [account](accounts.md) or a key pair. It is derived from the public key. In the XRP Ledger protocol, the Account ID is 20 bytes of binary data. Most XRP Ledger APIs represent the Account ID as an address, in one of two formats: +The **Account ID** is the core identifier for an [account](index.md) or a key pair. It is derived from the public key. In the XRP Ledger protocol, the Account ID is 20 bytes of binary data. Most XRP Ledger APIs represent the Account ID as an address, in one of two formats: - A "classic address" writes an Account ID in [base58][] with a checksum. In a [wallet_propose method][] response, this is the `account_id` value. - An "X-Address" combines an Account ID _and_ a [Destination Tag](../transactions/source-and-destination-tags.md) and writes the combined value in [base58][] with a checksum. The checksum in both formats is there so that small changes result in an invalid address, instead of changing it to refer to a different, but still potentially valid, account. This way, if you make a typo or a transmission error occurs, you don't send money to the wrong place. -It is important to know that not all Account IDs (or addresses) refer to accounts in the ledger. Deriving keys and addresses is purely a mathematical operation. For an account to have a record in the XRP Ledger, it must [receive a payment of XRP](accounts.md#creating-accounts) that funds its [reserve requirement](reserves.md). An account cannot send any transactions until after it has been funded. +It is important to know that not all Account IDs (or addresses) refer to accounts in the ledger. Deriving keys and addresses is purely a mathematical operation. For an account to have a record in the XRP Ledger, it must [receive a payment of XRP](index.md#creating-accounts) that funds its [reserve requirement](reserves.md). An account cannot send any transactions until after it has been funded. Even if an Account ID or address does not refer to a funded account, you _can_ use that Account ID or address to represent a [regular key pair](#regular-key-pair) or a [member of a signer list](multi-signing.md). diff --git a/docs/concepts/accounts/deleting-accounts.md b/docs/concepts/accounts/deleting-accounts.md index 38b7acaf18..28c2f8c066 100644 --- a/docs/concepts/accounts/deleting-accounts.md +++ b/docs/concepts/accounts/deleting-accounts.md @@ -12,7 +12,7 @@ The owner of an account can send an [AccountDelete transaction][] to deletes the Some types of associated ledger entries block an account from being deleted. For example, the issuer of a fungible token can't be deleted while anyone holds a nonzero balance of that token. -After an account has been deleted, it can be re-created in the ledger through the normal method of [creating accounts](accounts.md#creating-accounts). An account that has been deleted and re-created is no different than an account that has been created for the first time. +After an account has been deleted, it can be re-created in the ledger through the normal method of [creating accounts](index.md#creating-accounts). An account that has been deleted and re-created is no different than an account that has been created for the first time. ## Requirements diff --git a/docs/concepts/accounts/depositauth.md b/docs/concepts/accounts/depositauth.md index d64b88d52b..b097e96b6f 100644 --- a/docs/concepts/accounts/depositauth.md +++ b/docs/concepts/accounts/depositauth.md @@ -11,7 +11,7 @@ labels: _(Added by the [DepositAuth amendment][].)_ -Deposit Authorization is an optional [account](accounts.md) setting in the XRP Ledger. If enabled, Deposit Authorization blocks all transfers from strangers, including transfers of XRP and [tokens](../tokens/index.md). An account with Deposit Authorization can only receive value in two ways: +Deposit Authorization is an optional [account](index.md) setting in the XRP Ledger. If enabled, Deposit Authorization blocks all transfers from strangers, including transfers of XRP and [tokens](../tokens/index.md). An account with Deposit Authorization can only receive value in two ways: - From accounts it has [preauthorized](#preauthorization). - By sending a transaction to receive the funds. For example, an account with Deposit Authorization could finish an [Escrow](../payment-types/escrow.md) that was initiated by a stranger. diff --git a/docs/concepts/consensus-protocol/consensus-structure.md b/docs/concepts/consensus-protocol/consensus-structure.md index 4ae8e376c4..7a92e06d0e 100644 --- a/docs/concepts/consensus-protocol/consensus-structure.md +++ b/docs/concepts/consensus-protocol/consensus-structure.md @@ -19,7 +19,7 @@ When building applications on the XRP Ledger, it is important to understand this The peer-to-peer XRP Ledger network provides a worldwide, shared ledger, which gives applications authoritative information about the state of its contents. This state information includes: -- settings for each [account](../accounts/accounts.md) +- settings for each [account](../accounts/index.md) - balances of XRP and [tokens](../tokens/index.md) - offers in the distributed exchange - network settings, such as [transaction costs](../transactions/transaction-cost.md) and [reserve](../accounts/reserves.md) amounts diff --git a/docs/concepts/consensus-protocol/invariant-checking.md b/docs/concepts/consensus-protocol/invariant-checking.md index 329bb885d1..9dff55c3aa 100644 --- a/docs/concepts/consensus-protocol/invariant-checking.md +++ b/docs/concepts/consensus-protocol/invariant-checking.md @@ -90,7 +90,7 @@ The XRP Ledger checks all the following invariants on each transaction: ### Account Roots Not Deleted - **Invariant Condition(s):** - - An [account](../accounts/accounts.md) cannot be deleted from the ledger except by an [AccountDelete transaction][]. + - An [account](../accounts/index.md) cannot be deleted from the ledger except by an [AccountDelete transaction][]. - A successful AccountDelete transaction always deletes exactly 1 account. @@ -129,7 +129,7 @@ The XRP Ledger checks all the following invariants on each transaction: - **Invariant Condition(s):** - A new [account root](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md) must be the consequence of a payment. - A new account root must have the right starting [sequence](../../references/protocol/data-types/basic-data-types.md#account-sequence). - - A transaction must not create more than one new [account](../accounts/accounts.md). + - A transaction must not create more than one new [account](../accounts/index.md). ### ValidNFTokenPage diff --git a/docs/concepts/tokens/decentralized-exchange/index.md b/docs/concepts/tokens/decentralized-exchange/index.md index 1d96c0de79..0e3df116dd 100644 --- a/docs/concepts/tokens/decentralized-exchange/index.md +++ b/docs/concepts/tokens/decentralized-exchange/index.md @@ -53,7 +53,7 @@ Because trades are only executed each time a new ledger closes (approximately ev The XRP Ledger does not natively represent concepts such as market orders, stop orders, or trading on leverage. Some of these may be possible with creative use of custom tokens and Offer properties. -As a decentralized system, the XRP Ledger does not have any information on the actual people and organizations behind the [accounts](../../accounts/accounts.md) involved in trading. The ledger itself cannot implement restrictions around who can or cannot participate in trading, and users and issuers must take care to follow any relevant laws to regulate trading tokens that represent various types of underlying assets. Features such as [freezes](../fungible-tokens/freezes.md) and [authorized trust lines](../fungible-tokens/authorized-trust-lines.md) are intended to help issuers comply with relevant laws and regulations. +As a decentralized system, the XRP Ledger does not have any information on the actual people and organizations behind the [accounts](../../accounts/index.md) involved in trading. The ledger itself cannot implement restrictions around who can or cannot participate in trading, and users and issuers must take care to follow any relevant laws to regulate trading tokens that represent various types of underlying assets. Features such as [freezes](../fungible-tokens/freezes.md) and [authorized trust lines](../fungible-tokens/authorized-trust-lines.md) are intended to help issuers comply with relevant laws and regulations. ## See Also diff --git a/docs/concepts/tokens/fungible-tokens/index.md b/docs/concepts/tokens/fungible-tokens/index.md index 82383b2ec1..a6a2434974 100644 --- a/docs/concepts/tokens/fungible-tokens/index.md +++ b/docs/concepts/tokens/fungible-tokens/index.md @@ -18,7 +18,7 @@ Trust lines are structures in the XRP Ledger for holding fungible [tokens](../in Each "trust line" is a _bidirectional_ relationship consisting of: -- The identifiers for the two [accounts](../../accounts/accounts.md) that the trust line connects. +- The identifiers for the two [accounts](../../accounts/index.md) that the trust line connects. - A single, shared balance, which is positive from the perspective of one account and negative from the other perspective. - The account with a negative balance is generally considered the "issuer" of the tokens. However, in the [APIs](../../../references/http-websocket-apis/index.md), the name `issuer` can refer to either side. - Various settings and metadata. _Each_ of the two accounts can control its own settings on the trust line. diff --git a/docs/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md b/docs/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md index 775448fe03..c4cedc3c00 100644 --- a/docs/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md +++ b/docs/concepts/tokens/nfts/guaranteeing-a-fixed-supply.md @@ -12,7 +12,7 @@ For some projects, you might want to guarantee that no more than a fixed number To guarantee a fixed number of NFTs: -1. Create and fund a new account, the _Issuer_. This account is the issuer of the tokens within the collection. See [Creating Accounts](../../accounts/accounts.md#creating-accounts). +1. Create and fund a new account, the _Issuer_. This account is the issuer of the tokens within the collection. See [Creating Accounts](../../accounts/index.md#creating-accounts). 1. Use `AccountSet` to assign your operational wallet as an authorized minter for the issuer. See [Authorizing Another Account to Mint Your NFTs](authorizing-another-minter.md). 1. Use your operational account to mint the tokens using `NFTokenMint`. The operational wallet holds all of the tokens minted for the Issuer. See [Batch Minting](batch-minting.md). 1. Use `AccountSet` to remove your operational wallet as an authorized minter for the Issuer. 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 b8bd41ceae..a806aad71d 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/accounts.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/transaction-results.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 @@ -223,7 +223,7 @@ XRP amounts are tracked in the `Balance` field of `AccountRoot` objects. (XRP ca You should always use [the `delivered_amount` field](../../payment-types/partial-payments.md#the-delivered_amount-field) to see how much a payment delivered. -If the payment contains a `CreatedNode` with `"LedgerEntryType": "AccountRoot"`, that means the payment [funded a new account](../../accounts/accounts.md#creating-accounts) in the ledger. +If the payment contains a `CreatedNode` with `"LedgerEntryType": "AccountRoot"`, that means the payment [funded a new account](../../accounts/index.md#creating-accounts) in the ledger. #### Token Payments diff --git a/docs/concepts/transactions/source-and-destination-tags.md b/docs/concepts/transactions/source-and-destination-tags.md index 661c09bbb7..c5866c0c02 100644 --- a/docs/concepts/transactions/source-and-destination-tags.md +++ b/docs/concepts/transactions/source-and-destination-tags.md @@ -22,7 +22,7 @@ The practice of giving customers the ability to send and receive transactions fr ## Rationale -In other distributed ledgers, it is common to use different deposit addresses for each customer. In the XRP Ledger, an address must be a funded, permanent [account](../accounts/accounts.md) to receive payments. Using this approach in the XRP Ledger wastefully consumes resources of all servers in the network, and is costly because the [reserve](../accounts/reserves.md) amount must be set aside indefinitely for each address. +In other distributed ledgers, it is common to use different deposit addresses for each customer. In the XRP Ledger, an address must be a funded, permanent [account](../accounts/index.md) to receive payments. Using this approach in the XRP Ledger wastefully consumes resources of all servers in the network, and is costly because the [reserve](../accounts/reserves.md) amount must be set aside indefinitely for each address. Source and destination tags provide a more lightweight way to map deposits and payments to individual customers. diff --git a/docs/introduction/transactions-and-requests.md b/docs/introduction/transactions-and-requests.md index 75cd406b47..0ee72a69fc 100644 --- a/docs/introduction/transactions-and-requests.md +++ b/docs/introduction/transactions-and-requests.md @@ -110,6 +110,6 @@ The request returns a wealth of information. Here is an example response for an } } ``` -For information on the fields in an Account record, see [Accounts](../concepts/accounts/accounts.md). +For information on the fields in an Account record, see [Accounts](../concepts/accounts/index.md). Next: [Software Ecosystem](software-ecosystem.md) diff --git a/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md b/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md index 3a38c1ea7c..b040389437 100644 --- a/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md +++ b/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md @@ -10,7 +10,7 @@ labels: # wallet_propose [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") -Use the `wallet_propose` method to generate a key pair and XRP Ledger address. This command only generates key and address values, and does not affect the XRP Ledger itself in any way. To become a funded address stored in the ledger, the address must [receive a Payment transaction](../../../../concepts/accounts/accounts.md#creating-accounts) that provides enough XRP to meet the [reserve requirement](../../../../concepts/accounts/reserves.md). +Use the `wallet_propose` method to generate a key pair and XRP Ledger address. This command only generates key and address values, and does not affect the XRP Ledger itself in any way. To become a funded address stored in the ledger, the address must [receive a Payment transaction](../../../../concepts/accounts/index.md#creating-accounts) that provides enough XRP to meet the [reserve requirement](../../../../concepts/accounts/reserves.md). *The `wallet_propose` method is an [admin method](../index.md) that cannot be run by unprivileged users!* (This command is restricted to protect against people sniffing network traffic for account secrets, since admin commands are not usually transmitted over the outside network.) diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md index 6642cbfce1..506b0f6039 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md @@ -9,7 +9,7 @@ labels: # account_offers [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") -The `account_offers` method retrieves a list of [offers](../../../../concepts/tokens/decentralized-exchange/offers.md) made by a given [account](../../../../concepts/accounts/accounts.md) that are outstanding as of a particular [ledger version](../../../../concepts/ledgers/index.md). +The `account_offers` method retrieves a list of [offers](../../../../concepts/tokens/decentralized-exchange/offers.md) made by a given [account](../../../../concepts/accounts/index.md) that are outstanding as of a particular [ledger version](../../../../concepts/ledgers/index.md). ## Request Format diff --git a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index 9dcb74e2cf..47df59075c 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 @@ -98,7 +98,7 @@ Each member of the `books` array, if provided, is an object with the following f |:-------------|:--------|:----------------------------------------------------| | `taker_gets` | Object | Specification of which currency the account taking the Offer would receive, as a [currency object with no amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | | `taker_pays` | Object | Specification of which currency the account taking the Offer would pay, as a [currency object with no amount](../../../protocol/data-types/currency-formats.md#specifying-without-amounts). | -| `taker` | String | Unique [account address](../../../../concepts/accounts/accounts.md) to use as a perspective for viewing offers, in the XRP Ledger's [base58][] format. (This affects the funding status and fees of [Offers](../../../../concepts/tokens/decentralized-exchange/offers.md).) | +| `taker` | String | Unique [account address](../../../../concepts/accounts/index.md) to use as a perspective for viewing offers, in the XRP Ledger's [base58][] format. (This affects the funding status and fees of [Offers](../../../../concepts/tokens/decentralized-exchange/offers.md).) | | `snapshot` | Boolean | _(Optional)_ If `true`, return the current state of the order book once when you subscribe before sending updates. The default is `false`. | | `both` | Boolean | _(Optional)_ If `true`, return both sides of the order book. The default is `false`. | diff --git a/docs/references/protocol/binary-format.md b/docs/references/protocol/binary-format.md index 89626c7e6b..fc1b9180c3 100644 --- a/docs/references/protocol/binary-format.md +++ b/docs/references/protocol/binary-format.md @@ -177,7 +177,7 @@ Transaction instructions may contain fields of any of the following types: | Type Name | Type Code | Bit Length | [Length-prefixed][]? | Description | |:--------------|:----------|:-----------|:---------------------|----------------| -| [AccountID][] | 8 | 160 | Yes | The unique identifier for an [account](../../concepts/accounts/accounts.md). | +| [AccountID][] | 8 | 160 | Yes | The unique identifier for an [account](../../concepts/accounts/index.md). | | [Amount][] | 6 | 64 or 384 | No | An amount of XRP or tokens. The length of the field is 64 bits for XRP or 384 bits (64+160+160) for tokens. | | [Blob][] | 7 | Variable | Yes | Arbitrary binary data. One important such field is `TxnSignature`, the signature that authorizes a transaction. | | [Hash128][] | 4 | 128 | No | A 128-bit arbitrary binary value. The only such field is `EmailHash`, which is intended to store the MD-5 hash of an account owner's email for purposes of fetching a [Gravatar](https://www.gravatar.com/). | @@ -210,7 +210,7 @@ In addition to all of the above field types, the following types may appear in o ### AccountID Fields [AccountID]: #accountid-fields -Fields of this type contain the 160-bit identifier for an XRP Ledger [account](../../concepts/accounts/accounts.md). In JSON, these fields are represented as [base58][] XRP Ledger "addresses", with additional checksum data so that typos are unlikely to result in valid addresses. (This encoding, sometimes called "Base58Check", prevents accidentally sending money to the wrong address.) The binary format for these fields does not contain any checksum data nor does it include the `0x00` "type prefix" used in [address base58 encoding](../../concepts/accounts/addresses.md#address-encoding). (However, since the binary format is used mostly for signed transactions, a typo or other error in transcribing a signed transaction would invalidate the signature, preventing it from sending money.) +Fields of this type contain the 160-bit identifier for an XRP Ledger [account](../../concepts/accounts/index.md). In JSON, these fields are represented as [base58][] XRP Ledger "addresses", with additional checksum data so that typos are unlikely to result in valid addresses. (This encoding, sometimes called "Base58Check", prevents accidentally sending money to the wrong address.) The binary format for these fields does not contain any checksum data nor does it include the `0x00` "type prefix" used in [address base58 encoding](../../concepts/accounts/addresses.md#address-encoding). (However, since the binary format is used mostly for signed transactions, a typo or other error in transcribing a signed transaction would invalidate the signature, preventing it from sending money.) AccountIDs that appear as stand-alone fields (such as `Account` and `Destination`) are [length-prefixed](#length-prefixing) despite being a fixed 160 bits in length. As a result, the length indicator for these fields is always the byte `0x14`. AccountIDs that appear as children of special fields ([Amount `issuer`][Amount] and [PathSet `account`][PathSet]) are _not_ length-prefixed. diff --git a/docs/references/protocol/data-types/base58-encodings.md b/docs/references/protocol/data-types/base58-encodings.md index f1caa3f255..8e0555946d 100644 --- a/docs/references/protocol/data-types/base58-encodings.md +++ b/docs/references/protocol/data-types/base58-encodings.md @@ -21,7 +21,7 @@ The following table lists all the encodings the XRP Ledger uses: ¹ Content size excludes the 1-byte type prefix. -[Account]: ../../../concepts/accounts/accounts.md +[Account]: ../../../concepts/accounts/index.md ## See Also diff --git a/docs/references/protocol/data-types/basic-data-types.md b/docs/references/protocol/data-types/basic-data-types.md index fb89b3effa..6f2da31ddd 100644 --- a/docs/references/protocol/data-types/basic-data-types.md +++ b/docs/references/protocol/data-types/basic-data-types.md @@ -8,7 +8,7 @@ seo: Different types of objects are uniquely identified in different ways: -[Accounts](../../../concepts/accounts/accounts.md) are identified by their [Address][], for example `"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"`. Addresses always start with "r". Many `rippled` methods also accept a hexadecimal representation. +[Accounts](../../../concepts/accounts/index.md) are identified by their [Address][], for example `"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"`. Addresses always start with "r". Many `rippled` methods also accept a hexadecimal representation. [Transactions](../transactions/index.md) are identified by a [Hash][] of the transaction's binary format. You can also identify a transaction by its sending account and [Sequence Number][]. diff --git a/docs/references/protocol/data-types/currency-formats.md b/docs/references/protocol/data-types/currency-formats.md index 82ce5d0259..96b94128f2 100644 --- a/docs/references/protocol/data-types/currency-formats.md +++ b/docs/references/protocol/data-types/currency-formats.md @@ -57,7 +57,7 @@ To specify an amount of a [(fungible) token](../../../concepts/tokens/index.md), |:-----------|:---------------------------|:-----------------------------------| | `currency` | String - [Currency Code][] | Arbitrary currency code for the token. Cannot be `XRP`. | | `value` | [String Number][] | Quoted decimal representation of the amount of the token. This can include scientific notation, such as `1.23e11` meaning 123,000,000,000. Both `e` and `E` may be used. This can be negative when displaying balances, but negative values are disallowed in other contexts such as specifying how much to send. | -| `issuer` | String | Generally, the [account](../../../concepts/accounts/accounts.md) that issues this token. In special cases, this can refer to the account that holds the token instead (for example, in a [Clawback](../transactions/types/clawback.md) transaction). | +| `issuer` | String | Generally, the [account](../../../concepts/accounts/index.md) that issues this token. In special cases, this can refer to the account that holds the token instead (for example, in a [Clawback](../transactions/types/clawback.md) transaction). | [String Number]: #string-numbers diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index 604a3db7e5..fab8b41e00 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -10,7 +10,7 @@ labels: # AccountRoot [[Source]](https://github.com/XRPLF/rippled/blob/264280edd79b7f764536e02459f33f66a59c0531/src/ripple/protocol/impl/LedgerFormats.cpp#L36-L60 "Source") -An `AccountRoot` ledger entry type describes a single [account](../../../../concepts/accounts/accounts.md), its settings, and XRP balance. +An `AccountRoot` ledger entry type describes a single [account](../../../../concepts/accounts/index.md), its settings, and XRP balance. ## Example {% $frontmatter.seo.title %} JSON @@ -39,7 +39,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e | Field | JSON Type | [Internal Type][] | Required? | Description | |:------------------------------|:----------|:------------------|:----------|:-------------| -| `Account` | String | AccountID | Yes | The identifying (classic) address of this [account](../../../../concepts/accounts/accounts.md). | +| `Account` | String | AccountID | Yes | The identifying (classic) address of this [account](../../../../concepts/accounts/index.md). | | `AccountTxnID` | String | Hash256 | No | The identifying hash of the transaction most recently sent by this account. This field must be enabled to use the [`AccountTxnID` transaction field](../../transactions/common-fields.md#accounttxnid). To enable it, send an [AccountSet transaction with the `asfAccountTxnID` flag enabled](../../transactions/types/accountset.md#accountset-flags). | | `AMMID` | String | Hash256 | No | _(Requires the [AMM amendment][] {% not-enabled /%})_ The ledger entry ID of the corresponding AMM ledger entry. Set during account creation; cannot be modified. If present, indicates that this is a special AMM AccountRoot; always omitted on non-AMM accounts. | | `Balance` | String | Amount | No | The account's current [XRP balance in drops][XRP, in drops], represented as a string. | diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md index 15bd2c3e98..3440c0745d 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md @@ -34,7 +34,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e | Name | JSON Type | Internal Type | Required? | Description | |:--------------------|:----------|:--------------|:----------|:---------------------------| -| `Account` | String | AccountID | Yes | The [account](../../../../concepts/accounts/accounts.md) that owns this Ticket. | +| `Account` | String | AccountID | Yes | The [account](../../../../concepts/accounts/index.md) that owns this Ticket. | | `LedgerEntryType` | String | UInt16 | Yes | The value `0x0054`, mapped to the string `Ticket`, indicates that this is a {% $frontmatter.seo.title %} entry. | | `OwnerNode` | String | UInt64 | Yes | A hint indicating which page of the owner directory links to this entry, in case the directory consists of multiple pages. | | `PreviousTxnID` | String | Hash256 | Yes | The identifying hash of the [transaction](../../../../concepts/transactions/index.md) that most recently modified this entry. | diff --git a/docs/references/protocol/transactions/common-fields.md b/docs/references/protocol/transactions/common-fields.md index 5ab89a44d1..6bb47c8d01 100644 --- a/docs/references/protocol/transactions/common-fields.md +++ b/docs/references/protocol/transactions/common-fields.md @@ -12,7 +12,7 @@ Every transaction has the same set of common fields, plus additional fields base | Field | JSON Type | [Internal Type][] | Description | |:---------------------|:-----------------|:------------------|:-----------------| -| `Account` | String | AccountID | _(Required)_ The unique address of the [account](../../../concepts/accounts/accounts.md) that initiated the transaction. | +| `Account` | String | AccountID | _(Required)_ The unique address of the [account](../../../concepts/accounts/index.md) that initiated the transaction. | | `TransactionType` | String | UInt16 | _(Required)_ The type of transaction. Valid [transaction types](types/index.md) include: `Payment`, `OfferCreate`, `TrustSet`, and many others. | | `Fee` | String | Amount | _(Required; [auto-fillable][])_ Integer amount of XRP, in drops, to be destroyed as a cost for distributing this transaction to the network. Some transaction types have different minimum requirements. See [Transaction Cost][] for details. | | `Sequence` | Number | UInt32 | _(Required; [auto-fillable][])_ The [sequence number](../data-types/basic-data-types.md#account-sequence) of the account sending the transaction. A transaction is only valid if the `Sequence` number is exactly 1 greater than the previous transaction from the same account. The special case `0` means the transaction is using a [Ticket](../../../concepts/accounts/tickets.md) instead _(Added by the [TicketBatch amendment][].)_. | diff --git a/docs/references/protocol/transactions/transaction-results/tem-codes.md b/docs/references/protocol/transactions/transaction-results/tem-codes.md index 8196018daa..c32d5a9143 100644 --- a/docs/references/protocol/transactions/transaction-results/tem-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tem-codes.md @@ -33,7 +33,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco | `temBAD_SEND_XRP_PATHS` | The [Payment transaction][] included `Paths` while sending XRP, even though XRP-to-XRP payments should always be direct. | | `temBAD_SEQUENCE` | The transaction is references a sequence number that is higher than its own `Sequence` number, for example trying to cancel an offer that would have to be placed after the transaction that cancels it. | | `temBAD_SIGNATURE` | The signature to authorize this transaction is either missing, or formed in a way that is not a properly-formed signature. (See [`tecNO_PERMISSION`](tec-codes.md) for the case where the signature is properly formed, but not authorized for this account.) | -| `temBAD_SRC_ACCOUNT` | The `Account` on whose behalf this transaction is being sent (the "source account") is not a properly-formed [account](../../../../concepts/accounts/accounts.md) address. | +| `temBAD_SRC_ACCOUNT` | The `Account` on whose behalf this transaction is being sent (the "source account") is not a properly-formed [account](../../../../concepts/accounts/index.md) address. | | `temBAD_TRANSFER_RATE` | The [`TransferRate` field of an AccountSet transaction](../types/accountset.md#transferrate) is not properly formatted or out of the acceptable range. | | `temCANNOT_PREAUTH_SELF` | The sender of the [DepositPreauth transaction][] was also specified as the account to preauthorize. You cannot preauthorize yourself. | | `temDST_IS_SRC` | The transaction improperly specified a destination address as the `Account` sending the transaction. This includes trust lines (where the destination address is the `issuer` field of `LimitAmount`) and payment channels (where the destination address is the `Destination` field). | diff --git a/docs/references/protocol/transactions/types/checkcreate.md b/docs/references/protocol/transactions/types/checkcreate.md index 1cb8c19cbd..e5883e76a3 100644 --- a/docs/references/protocol/transactions/types/checkcreate.md +++ b/docs/references/protocol/transactions/types/checkcreate.md @@ -35,7 +35,7 @@ Create a Check object in the ledger, which is a deferred payment that can be cas | Field | JSON Type | [Internal Type][] | Description | |:-----------------|:--------------------|:------------------|:----------------| -| `Destination` | String | AccountID | The unique address of the [account](../../../../concepts/accounts/accounts.md) that can cash the Check. | +| `Destination` | String | AccountID | The unique address of the [account](../../../../concepts/accounts/index.md) that can cash the Check. | | `SendMax` | [Currency Amount][] | Amount | Maximum amount of source currency the Check is allowed to debit the sender, including [transfer fees](../../../../concepts/tokens/transfer-fees.md) on non-XRP currencies. The Check can only credit the destination with the same currency (from the same issuer, for non-XRP currencies). For non-XRP amounts, the nested field names MUST be lower-case. | | `DestinationTag` | Number | UInt32 | _(Optional)_ Arbitrary tag that identifies the reason for the Check, or a hosted recipient to pay. | | `Expiration` | Number | UInt32 | _(Optional)_ Time after which the Check is no longer valid, in [seconds since the Ripple Epoch][]. | @@ -45,7 +45,7 @@ Create a Check object in the ledger, which is a deferred payment that can be cas - If the `Destination` account is blocking incoming Checks, the transaction fails with the result code `tecNO_PERMISSION`. _(Requires the [DisallowIncoming amendment][] {% not-enabled /%})_ - If the `Destination` is the sender of the transaction, the transaction fails with the result code `temREDUNDANT`. -- If the `Destination` [account](../../../../concepts/accounts/accounts.md) does not exist in the ledger, the transaction fails with the result code `tecNO_DST`. +- If the `Destination` [account](../../../../concepts/accounts/index.md) does not exist in the ledger, the transaction fails with the result code `tecNO_DST`. - If the `Destination` account has the `RequireDest` flag enabled but the transaction does not include a `DestinationTag` field, the transaction fails with the result code `tecDST_TAG_NEEDED`. - If `SendMax` specifies a token which is [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md), the transaction fails with the result `tecFROZEN`. - If the `Expiration` of the transaction is in the past, the transaction fails with the result `tecEXPIRED`. diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index 176082cf19..dcb000aa55 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -84,7 +84,7 @@ Most of the time, the `issuer` field of a non-XRP [Currency Amount][] indicates The Payment transaction type can create new accounts in the XRP Ledger by sending enough XRP to an unfunded address. Other transactions to unfunded addresses always fail. -For more information, see [Accounts](../../../../concepts/accounts/accounts.md#creating-accounts). +For more information, see [Accounts](../../../../concepts/accounts/index.md#creating-accounts). ## Paths diff --git a/docs/tutorials/java/get-started.md b/docs/tutorials/java/get-started.md index 68c335bed7..ce57a113db 100644 --- a/docs/tutorials/java/get-started.md +++ b/docs/tutorials/java/get-started.md @@ -77,7 +77,7 @@ Check out the [xrpl4j sample project](https://github.com/XRPLF/xrpl4j-sample) fo ## Start Building -When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/accounts.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. +When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/index.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. Here are the basic steps you'll need to cover for almost any XRP Ledger project: @@ -115,7 +115,7 @@ The sample code in the previous section shows you how to connect to the Testnet, ### 2. Get account -To store value and execute transactions on the XRP Ledger, you need to get an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/accounts.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up a [secure signing method](../../concepts/transactions/secure-signing.md). +To store value and execute transactions on the XRP Ledger, you need to get an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/index.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up a [secure signing method](../../concepts/transactions/secure-signing.md). To generate a new account, `xrpl4j` provides the [`DefaultWalletFactory`](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/org/xrpl/xrpl4j/wallet/DefaultWalletFactory.html). diff --git a/docs/tutorials/javascript/get-started.md b/docs/tutorials/javascript/get-started.md index 2efc6269d5..b995361ea2 100644 --- a/docs/tutorials/javascript/get-started.md +++ b/docs/tutorials/javascript/get-started.md @@ -43,7 +43,7 @@ npm install xrpl ## Start Building -When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/accounts.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. +When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/index.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. Here are some steps you use in many XRP Ledger projects: diff --git a/docs/tutorials/php/get-started.md b/docs/tutorials/php/get-started.md index 5d76e332f5..3669173794 100644 --- a/docs/tutorials/php/get-started.md +++ b/docs/tutorials/php/get-started.md @@ -45,7 +45,7 @@ composer require hardcastle/xrpl_php ## Start Building -When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/accounts.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. +When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/index.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. Here are the basic steps you'll need to cover for almost any XRP Ledger project: @@ -99,7 +99,7 @@ The sample code in the previous section shows you how to connect to the Testnet, ### 2. Get account -To store value and execute transactions on the XRP Ledger, you need to get an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/accounts.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up a [secure signing method](../../concepts/transactions/secure-signing.md). +To store value and execute transactions on the XRP Ledger, you need to get an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/index.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up a [secure signing method](../../concepts/transactions/secure-signing.md). To generate a new account, `PHP_XRPL` provides the static `generate()` method in the `Wallet` class: diff --git a/docs/tutorials/python/get-started.md b/docs/tutorials/python/get-started.md index 2da5423135..4270f4207e 100644 --- a/docs/tutorials/python/get-started.md +++ b/docs/tutorials/python/get-started.md @@ -36,7 +36,7 @@ pip3 install xrpl-py ## Start Building -When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/accounts.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. +When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../concepts/accounts/index.md), integrating with the [decentralized exchange](../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them. Here are the basic steps you'll need to cover for almost any XRP Ledger project: @@ -76,7 +76,7 @@ The sample code in the previous section shows you how to connect to the Testnet, ### 2. Get account -To store value and execute transactions on the XRP Ledger, you need an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/accounts.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. +To store value and execute transactions on the XRP Ledger, you need an account: a [set of keys](../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../concepts/accounts/index.md#creating-accounts) to meet the [account reserve](../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger. For testing and development purposes, you can use the [XRP Faucets](/resources/dev-tools/xrp-faucets) to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a [secure signing method](../../concepts/transactions/secure-signing.md). Another difference in production is that XRP has real worth, so you can't get it for free from a faucet. diff --git a/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md b/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md index cb3b491827..9a25a9955c 100644 --- a/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md +++ b/docs/tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md @@ -9,7 +9,7 @@ labels: --- # Assign a Regular Key Pair -The XRP Ledger allows an account to authorize a secondary key pair, called a _[regular key pair](../../../concepts/accounts/cryptographic-keys.md)_, to sign future transactions. If the private key of a regular key pair is compromised, you can remove or replace it without changing the rest of your [account](../../../concepts/accounts/accounts.md) and re-establishing its relationships to other accounts. You can also rotate a regular key pair proactively. (Neither of those things is possible for the master key pair of an account, which is intrinsically linked to the account's address.) +The XRP Ledger allows an account to authorize a secondary key pair, called a _[regular key pair](../../../concepts/accounts/cryptographic-keys.md)_, to sign future transactions. If the private key of a regular key pair is compromised, you can remove or replace it without changing the rest of your [account](../../../concepts/accounts/index.md) and re-establishing its relationships to other accounts. You can also rotate a regular key pair proactively. (Neither of those things is possible for the master key pair of an account, which is intrinsically linked to the account's address.) For more information about master and regular key pairs, see [Cryptographic Keys](../../../concepts/accounts/cryptographic-keys.md). diff --git a/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md b/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md index db7c52958b..84a135a8b9 100644 --- a/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md +++ b/docs/tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md @@ -9,7 +9,7 @@ labels: --- # Change or Remove a Regular Key Pair -The XRP Ledger allows an account to authorize a secondary key pair, called a _[regular key pair](../../../concepts/accounts/cryptographic-keys.md)_, to sign future transactions. If your [account](../../../concepts/accounts/accounts.md)'s regular key pair is compromised, or if you want to periodically change the regular key pair as a security measure, use a [SetRegularKey transaction][] to remove or change the regular key pair for your account. +The XRP Ledger allows an account to authorize a secondary key pair, called a _[regular key pair](../../../concepts/accounts/cryptographic-keys.md)_, to sign future transactions. If your [account](../../../concepts/accounts/index.md)'s regular key pair is compromised, or if you want to periodically change the regular key pair as a security measure, use a [SetRegularKey transaction][] to remove or change the regular key pair for your account. For more information about master and regular key pairs, see [Cryptographic Keys](../../../concepts/accounts/cryptographic-keys.md). diff --git a/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md b/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md index cb893b3a01..373bf6e18a 100644 --- a/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md +++ b/docs/tutorials/tasks/manage-account-settings/disable-master-key-pair.md @@ -9,7 +9,7 @@ labels: --- # Disable Master Key Pair -This page describes how to disable the [master key pair](../../../concepts/accounts/cryptographic-keys.md) that is mathematically associated with an [account](../../../concepts/accounts/accounts.md)'s address. You should do this if your account's master key pair may have been compromised, or if you want to make [multi-signing](../../../concepts/accounts/multi-signing.md) the _only_ way to submit transactions from your account. +This page describes how to disable the [master key pair](../../../concepts/accounts/cryptographic-keys.md) that is mathematically associated with an [account](../../../concepts/accounts/index.md)'s address. You should do this if your account's master key pair may have been compromised, or if you want to make [multi-signing](../../../concepts/accounts/multi-signing.md) the _only_ way to submit transactions from your account. **Warning:** Disabling the master key pair removes one method of [authorizing transactions](../../../concepts/transactions/index.md#authorizing-transactions). You should be sure you can use one of the other ways of authorizing transactions, such as with a regular key or by multi-signing, before you disable the master key pair. (For example, if you [assigned a regular key pair](assign-a-regular-key-pair.md), make sure that you can successfully submit transactions with that regular key.) Due to the decentralized nature of the XRP Ledger, no one can restore access to your account if you cannot use the remaining ways of authorizing transactions. @@ -19,7 +19,7 @@ This page describes how to disable the [master key pair](../../../concepts/accou To disable the master key pair for an account, you must meet the following prerequisites: -- You must have an XRP Ledger [account](../../../concepts/accounts/accounts.md) and you must be able to sign and submit transactions from that account using the master key pair. See also: [Set Up Secure Signing](../../../concepts/transactions/secure-signing.md). Two common ways this can work are: +- You must have an XRP Ledger [account](../../../concepts/accounts/index.md) and you must be able to sign and submit transactions from that account using the master key pair. See also: [Set Up Secure Signing](../../../concepts/transactions/secure-signing.md). Two common ways this can work are: - You know the account's master seed value. A seed value is commonly represented as a [base58][] value starting with "s", such as `sn3nxiW7v8KXzPzAqzyHXbSSKNuN9`. - Or, you use a [dedicated signing device](../../../concepts/transactions/secure-signing.md#use-a-dedicated-signing-device) that stores the seed value securely, so you don't need to know it. - Your account must have at least one method of authorizing transactions other than the master key pair. In other words, you must do one or both of the following: diff --git a/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md b/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md index e73f048371..84edf10c31 100644 --- a/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md +++ b/docs/tutorials/tasks/manage-account-settings/offline-account-setup.md @@ -9,7 +9,7 @@ labels: --- # Offline Account Setup Tutorial -A highly secure [signing configuration](../../../concepts/transactions/secure-signing.md) involves keeping an XRP Ledger [account](../../../concepts/accounts/accounts.md)'s [cryptographic keys](../../../concepts/accounts/cryptographic-keys.md) securely on an offline, air-gapped machine. After setting up this configuration, you can sign a variety of transactions, transfer only the signed transactions to an online computer, and submit them to the XRP Ledger network without ever exposing your secret key to malicious actors online. +A highly secure [signing configuration](../../../concepts/transactions/secure-signing.md) involves keeping an XRP Ledger [account](../../../concepts/accounts/index.md)'s [cryptographic keys](../../../concepts/accounts/cryptographic-keys.md) securely on an offline, air-gapped machine. After setting up this configuration, you can sign a variety of transactions, transfer only the signed transactions to an online computer, and submit them to the XRP Ledger network without ever exposing your secret key to malicious actors online. **Caution:** Proper operational security is necessary to protect your offline machine. For example, the offline machine must be physically located where untrusted people cannot get access to it, and trusted operators must be careful not to transfer compromised software onto the machine. (For example, do not use a USB drive that was previously attached to a network-connected computer.) @@ -71,7 +71,7 @@ Loading: "/etc/opt/ripple/rippled.cfg" Take note of the following values: -- **`account_id`**. This is the address associated with the key pair, which becomes your **[account](../../../concepts/accounts/accounts.md) address** in the XRP Ledger after you fund it with XRP (later in this process). It is safe to share your `account_id` publicly. +- **`account_id`**. This is the address associated with the key pair, which becomes your **[account](../../../concepts/accounts/index.md) address** in the XRP Ledger after you fund it with XRP (later in this process). It is safe to share your `account_id` publicly. - **`master_seed`**. This is the secret seed value for the key pair, which you'll use to sign transactions from the account. For best security, encrypt this value before writing it to disk on the offline machine. As an encryption key, use a secure passphrase that human operators can memorize or write down somewhere physically secure, such as a [diceware passphrase](https://theworld.com/~reinhold/diceware.html) created with properly weighted dice. You may also want to use a physical security key as a second factor. The extent of the precautions to take at this stage is up to you. - **`key_type`**. This is the cryptographic algorithm used for this key pair. You need to know what type of key pair you have. The default in `rippled` is `secp256k1`, but some client libraries use `Ed25519` by default. @@ -83,7 +83,7 @@ Take note of the following values: ### 3. Fund the new address -From an online machine, send enough XRP to the **account address** you noted in step 1. For more information, see [Creating Accounts](../../../concepts/accounts/accounts.md#creating-accounts). +From an online machine, send enough XRP to the **account address** you noted in step 1. For more information, see [Creating Accounts](../../../concepts/accounts/index.md#creating-accounts). **Tip:** For testing purposes, you can use the [Testnet Faucet](/resources/dev-tools/xrp-faucets) to get a new account with Test XRP, then use that account to fund the address you generated offline. @@ -328,7 +328,7 @@ Then adjust and sign any replacement transactions for transactions that failed i ## See Also - **Concepts:** - - [Accounts](../../../concepts/accounts/accounts.md) + - [Accounts](../../../concepts/accounts/index.md) - [Cryptographic Keys](../../../concepts/accounts/cryptographic-keys.md) - **Tutorials:** - [Set Up Secure Signing](../../../concepts/transactions/secure-signing.md) diff --git a/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md b/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md index 20d1e288e5..1c41679250 100644 --- a/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md +++ b/docs/tutorials/tasks/manage-account-settings/require-destination-tags.md @@ -148,7 +148,7 @@ For further confirmation, you can send test transactions (from a different addre ## See Also - **Concepts:** - - [Accounts](../../../concepts/accounts/accounts.md) + - [Accounts](../../../concepts/accounts/index.md) - [Source and Destination Tags](../../../concepts/transactions/source-and-destination-tags.md) - [Transaction Cost](../../../concepts/transactions/transaction-cost.md) - [Payment Types](../../../concepts/payment-types/index.md) diff --git a/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md b/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md index fa857348e3..365c714491 100644 --- a/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md +++ b/docs/tutorials/tasks/manage-account-settings/set-up-multi-signing.md @@ -8,14 +8,14 @@ labels: --- # Set Up Multi-Signing -[Multi-signing](../../../concepts/accounts/multi-signing.md) is one of three ways to authorize [transactions](../../../concepts/transactions/index.md) for the XRP Ledger, alongside signing with [regular keys and master keys](../../../concepts/accounts/cryptographic-keys.md). You can configure your [address](../../../concepts/accounts/accounts.md) to allow any combination of the three methods to authorize transactions. +[Multi-signing](../../../concepts/accounts/multi-signing.md) is one of three ways to authorize [transactions](../../../concepts/transactions/index.md) for the XRP Ledger, alongside signing with [regular keys and master keys](../../../concepts/accounts/cryptographic-keys.md). You can configure your [address](../../../concepts/accounts/index.md) to allow any combination of the three methods to authorize transactions. This tutorial demonstrates how to enable multi-signing for an address. ## Prerequisites -- You must have a funded XRP Ledger [address](../../../concepts/accounts/accounts.md) with enough spare XRP to send transactions and meet the [reserve requirement](../../../concepts/accounts/reserves.md) of a new signer list. +- You must have a funded XRP Ledger [address](../../../concepts/accounts/index.md) with enough spare XRP to send transactions and meet the [reserve requirement](../../../concepts/accounts/reserves.md) of a new signer list. - With the [MultiSignReserve amendment][] enabled, multi-signing requires 2 XRP for the account reserve, regardless of the number of signers and signatures you use. (The MultiSignReserve amendment has been enabled in the production XRP Ledger since **2019-04-07**.) diff --git a/docs/tutorials/tasks/send-xrp.md b/docs/tutorials/tasks/send-xrp.md index 71f7959248..a9f061403b 100644 --- a/docs/tutorials/tasks/send-xrp.md +++ b/docs/tutorials/tasks/send-xrp.md @@ -395,7 +395,7 @@ print_r("Seed: " . $wallet->getSeed()); // Example: sp6JS7f14BuwFY8Mw6bTtLKWauoU **Warning:** You should only use an address and secret that you generated securely, on your local machine. If another computer generated the address and secret and sent it to you over a network, it's possible that someone else on the network may see that information. If they do, they'll have as much control over your XRP as you do. It's also recommended not to use the same address for the Testnet and Mainnet, because transactions that you created for use on one network could also be valid to execute on the other network, depending on the parameters you provided. -Generating an address and secret doesn't get you XRP directly; you're only choosing a random number. You must also receive XRP at that address to [fund the account](../../concepts/accounts/accounts.md#creating-accounts). A common way to acquire XRP is to buy it from an exchange, then withdraw it to your own address. +Generating an address and secret doesn't get you XRP directly; you're only choosing a random number. You must also receive XRP at that address to [fund the account](../../concepts/accounts/index.md#creating-accounts). A common way to acquire XRP is to buy it from an exchange, then withdraw it to your own address. ### Connecting to the Production XRP Ledger diff --git a/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/use-an-escrow-as-a-smart-contract.md b/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/use-an-escrow-as-a-smart-contract.md index 9fcaf2566a..f9a67e4911 100644 --- a/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/use-an-escrow-as-a-smart-contract.md +++ b/docs/tutorials/tasks/use-specialized-payment-types/use-escrows/use-an-escrow-as-a-smart-contract.md @@ -28,13 +28,13 @@ Here’s a roadmap to the high-level tasks that these participants need to compl The party host (sender) must have: -- An XRP Ledger [account](../../../../concepts/accounts/accounts.md#creating-accounts) that holds enough XRP to pay for escrow and any fees incurred. +- An XRP Ledger [account](../../../../concepts/accounts/index.md#creating-accounts) that holds enough XRP to pay for escrow and any fees incurred. - Access to a secure signing environment, which includes having a network connection to a [`rippled` server](../../../../infrastructure/installation/index.md) (any server) that they can submit signed transactions to. The party band (receiver) must have: -- An XRP Ledger [account](../../../../concepts/accounts/accounts.md#creating-accounts) that can receive the XRP paid by the escrow. +- An XRP Ledger [account](../../../../concepts/accounts/index.md#creating-accounts) that can receive the XRP paid by the escrow. - Access to a [`rippled` server](../../../../infrastructure/installation/index.md) that they can use to look up the details of an XRP Ledger transaction hash and submit the fulfillment value to finish the escrow. diff --git a/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md b/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md index 0e7984fa2c..66eff9fab4 100644 --- a/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md +++ b/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/index.md @@ -11,7 +11,7 @@ labels: [Payment Channels](../../../../concepts/payment-types/payment-channels.md) are an advanced feature for sending "asynchronous" XRP payments that can be divided into very small increments and settled later. This tutorial walks through the entire process of using a payment channel, with examples using the [JSON-RPC API](../../../../references/http-websocket-apis/index.md) of a local [`rippled` server](../../../../concepts/networks-and-servers/index.md). -Ideally, to step through this tutorial, you would have two people, each with the keys to a [funded XRP Ledger account](../../../../concepts/accounts/accounts.md). However, you can also step through the tutorial as one person managing two XRP Ledger addresses. +Ideally, to step through this tutorial, you would have two people, each with the keys to a [funded XRP Ledger account](../../../../concepts/accounts/index.md). However, you can also step through the tutorial as one person managing two XRP Ledger addresses. ## Example Values diff --git a/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/open-a-payment-channel-to-enable-an-inter-exchange-network.md b/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/open-a-payment-channel-to-enable-an-inter-exchange-network.md index fb5cd6dc0e..5a60fc9132 100644 --- a/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/open-a-payment-channel-to-enable-an-inter-exchange-network.md +++ b/docs/tutorials/tasks/use-specialized-payment-types/use-payment-channels/open-a-payment-channel-to-enable-an-inter-exchange-network.md @@ -84,7 +84,7 @@ Along these lines, there's a good chance that you are following industry best pr The account needs at least 11 XRP, which provides the 10 XRP [base reserve](../../../../concepts/accounts/reserves.md), plus enough to pay the transaction costs of redeeming claims, which are trivial. For example, you could redeem thousands of claims for less than 1 XRP in total. ``` -[Fund XRP Ledger accounts with enough XRP >](../../../../concepts/accounts/accounts.md) +[Fund XRP Ledger accounts with enough XRP >](../../../../concepts/accounts/index.md) ## Payer: [Open a payment channel](index.md#1-the-payer-creates-a-payment-channel-to-a-particular-recipient) diff --git a/docs/use-cases/defi/list-xrp-as-an-exchange.md b/docs/use-cases/defi/list-xrp-as-an-exchange.md index e2efbbea8c..1ee9537191 100644 --- a/docs/use-cases/defi/list-xrp-as-an-exchange.md +++ b/docs/use-cases/defi/list-xrp-as-an-exchange.md @@ -97,7 +97,7 @@ See also: * [Issuing and Operational Addresses](../../concepts/accounts/account-types.md) -* [Creating Accounts](../../concepts/accounts/accounts.md#creating-accounts) +* [Creating Accounts](../../concepts/accounts/index.md#creating-accounts) * [Reserves](../../concepts/accounts/reserves.md) @@ -608,7 +608,7 @@ Off-Ledger Balances ## See Also - **Concepts:** - - [Accounts](../../concepts/accounts/accounts.md) + - [Accounts](../../concepts/accounts/index.md) - [Direct XRP Payments](../../concepts/payment-types/direct-xrp-payments.md) - [Partial Payments](../../concepts/payment-types/partial-payments.md) - [Source and Destination Tags](../../concepts/transactions/source-and-destination-tags.md) diff --git a/docs/use-cases/payments/peer-to-peer-payments-uc.md b/docs/use-cases/payments/peer-to-peer-payments-uc.md index 0a4a1d9510..4b0826861c 100644 --- a/docs/use-cases/payments/peer-to-peer-payments-uc.md +++ b/docs/use-cases/payments/peer-to-peer-payments-uc.md @@ -20,7 +20,7 @@ Before jumping into using the XRP Ledger to handle direct payments, you should s Before creating an account, you must decide which XRP Ledger network to use. There are multiple networks for different use cases, but native XRP transactions only happen on `Mainnet`. See: [Parallel Networks](../../concepts/networks-and-servers/parallel-networks.md) -Most publicly available wallets offer the ability to create an account for you and can generate a public and private key. If they don't, you can create an account yourself, so long as it's mathematically valid. See: [Creating Accounts](../../concepts/accounts/accounts.md#creating-accounts). +Most publicly available wallets offer the ability to create an account for you and can generate a public and private key. If they don't, you can create an account yourself, so long as it's mathematically valid. See: [Creating Accounts](../../concepts/accounts/index.md#creating-accounts). ## Fund Your Account diff --git a/resources/known-amendments.md b/resources/known-amendments.md index 7edc3d4c0b..0c120bdbbf 100644 --- a/resources/known-amendments.md +++ b/resources/known-amendments.md @@ -324,7 +324,7 @@ However, the amendment was added to `rippled` v0.60.0 before implementation was | Default Vote (Latest stable release) | Yes | | Pre-amendment functionality retired? | No | -Makes it possible to delete [accounts](../docs/concepts/accounts/accounts.md). +Makes it possible to delete [accounts](../docs/concepts/accounts/index.md). Without this amendment, new accounts always start with their `Sequence` numbers at 1, and there is no way to remove accounts from the state data of the ledger. @@ -704,7 +704,7 @@ Without this amendment, the minimum threshold for amendment activation is any va | Default Vote (Latest stable release) | Yes | | Pre-amendment functionality retired? | No | -Changes the way Checks transactions affect account metadata, so that Checks are properly added to the [account](../docs/concepts/accounts/accounts.md) history of the receiving account. (Specifically, they update the `PreviousTxnID` and `PreviousTxnLedgerSeq` fields of the receiving account's [AccountRoot object](../docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md), which can be used to trace the "thread" of transactions that affected the account and the objects it owns.) +Changes the way Checks transactions affect account metadata, so that Checks are properly added to the [account](../docs/concepts/accounts/index.md) history of the receiving account. (Specifically, they update the `PreviousTxnID` and `PreviousTxnLedgerSeq` fields of the receiving account's [AccountRoot object](../docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md), which can be used to trace the "thread" of transactions that affected the account and the objects it owns.) Without this amendment, Checks transactions ([CheckCreate][], [CheckCash][], and [CheckCancel][]) only update the account history of the sender. With this amendment, those transactions affect both the sending and receiving accounts. This amendment has no effect unless the [Checks amendment](#checks) is also enabled.