diff --git a/content/_snippets/post-rippled-install.ja.md b/content/_snippets/post-rippled-install.ja.md index 80b6df2331..39c0c9ddd9 100644 --- a/content/_snippets/post-rippled-install.ja.md +++ b/content/_snippets/post-rippled-install.ja.md @@ -23,7 +23,7 @@ rippled APIを使用した`rippled`サーバーとの通信について詳しく {% include '_snippets/conf-file-location.md' %} -すべての構成オプションの説明については、[`rippled` GitHubリポジトリー](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg)を参照してください。 +すべての構成オプションの説明については、[`rippled` GitHubリポジトリー](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)を参照してください。 構成の変更を有効にするには、`rippled`を再起動する必要があります。 diff --git a/content/_snippets/post-rippled-install.md b/content/_snippets/post-rippled-install.md index 4f23277706..6b71398d29 100644 --- a/content/_snippets/post-rippled-install.md +++ b/content/_snippets/post-rippled-install.md @@ -23,7 +23,7 @@ Having trouble getting your server started? See [rippled Server Won't Start](ser {% include '_snippets/conf-file-location.md' %} -See [the `rippled` GitHub repository](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options. +See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options. You must restart `rippled` for any configuration changes to take effect: diff --git a/content/_snippets/rippled_versions.md b/content/_snippets/rippled_versions.md index 6392a4d39c..321a2456fa 100644 --- a/content/_snippets/rippled_versions.md +++ b/content/_snippets/rippled_versions.md @@ -47,12 +47,12 @@ ] %} {% for v in rippled_versions %} -[New in: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[Introduced in: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[Updated in: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[Removed in: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_RED" -[導入: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[新規: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[更新: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_BLUE" -[削除: rippled {{v}}]: https://github.com/ripple/rippled/releases/tag/{{v}} "BADGE_RED" +[New in: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[Introduced in: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[Updated in: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[Removed in: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_RED" +[導入: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[新規: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[更新: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_BLUE" +[削除: rippled {{v}}]: https://github.com/XRPLF/rippled/releases/tag/{{v}} "BADGE_RED" {% endfor %} diff --git a/content/concepts/accounts/accounts.ja.md b/content/concepts/accounts/accounts.ja.md index 8feed9de74..f5c4139caa 100644 --- a/content/concepts/accounts/accounts.ja.md +++ b/content/concepts/accounts/accounts.ja.md @@ -61,7 +61,7 @@ XRP Ledgerでは、過去の使用という点で、一部のアドレスに特 |-----------------------------|------|---------|-------------| | rrrrrrrrrrrrrrrrrrrrrhoLvTp | ACCOUNT_ZERO | 値`0`を[base58][]形式にエンコードしたXRP Ledgerのアドレス。ピアツーピア通信では、このアドレスは、XRPの発行者として`rippled`で使用されます。 | はい | | rrrrrrrrrrrrrrrrrrrrBZbvji | ACCOUNT_ONE | 値`1`を[base58][]形式にエンコードしたXRP Ledgerのアドレス。レジャーの[RippleState項目](ripplestate.html)では、このアドレスは、トラストライン残高の発行者のプレースホルダーとして使用されます。 | はい | -| rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh | ジェネシスアカウント | `rippled`で新しいジェネシスレジャーが一から開始される場合（例えば、スタンドアロンモード）、このアカウントはすべてのXRPを保持します。このアドレスは、シード値「masterpassphrase」から生成されており、この値は[ハードコーディング](https://github.com/ripple/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 | いいえ | +| rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh | ジェネシスアカウント | `rippled`で新しいジェネシスレジャーが一から開始される場合（例えば、スタンドアロンモード）、このアカウントはすべてのXRPを保持します。このアドレスは、シード値「masterpassphrase」から生成されており、この値は[ハードコーディング](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 | いいえ | | rrrrrrrrrrrrrrrrrNAMEtxvNvQ | Ripple名予約のブラックホール | 以前は、Rippleでは、このアカウントにXRPを送信してRipple名を予約するようユーザーに求めていました。 | はい | | rrrrrrrrrrrrrrrrrrrn5RM1rHd | NaNアドレス | 以前のバージョンの[ripple-lib](https://github.com/XRPLF/xrpl.js)では、XRP Ledgerの[base58][]文字列エンコード形式を使用して、値[NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)をエンコードするときにこのアドレスを生成しました。 | はい | @@ -113,7 +113,7 @@ XRP Ledgerでは、トランザクション（取引）履歴をトランザク **ヒント:** これらの技術的な詳細は、XRP Ledgerとの互換性を保つために低レベルのライブラリソフトウェアを構築しているユーザーのみを対象としています。 -[[ソース]](https://github.com/ripple/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Source") XRP Ledgerのアドレスは、[base58][]_形式のディクショナリ_`rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`を使用してエンコードされています。XRP Ledgerはbase58でいくつかのタイプのキーをエンコードするため、それらを区別するためにエンコードされたデータの前に1バイトの「タイププレフィクス」（「バージョンプレフィクス」とも呼ばれます）を付けます。タイププレフィクスによりアドレスは通常、base58形式の異なる文字で始まります。 @@ -181,6 +181,6 @@ XRP Ledgerのアドレスは、[base58][]_形式のディクショナリ_`rpshna - [WebSocketを使用した着信ペイメントの監視](monitor-incoming-payments-with-websocket.html) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/accounts/addresses.md b/content/concepts/accounts/addresses.md index dcf78d0829..d89be8102d 100644 --- a/content/concepts/accounts/addresses.md +++ b/content/concepts/accounts/addresses.md @@ -23,7 +23,7 @@ Some addresses have special meaning, or historical uses, in the XRP Ledger. In m |-------------------------------|------|---------|-------------| | `rrrrrrrrrrrrrrrrrrrrrhoLvTp` | ACCOUNT\_ZERO | An address that is the XRP Ledger's [base58][] encoding of the value `0`. In peer-to-peer communications, `rippled` uses this address as the issuer for XRP. | Yes | | `rrrrrrrrrrrrrrrrrrrrBZbvji` | ACCOUNT\_ONE | An address that is the XRP Ledger's [base58][] encoding of the value `1`. In the ledger, [RippleState entries](ripplestate.html) use this address as a placeholder for the issuer of a trust line balance. | Yes | -| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | The genesis account | When `rippled` starts a new genesis ledger from scratch (for example, in stand-alone mode), this account holds all the XRP. This address is generated from the seed value `masterpassphrase` which is [hard-coded](https://github.com/ripple/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184). | No | +| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | The genesis account | When `rippled` starts a new genesis ledger from scratch (for example, in stand-alone mode), this account holds all the XRP. This address is generated from the seed value `masterpassphrase` which is [hard-coded](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184). | No | | `rrrrrrrrrrrrrrrrrNAMEtxvNvQ` | Ripple Name reservation black-hole | In the past, Ripple asked users to send XRP to this account to reserve Ripple Names.| Yes | | `rrrrrrrrrrrrrrrrrrrn5RM1rHd` | NaN Address | Previous versions of [ripple-lib](https://github.com/XRPLF/xrpl.js) generated this address when encoding the value [NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN) using the XRP Ledger's [base58][] string encoding format. | Yes | @@ -32,7 +32,7 @@ Some addresses have special meaning, or historical uses, in the XRP Ledger. In m **Tip:** These technical details are only relevant for people building low-level library software for XRP Ledger compatibility! -[[Source]](https://github.com/ripple/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Source") XRP Ledger addresses are encoded using [base58][] with the _dictionary_ `rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`. Since the XRP Ledger encodes several types of keys with base58, it prefixes the encoded data with a one-byte "type prefix" (also called a "version prefix") to distinguish them. The type prefix causes addresses to usually start with different letters in base58 format. @@ -84,6 +84,6 @@ The formula for calculating an XRP Ledger address from a public key is as follow -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/consensus-protocol/consensus-protections.ja.md b/content/concepts/consensus-protocol/consensus-protections.ja.md index 9ca7e42ad1..e526381631 100644 --- a/content/concepts/consensus-protocol/consensus-protections.ja.md +++ b/content/concepts/consensus-protocol/consensus-protections.ja.md @@ -34,7 +34,7 @@ _バリデータ_ とは、新しいレジャーバージョンの決定プロ あらゆるソフトウェアシステムと同様に、XRP Ledgerコンセンサスプロトコル、広く導入されているソフトウェアパッケージ、またはその依存関係の実装に伴うバグ（または意図的に悪意のあるコード）の問題には、真剣に取り組む必要があります。巧妙に作成された入力を取り込んだサーバーをクラッシュさせるだけのバグであっても、ネットワークの進捗を妨害する目的で悪用される可能性があります。Rippleではこのような脅威に対処するため、次のようなさまざまな対策を導入しています。 -- [オープンソースコードベース](https://github.com/ripple/rippled/)。これにより、一般のユーザーが関連ソフトウェアをレビュー、コンパイルし、個別にテストできます。 +- [オープンソースコードベース](https://github.com/XRPLF/rippled/)。これにより、一般のユーザーが関連ソフトウェアをレビュー、コンパイルし、個別にテストできます。 - 公式XRP Ledgerリポジトリのあらゆる変更のための綿密で堅固なコードレビュープロセス。 - すべてのリリースと公式ソフトウェアパッケージへのRipple社員によるデジタル署名付与。 - セキュリティの脆弱性と不安定さに関する定期的に委託された専門家レビュー。 diff --git a/content/concepts/consensus-protocol/consensus-protections.md b/content/concepts/consensus-protocol/consensus-protections.md index d0b3db54e1..7603bcabfa 100644 --- a/content/concepts/consensus-protocol/consensus-protections.md +++ b/content/concepts/consensus-protocol/consensus-protections.md @@ -34,7 +34,7 @@ The only way to confirm an invalid transaction would be to get at least 80% of t As with any software system, bugs (or intentionally malicious code) in the implementation of the XRP Ledger Consensus Protocol, commonly deployed software packages, or their dependencies, are a problem to be taken seriously. Even bugs that cause a server to crash when it sees carefully crafted inputs can be abused to disrupt the progress of the network. Ripple takes precautions to address this threat in its reference implementations of XRP Ledger software, including: -- An [open-source code base](https://github.com/ripple/rippled/), so any member of the public can review, compile, and independently test the relevant software. +- An [open-source code base](https://github.com/XRPLF/rippled/), so any member of the public can review, compile, and independently test the relevant software. - A thorough and robust code review process for all changes to the official XRP Ledger repositories. - Digital signatures from Ripple employees on all releases and official software packages. - Regularly-commissioned professional reviews for security vulnerabilities and insecurities. diff --git a/content/concepts/consensus-protocol/consensus-structure.ja.md b/content/concepts/consensus-protocol/consensus-structure.ja.md index e0dbc1f7db..dec713c9c7 100644 --- a/content/concepts/consensus-protocol/consensus-structure.ja.md +++ b/content/concepts/consensus-protocol/consensus-structure.ja.md @@ -103,7 +103,7 @@ _図5: バリデータによるトランザクションセットの提案と修 2. すべてのサーバーが同じ方法で処理できるように、合意済みのトランザクションセットを _正規順序_ で並べ変えます。 - [正規順序](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36)は、トランザクションを受け取った順序ではありません（サーバーが同じトランザクションを異なる順序で受け取る可能性があるため）。参加者がトランザクションの順序付けで競合しないように、故意に操作するのが困難な正規順序を使います。 + [正規順序](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36)は、トランザクションを受け取った順序ではありません（サーバーが同じトランザクションを異なる順序で受け取る可能性があるため）。参加者がトランザクションの順序付けで競合しないように、故意に操作するのが困難な正規順序を使います。 3. 指示に従って、各トランザクションを順番に処理します。それに応じてレジャーの状態データを更新します。 @@ -211,6 +211,6 @@ XRP Ledgerに送信されたトランザクションはすぐには処理され -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/consensus-protocol/consensus-structure.md b/content/concepts/consensus-protocol/consensus-structure.md index 7b63bd7c01..e98ef7a5f3 100644 --- a/content/concepts/consensus-protocol/consensus-structure.md +++ b/content/concepts/consensus-protocol/consensus-structure.md @@ -106,7 +106,7 @@ When the consensus process completes, each server independently computes a new l 2. Place the agreed-upon transaction set in _canonical order_ so that every server processes them the same way. - [Canonical order](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36) is not the order the transactions were received, because servers may receive the same transactions in different order. To prevent participants from competing over transaction ordering, canonical order is hard to manipulate. + [Canonical order](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36) is not the order the transactions were received, because servers may receive the same transactions in different order. To prevent participants from competing over transaction ordering, canonical order is hard to manipulate. 3. Process each transaction according to its instructions, in order. Update the ledger's state data accordingly. @@ -213,6 +213,6 @@ Best practices for applications submitting transactions include: -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/consensus-protocol/invariant-checking.ja.md b/content/concepts/consensus-protocol/invariant-checking.ja.md index 9d2a2979d9..b114c72766 100644 --- a/content/concepts/consensus-protocol/invariant-checking.ja.md +++ b/content/concepts/consensus-protocol/invariant-checking.ja.md @@ -37,39 +37,39 @@ labels: XRP Ledgerは、各トランザクションについて、以下のすべての不変条件をチェックします。 -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "ソース") - [トランザクション手数料チェック](#トランザクション手数料チェック) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "ソース") - [XRPは作成されません](#xrpは作成されません) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "ソース") - [アカウントルートが削除されていない](#アカウントルートが削除されていない) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "ソース") - [XRPの残高確認](#xrpの残高確認) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "ソース") - [レジャーエントリ形式の一致](#レジャーエントリ形式の一致) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "ソース") - [XRPのトラストラインはありません](#xrpのトラストラインはありません) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "ソース") - [不正なオファーでない](#不正なオファーでない) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "ソース") - [0のエスクローでない](#0のエスクローでない) -[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "ソース") - [有効な新規アカウントルート](#有効な新規アカウントルート) @@ -137,11 +137,11 @@ XRP Ledgerは、各トランザクションについて、以下のすべての - [レジャーの保護: 不変性チェック](https://xrpl.org/blog/2017/invariant-checking.html) - **リポジトリ:** - - [Invariant Check.h](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) - - [Invariant Check.cpp](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) - - [System Parameters](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) - - [XRP Amount](https://github.com/ripple/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) - - [Ledger Formats](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) + - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) + - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) + - [System Parameters](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) + - [XRP Amount](https://github.com/XRPLF/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) + - [Ledger Formats](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) - **その他:** @@ -151,6 +151,6 @@ XRP Ledgerは、各トランザクションについて、以下のすべての -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/consensus-protocol/invariant-checking.md b/content/concepts/consensus-protocol/invariant-checking.md index 47aa449351..240c86713a 100644 --- a/content/concepts/consensus-protocol/invariant-checking.md +++ b/content/concepts/consensus-protocol/invariant-checking.md @@ -37,39 +37,39 @@ To include the transaction in the ledger with a `tec`-class code, some minimal p The XRP Ledger checks all the following invariants on each transaction: -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "Source") - [Transaction Fee Check](#transaction-fee-check) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "Source") - [XRP Not Created](#xrp-not-created) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "Source") - [Account Roots Not Deleted](#account-roots-not-deleted) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "Source") - [XRP Balance Checks](#xrp-balance-checks) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "Source") - [Ledger Entry Types Match](#ledger-entry-types-match) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "Source") - [No XRP Trust Lines](#no-xrp-trust-lines) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "Source") - [No Bad Offers](#no-bad-offers) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "Source") - [No Zero Escrow](#no-zero-escrow) -[[Source]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "Source") - [Valid New Account Root](#valid-new-account-root) @@ -140,7 +140,7 @@ The XRP Ledger checks all the following invariants on each transaction: - A successful NFTokenBurn transaction must increase the number of burned NFTs. - A failed NFTokenBurn transaction must not change the number of burned NFTs. - A NFTokenBurn transaction cannot change the number of minted NFTs. - + ### NFTokenCountTracking - **Invariant Condition(s):** @@ -157,11 +157,11 @@ The XRP Ledger checks all the following invariants on each transaction: - [Protecting the Ledger: Invariant Checking](https://xrpl.org/blog/2017/invariant-checking.html) - **Repository:** - - [Invariant Check.h](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) - - [Invariant Check.cpp](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) - - [System Parameters](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) - - [XRP Amount](https://github.com/ripple/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) - - [Ledger Formats](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) + - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) + - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) + - [System Parameters](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) + - [XRP Amount](https://github.com/XRPLF/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) + - [Ledger Formats](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) - **Other:** @@ -171,6 +171,6 @@ The XRP Ledger checks all the following invariants on each transaction: -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/networks-and-servers/ledger-history/online-deletion.ja.md b/content/concepts/networks-and-servers/ledger-history/online-deletion.ja.md index 63d2c252dd..16e40fb1d3 100644 --- a/content/concepts/networks-and-servers/ledger-history/online-deletion.ja.md +++ b/content/concepts/networks-and-servers/ledger-history/online-deletion.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # オンライン削除 -[[ソース]
](https://github.com/ripple/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") +[[ソース]
](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") オンライン削除機能により、`rippled`サーバーはレジャーの古いバージョンのローカルコピーを削除できます。これにより、時間とともにディスク使用量が急増しないようにできます。デフォルトの構成ファイルにはオンライン削除の自動実行が設定されていますが、指示があった場合にのみオンライン削除を実行するようにも設定できます。[新規: rippled 0.27.0][] diff --git a/content/concepts/networks-and-servers/ledger-history/online-deletion.md b/content/concepts/networks-and-servers/ledger-history/online-deletion.md index 09538228fd..ad10f3fada 100644 --- a/content/concepts/networks-and-servers/ledger-history/online-deletion.md +++ b/content/concepts/networks-and-servers/ledger-history/online-deletion.md @@ -7,7 +7,7 @@ labels: - Core Server --- # Online Deletion -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") The online deletion feature lets the `rippled` server delete the server's local copy of old ledger versions to keep disk usage from rapidly growing over time. The default config file sets online deletion to run automatically, but online deletion can also be configured to run only when prompted. [New in: rippled 0.27.0][] diff --git a/content/concepts/networks-and-servers/peer-protocol.ja.md b/content/concepts/networks-and-servers/peer-protocol.ja.md index cc5675d640..ff51b3d874 100644 --- a/content/concepts/networks-and-servers/peer-protocol.ja.md +++ b/content/concepts/networks-and-servers/peer-protocol.ja.md @@ -17,11 +17,11 @@ XRP Ledgerのサーバーは、XRP Ledgerピアプロトコル（RTXP）を使 - 履歴レジャーへのレジャーデータの要求、またはレジャーデータの提供。 - コンセンサスのための一連のトランザクションの提示、またはコンセンサストランザクションセットの適用に関する算出結果の共有。 -ピアツーピア接続を確立するには、サーバーどうしをHTTPSで接続し、一方のサーバーはRTXPへの切り替えのために[HTTPアップグレード](https://tools.ietf.org/html/rfc7230#section-6.7)を要求します。（詳細は、[`rippled`リポジトリ](https://github.com/ripple/rippled)の[Overlay Network](https://github.com/ripple/rippled/blob/906ef761bab95f80b0a7e0cab3b4c594b226cf57/src/ripple/overlay/README.md#handshake)を参照してください。） +ピアツーピア接続を確立するには、サーバーどうしをHTTPSで接続し、一方のサーバーはRTXPへの切り替えのために[HTTPアップグレード](https://tools.ietf.org/html/rfc7230#section-6.7)を要求します。（詳細は、[`rippled`リポジトリ](https://github.com/ripple/rippled)の[Overlay Network](https://github.com/XRPLF/rippled/blob/906ef761bab95f80b0a7e0cab3b4c594b226cf57/src/ripple/overlay/README.md#handshake)を参照してください。） ## ピアの検出 -XRP Ledgerでは、「ゴシップ」プロトコルを使用して、XRP Ledgerネットワーク内でサーバーが互いを識別できるようにします。サーバーは、起動するたびに、以前に接続したその他のあらゆるピアに再接続します。フォールバックとして、[ハードコーディングされた公開ハブ](https://github.com/ripple/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525)を使用します。サーバーがピアに正常に接続されると、ピアを探している他のXRP Ledgerサーバーの接続情報（通常はIPアドレスとポート）をそのピアに要求します。その後、サーバーはそれらのサーバーに接続し、ピア接続するXRP Ledgerサーバーの接続情報をさらに要求できます。このプロセスにより、サーバーは十分なピア接続を確立し、単一のピアへの接続が失われた場合でも、ネットワークの残りの部分にその後も接続されます。 +XRP Ledgerでは、「ゴシップ」プロトコルを使用して、XRP Ledgerネットワーク内でサーバーが互いを識別できるようにします。サーバーは、起動するたびに、以前に接続したその他のあらゆるピアに再接続します。フォールバックとして、[ハードコーディングされた公開ハブ](https://github.com/XRPLF/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525)を使用します。サーバーがピアに正常に接続されると、ピアを探している他のXRP Ledgerサーバーの接続情報（通常はIPアドレスとポート）をそのピアに要求します。その後、サーバーはそれらのサーバーに接続し、ピア接続するXRP Ledgerサーバーの接続情報をさらに要求できます。このプロセスにより、サーバーは十分なピア接続を確立し、単一のピアへの接続が失われた場合でも、ネットワークの残りの部分にその後も接続されます。 通常、サーバーが公開ハブに接続する必要があるのは1回のみです。他のピアを見つけるために、短時間のみ接続します。そうすることで、ネットワーク接続の安定性、ハブのビジー状態、およびサーバーが検出する他の高品質ピアの数に応じて、ハブにサーバーを引き続き接続するかどうかが異なります。サーバーでは、これらの他のピアのアドレスを保存するため、ネットワークの停止後または再起動後、それらのピアへの直接再接続を試行できます。 @@ -36,7 +36,7 @@ XRP Ledgerに参加するため、`rippled`サーバーはピアプロトコル サーバーがピアポートで接続を送信 _かつ_ 受信できることが理想的です。`rippled`サーバーに、[ファイアウォール経由でピアプロトコルに使用するポートを転送する](forward-ports-for-peering.html)必要があります。 -[デフォルトの`rippled`構成ファイル](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg)は、すべてのネットワークインターフェイスにおいて、ポート51235で着信ピアプロトコル接続をリッスンします。使用するポートを変更するには、`rippled.cfg`ファイル内の該当するスタンザを編集します。 +[デフォルトの`rippled`構成ファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)は、すべてのネットワークインターフェイスにおいて、ポート51235で着信ピアプロトコル接続をリッスンします。使用するポートを変更するには、`rippled.cfg`ファイル内の該当するスタンザを編集します。 例: @@ -172,6 +172,6 @@ XRP Ledgerで使用できるように、`rippled`サーバーをピアツーピ -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/networks-and-servers/peer-protocol.md b/content/concepts/networks-and-servers/peer-protocol.md index 93f0de4f79..6dae2b1783 100644 --- a/content/concepts/networks-and-servers/peer-protocol.md +++ b/content/concepts/networks-and-servers/peer-protocol.md @@ -17,11 +17,11 @@ The peer protocol is the main mode of communication between servers in the XRP L - Requesting ledger data from historical ledgers, or providing that data. - Proposing a set of transactions for consensus, or sharing the calculated outcome of applying a consensus transaction set. -To set up a peer-to-peer connection, one server connects to another using HTTPS and requests an [HTTP upgrade](https://tools.ietf.org/html/rfc7230#section-6.7) to switch to the `XRPL/2.0` protocol (formerly `RTXP/1.2`). (For more information, see the [Overlay Network](https://github.com/ripple/rippled/blob/96bbabbd2ece106779bb544aa0e4ce174e99fdf6/src/ripple/overlay/README.md#handshake) article in the [`rippled` repository](https://github.com/ripple/rippled).) +To set up a peer-to-peer connection, one server connects to another using HTTPS and requests an [HTTP upgrade](https://tools.ietf.org/html/rfc7230#section-6.7) to switch to the `XRPL/2.0` protocol (formerly `RTXP/1.2`). (For more information, see the [Overlay Network](https://github.com/XRPLF/rippled/blob/96bbabbd2ece106779bb544aa0e4ce174e99fdf6/src/ripple/overlay/README.md#handshake) article in the [`rippled` repository](https://github.com/ripple/rippled).) ## Peer Discovery -The XRP Ledger uses a "gossip" protocol to help find servers find others to connect to in the XRP Ledger network. Whenever a server starts up, it reconnects to any other peers it previously connected to. As a fallback, it uses the [hardcoded public hubs](https://github.com/ripple/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525). After a server successfully connects to a peer, it asks that peer for the contact information (generally, IP address and port) of other XRP Ledger servers that may also be seeking peers. The server can then connect to those servers, and ask them for the contact information of yet more XRP Ledger servers to peer with. Through this process, the server makes enough peer connections that it can remain reliably connected to the rest of the network even if it loses a connection to any single peer. +The XRP Ledger uses a "gossip" protocol to help find servers find others to connect to in the XRP Ledger network. Whenever a server starts up, it reconnects to any other peers it previously connected to. As a fallback, it uses the [hardcoded public hubs](https://github.com/XRPLF/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525). After a server successfully connects to a peer, it asks that peer for the contact information (generally, IP address and port) of other XRP Ledger servers that may also be seeking peers. The server can then connect to those servers, and ask them for the contact information of yet more XRP Ledger servers to peer with. Through this process, the server makes enough peer connections that it can remain reliably connected to the rest of the network even if it loses a connection to any single peer. Typically, a server needs to connect to a public hub only once, for a short amount of time, to find other peers. After doing so, the server may or may not remain connected to the hub, depending on how stable its network connection is, how busy the hub is, and how many other high-quality peers the server finds. The server saves the addresses of these other peers so it can try reconnecting directly to those peers later, after a network outage or a restart. @@ -36,7 +36,7 @@ To participate in the XRP Ledger, `rippled` servers connect to arbitrary peers u Ideally, the server should be able to send _and_ receive connections on the peer port. You should [forward the port used for the peer protocol through your firewall](forward-ports-for-peering.html) to the `rippled` server. -IANA [has assigned port **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) for the XRP Ledger peer protocol, but for compatibility with legacy systems, the [default `rippled` config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on **port 51235** on all network interfaces. If you run a server, you can configure which port(s) your server listens on using the `rippled.cfg` file. +IANA [has assigned port **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) for the XRP Ledger peer protocol, but for compatibility with legacy systems, the [default `rippled` config file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on **port 51235** on all network interfaces. If you run a server, you can configure which port(s) your server listens on using the `rippled.cfg` file. Example: @@ -172,6 +172,6 @@ To configure your server as a private server, set the `[peer_private]` setting t -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/tokens/offers.ja.md b/content/concepts/tokens/offers.ja.md index e6d830a651..56914a3956 100644 --- a/content/concepts/tokens/offers.ja.md +++ b/content/concepts/tokens/offers.ja.md @@ -80,7 +80,7 @@ Offerオブジェクトは、他のオファーやクロスカレンシー決済 台帳内のOfferオブジェクトは取引レートによってグループにまとめられます。取引レートは、`TakerGets`と`TakerPays`の比率として計算されます。取引レートが高いOfferオブジェクトが優先的に処理されます。（つまり、オファーを約定する人は、支払われる通貨額に対して可能な限り多くの額を受領します。）同じ取引レートのオファーは、オファーの作成タイミングを基準にして処理されます。 -同じ取引レートのOfferオブジェクトが同じ台帳ブロックに記録されている場合、オファーの処理順序は[レジャーへトランザクションを適用する](https://github.com/ripple/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source Code: Applying transactions")ための[正規順序](https://github.com/ripple/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source Code: Transaction ordering")によって決定します。この動作は確定的かつ効率的であり、操作することが困難であるように設計されています。 +同じ取引レートのOfferオブジェクトが同じ台帳ブロックに記録されている場合、オファーの処理順序は[レジャーへトランザクションを適用する](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source Code: Applying transactions")ための[正規順序](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source Code: Transaction ordering")によって決定します。この動作は確定的かつ効率的であり、操作することが困難であるように設計されています。 ## オファーの有効期限 diff --git a/content/concepts/tokens/offers.md b/content/concepts/tokens/offers.md index 093e499365..b572e136b4 100644 --- a/content/concepts/tokens/offers.md +++ b/content/concepts/tokens/offers.md @@ -84,7 +84,7 @@ Trust line limits protect you from receiving more of a token as payment than you Existing Offers are grouped by exchange rate, which is measured as the ratio between `TakerGets` and `TakerPays`. Offers with a higher exchange rate are taken preferentially. (That is, the person accepting the offer receives as much as possible for the amount of currency they pay out.) Offers with the same exchange rate are taken on the basis of which offer was placed first. -When Offers execute in the same ledger block, the order in which they execute is determined by the [canonical order](https://github.com/ripple/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source code: Transaction ordering") in which the transactions were [applied to the ledger](https://github.com/ripple/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source code: Applying transactions"). This behavior is designed to be deterministic, efficient, and hard to game. +When Offers execute in the same ledger block, the order in which they execute is determined by the [canonical order](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source code: Transaction ordering") in which the transactions were [applied to the ledger](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source code: Applying transactions"). This behavior is designed to be deterministic, efficient, and hard to game. ## Offer Expiration diff --git a/content/concepts/tokens/trust-lines-and-issuing.ja.md b/content/concepts/tokens/trust-lines-and-issuing.ja.md index 2e17f87932..5d1a8b4d78 100644 --- a/content/concepts/tokens/trust-lines-and-issuing.ja.md +++ b/content/concepts/tokens/trust-lines-and-issuing.ja.md @@ -59,7 +59,7 @@ labels: **Authorized** の設定は、一度オンにするとオフにできないため、トラストラインの初期状態にはカウントされません。 ## Free Trust Lines -[[Source]](https://github.com/ripple/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) +[[Source]](https://github.com/XRPLF/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) トラストラインはXRP Ledgerの強力な機能であるため、アカウントの最初の2つのトラストラインを「無料」にする特別な機能が用意されています。 @@ -78,7 +78,7 @@ labels: - [gateway_balancesメソッド][] - 発行者の発行残高を確認 - [RippleStateオブジェクト](ripplestate.html) - 台帳の状態データのうち、トラストラインのデータ形式 - [TrustSetトランザクション][] - トラストラインを作成・変更するトランザクション - - + - {% include '_snippets/rippled-api-links.md' %} {% include '_snippets/tx-type-links.md' %} diff --git a/content/concepts/tokens/trust-lines-and-issuing.md b/content/concepts/tokens/trust-lines-and-issuing.md index 8be3a21fa0..540a1d0021 100644 --- a/content/concepts/tokens/trust-lines-and-issuing.md +++ b/content/concepts/tokens/trust-lines-and-issuing.md @@ -63,7 +63,7 @@ If your balance is negative (you are the issuer) or the other side's settings ar Since the **Authorized** setting cannot be turned off after it has been turned on, it does not count toward the trust line's default state. ### Free Trust Lines -[[Source]](https://github.com/ripple/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) +[[Source]](https://github.com/XRPLF/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) Since trust lines are a powerful feature of the XRP Ledger, there is a special feature to make an account's first two trust lines "free". diff --git a/content/concepts/transactions/set-up-secure-signing.ja.md b/content/concepts/transactions/set-up-secure-signing.ja.md index 94a4f116e1..5c7bd4124a 100644 --- a/content/concepts/transactions/set-up-secure-signing.ja.md +++ b/content/concepts/transactions/set-up-secure-signing.ja.md @@ -46,7 +46,7 @@ labels: 2. トランザクションに署名する必要がある場合は、`localhost`または`127.0.0.1`のサーバーに接続します。シングル署名の場合は[signメソッド][]、マルチシグの場合は[sign_forメソッド][]を使用します。 - [構成ファイルの例](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 + [構成ファイルの例](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 **注意:** 署名に[コマンドラインAPI](request-formatting.html#コマンドライン形式)を使用する場合は、コマンドラインでないクライアントで[Websocket APIやJSON-RPC APIを使用](get-started-using-http-websocket-apis.html)する場合よりもセキュリティが弱くなります。コマンドライン構文を使用すると、秘密鍵がシステムのプロセスリストで他のユーザーに見える可能性があり、シェル履歴にプレーンテキスト形式でキーが保存される可能性があります。 @@ -78,7 +78,7 @@ labels: - [設定](get-started-using-javascript.html) - [APIリファレンス](https://js.xrpl.org/) - **Signing Library for C++**（`rippled`に付属） - - [ドキュメント](https://github.com/ripple/rippled/tree/develop/Builds/linux#signing-library) + - [ドキュメント](https://github.com/XRPLF/rippled/tree/develop/Builds/linux#signing-library) Rippleが公開したものでないクライアントライブラリを使用する場合は、そのライブラリが実装している署名アルゴリズムの実装が適切で安全であることを確認してください。（例えば、クライアントライブラリがデフォルトのECDSAアルゴリズムを使用している場合は、そのライブラリは[RFC6979](https://tools.ietf.org/html/rfc6979)に記載されているとおりに決定論的ノンスを使用している必要があります。)Rippleが公開している上記のすべてのライブラリは、業界のベストプラクティスに従っています。 @@ -148,6 +148,6 @@ Rippleが公開したものでないクライアントライブラリを使用 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/transactions/set-up-secure-signing.md b/content/concepts/transactions/set-up-secure-signing.md index 49cb4b38da..e695b3998b 100644 --- a/content/concepts/transactions/set-up-secure-signing.md +++ b/content/concepts/transactions/set-up-secure-signing.md @@ -44,7 +44,7 @@ In this configuration, you run `rippled` on the machine that generates the trans 2. When you need to sign transactions, connect to your server on `localhost` or `127.0.0.1`. Use the [sign method][] (for single signatures) or [sign_for method][] (for multi-signatures). - The [example config file](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. + The [example config file](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. **Caution:** Using the [commandline API](request-formatting.html#commandline-format) for signatures is less secure than [using the Websocket or JSON-RPC APIs](get-started-using-http-websocket-apis.html) through non-commandline clients. When using the commandline syntax, your secret key may be visible to other users in the system's process listing, and your shell history may save the key in plain text. @@ -91,7 +91,7 @@ To optimize the security of your signing library: Here are examples of how to sign transaction instructions locally using the following languages and libraries: -* **JavaScript** / **TypeScript** - [`xrpl.js`](https://github.com/XRPLF/xrpl.js) +* **JavaScript** / **TypeScript** - [`xrpl.js`](https://github.com/XRPLF/xrpl.js) * **Python** - [`xrpl-py`](https://github.com/XRPLF/xrpl-py) @@ -158,6 +158,6 @@ To use this configuration, follow the steps for [running `rippled` on a private -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/transactions/transaction-cost.ja.md b/content/concepts/transactions/transaction-cost.ja.md index b2fc109406..f658950beb 100644 --- a/content/concepts/transactions/transaction-cost.ja.md +++ b/content/concepts/transactions/transaction-cost.ja.md @@ -63,7 +63,7 @@ XRP LedgerをスパムやDoS攻撃から守るため、各トランザクショ オープンレジャーコストの水準は、絶対的なトランザクションコストではなく[標準的なトランザクションコストに比例](#手数料レベル)しています。標準よりも高い要件を持つトランザクションタイプ（[マルチシグトランザクション](multi-signing.html)など）は、オープンレジャーコストを満たすために最低限のトランザクションコスト要件を持つトランザクションよりも多く支払う必要があります。 -関連項目: [`rippled`リポジトリー内のFee Escalationの説明](https://github.com/ripple/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md)。 +関連項目: [`rippled`リポジトリー内のFee Escalationの説明](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md)。 ### キューに入れられたトランザクション @@ -176,6 +176,6 @@ XRP Ledgerは、XRPの価値が長期的に変化することを見越して、 - [SetFee疑似トランザクション][] -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/concepts/transactions/transaction-cost.md b/content/concepts/transactions/transaction-cost.md index daa9187c18..d8da8161f4 100644 --- a/content/concepts/transactions/transaction-cost.md +++ b/content/concepts/transactions/transaction-cost.md @@ -62,7 +62,7 @@ For each new ledger version, the server picks a soft limit on the number of tran The open ledger cost requirement is [proportional to the normal cost of the transaction](#fee-levels), not the absolute transaction cost. Transaction types that have a higher-than-normal requirement, such as [multi-signed transactions](multi-signing.html) must pay more to meet the open ledger cost than transactions which have minimum transaction cost requirements. -See also: [Fee Escalation explanation in `rippled` repository](https://github.com/ripple/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md). +See also: [Fee Escalation explanation in `rippled` repository](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md). ### Queued Transactions @@ -174,6 +174,6 @@ The XRP Ledger has a mechanism for changing the minimum transaction cost to acco - [SetFee pseudo-transaction][] -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/infrastructure/rippled/configuration/configure-history-sharding.ja.md b/content/infrastructure/rippled/configuration/configure-history-sharding.ja.md index 9b6f50cdfb..e5a9ba10a2 100644 --- a/content/infrastructure/rippled/configuration/configure-history-sharding.ja.md +++ b/content/infrastructure/rippled/configuration/configure-history-sharding.ja.md @@ -45,7 +45,7 @@ max_size_gb=50 **注意:** `rippled`がシャードストアーパスで不適切なデータを検出すると、[起動できない](server-wont-start.html)可能性があります。シャードストアーには新しいフォルダーを使用する必要があります。以前にRocksDBシャードストアー（`rippled` 1.2.x以前）を使用していた場合は、別のパスを使用するか、RocksDBシャードデータを削除します。 -詳細は、[rippled.cfgの設定例](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg)の`[shard_db]`の例を参照してください。 +詳細は、[rippled.cfgの設定例](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)の`[shard_db]`の例を参照してください。 ## 3. サーバーの再起動 diff --git a/content/infrastructure/rippled/configuration/configure-history-sharding.md b/content/infrastructure/rippled/configuration/configure-history-sharding.md index 568b842c73..0f53359c1f 100644 --- a/content/infrastructure/rippled/configuration/configure-history-sharding.md +++ b/content/infrastructure/rippled/configuration/configure-history-sharding.md @@ -52,7 +52,7 @@ The `type` field of `[shard_db]` can be omitted. If present, it _MUST_ be `NuDB` **Caution:** If `rippled` detects the wrong type of data in the shard store path, it may [fail to start](server-wont-start.html). You should use a new folder for the shard store. If you previously used a RocksDB shard store (`rippled` 1.2.x and lower), use a different path or delete the RocksDB shard data. -For more information, reference the `[shard_db]` example in the [rippled.cfg configuration example](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg). +For more information, reference the `[shard_db]` example in the [rippled.cfg configuration example](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg). ## 3. Restart the server diff --git a/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.ja.md b/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.ja.md index 55fab2cda1..8ba00df322 100644 --- a/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.ja.md +++ b/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.ja.md @@ -36,7 +36,7 @@ top_nav_name: UNLに参加しよう - **合意** - 優れたバリデータの投票は、可能な限り高い頻度で、コンセンサスプロセスの結果と合致します。これに該当しない場合は、バリデータのソフトウェアが最新のものではないか、不具合があるか、意図的な偏りがあることを示唆している可能性があります。常に[最新の`rippled`リリース](https://github.com/ripple/rippled/tree/master)を、修正を加えることなく実行します。新規リリースについて知るために、[`rippled`のリリースを確認](https://github.com/ripple/rippled/releases)してください。 + 優れたバリデータの投票は、可能な限り高い頻度で、コンセンサスプロセスの結果と合致します。これに該当しない場合は、バリデータのソフトウェアが最新のものではないか、不具合があるか、意図的な偏りがあることを示唆している可能性があります。常に[最新の`rippled`リリース](https://github.com/XRPLF/rippled/tree/master)を、修正を加えることなく実行します。新規リリースについて知るために、[`rippled`のリリースを確認](https://github.com/XRPLF/rippled/releases)してください。 - **適時の投票** @@ -46,7 +46,7 @@ top_nav_name: UNLに参加しよう 優れたバリデータには、身元が明確な所有者が存在します。[ドメイン検証](#6-ドメイン検証の提供)を提供することは、その第一歩になります。XRP LedgerネットワークのUNLに、多くの法的な管轄域および地域のさまざまな所有者によって運営されているバリデータが含まれていると理想的です。結果として、信頼できるバリデータの公正な運用が地域特有の事象によって損なわれるおそれが低減されます。 -Ripple社は、推奨される一連のバリデータを記載した[バリデータリスト](https://github.com/ripple/rippled/blob/develop/cfg/validators-example.txt)を公開しています。本番環境のサーバーでは、このリストを使用することを強くお勧めします。 +Ripple社は、推奨される一連のバリデータを記載した[バリデータリスト](https://github.com/XRPLF/rippled/blob/develop/cfg/validators-example.txt)を公開しています。本番環境のサーバーでは、このリストを使用することを強くお勧めします。 @@ -143,7 +143,7 @@ Ripple社は、推奨される一連のバリデータを記載した[バリデ この構成では、[検出されたピア](peer-protocol.html#ピアの検出)を使用してバリデータをXRP Ledgerネットワークに接続します。これは`rippled`サーバーのデフォルトの動作です。 -_**検出されたピアを使用してバリデータをXRP Ledgerネットワークに接続するには、**_ バリデータの`rippled.cfg`ファイルで`[peer_private]`スタンザを省略するか、それを`0`に設定します。この構成の[サンプルのrippled.cfgファイル](https://github.com/ripple/rippled/blob/develop/cfg/rippled-example.cfg)が提供されています。 +_**検出されたピアを使用してバリデータをXRP Ledgerネットワークに接続するには、**_ バリデータの`rippled.cfg`ファイルで`[peer_private]`スタンザを省略するか、それを`0`に設定します。この構成の[サンプルのrippled.cfgファイル](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg)が提供されています。 ### プロキシを使用した接続 @@ -306,6 +306,6 @@ _**公開ハブを使用してバリデータをネットワークに接続す -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.md b/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.md index dd5a4b82ac..3d0881d61c 100644 --- a/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.md +++ b/content/infrastructure/rippled/configuration/run-rippled-as-a-validator.md @@ -147,7 +147,7 @@ For a comparison of these approaches, see [Pros and Cons of Peering Configuratio This configuration connects your validator to the XRP Ledger network using [discovered peers](peer-protocol.html#peer-discovery). This is the default behavior for `rippled` servers. -_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/ripple/rippled/blob/develop/cfg/rippled-example.cfg) is delivered with this configuration. +_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) is delivered with this configuration. ### Connect using proxies @@ -280,6 +280,6 @@ For information about how to revoke a master key pair you generated for your val -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.ja.md b/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.ja.md index ae6099cb6f..f43f6160dc 100644 --- a/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.ja.md +++ b/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.ja.md @@ -30,7 +30,7 @@ labels: 各応答の`validation_seed`パラメーターと`validation_public_key`パラメーターを安全な場所に保存します。 -3. 各サーバーで[構成ファイル](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg)を編集し、以下のセクションを変更します。 +3. 各サーバーで[構成ファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)を編集し、以下のセクションを変更します。 1. `[ips_fixed]`セクションに、クラスターの _その他の_ 各メンバーのIPアドレスとポートを記入します。各サーバーのポート番号は、サーバーの `rippled.cfg`に指定されている`protocol = peer`ポート（通常は51235）と一致している必要があります。例: diff --git a/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.md b/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.md index ba555ad27b..d278207090 100644 --- a/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.md +++ b/content/infrastructure/rippled/configure-peering/cluster-rippled-servers.md @@ -30,7 +30,7 @@ If you run multiple [`rippled` servers](xrpl-servers.html) in the same data cent Save the `validation_seed` and `validation_public_key` parameters from each response somewhere secure. -3. On each server, edit the [config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg), modifying the following sections: +3. On each server, edit the [config file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg), modifying the following sections: 1. In the `[ips_fixed]` section, list the IP address and port of each _other_ member of the cluster. For each of those servers, the port number should match the `protocol = peer` port (usually 51235) from that server's `rippled.cfg`. For example: diff --git a/content/infrastructure/rippled/installation/capacity-planning.ja.md b/content/infrastructure/rippled/installation/capacity-planning.ja.md index a34146109e..7b1c95734d 100644 --- a/content/infrastructure/rippled/installation/capacity-planning.ja.md +++ b/content/infrastructure/rippled/installation/capacity-planning.ja.md @@ -20,7 +20,7 @@ XRP Ledgerのサーバーの負荷は、複数の要因によって変化しま デフォルトの設定ファイルには、一般的なユースケースを幅広くカバーする設定が含まれています。お使いのハードウェアや使用目的に合わせて設定をカスタマイズすることで、より良いパフォーマンスを得ることができます。 -本セクションでの設定は、`rippled.cfg`ファイルのパラメータです。設定ファイルの例である `rippled-example.cfg` は、`rippled` GitHubリポジトリ の [`cfg` ディレクトリ](https://github.com/ripple/rippled/blob/develop/cfg/rippled-example.cfg)からアクセスできます。サンプル設定ファイルの設定は、サーバーと一緒にインストールされたデフォルトの設定と一致しています。 +本セクションでの設定は、`rippled.cfg`ファイルのパラメータです。設定ファイルの例である `rippled-example.cfg` は、`rippled` GitHubリポジトリ の [`cfg` ディレクトリ](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg)からアクセスできます。サンプル設定ファイルの設定は、サーバーと一緒にインストールされたデフォルトの設定と一致しています。 ### ノードサイズ diff --git a/content/infrastructure/rippled/installation/capacity-planning.md b/content/infrastructure/rippled/installation/capacity-planning.md index ccf8bc074e..dbf5ad8985 100644 --- a/content/infrastructure/rippled/installation/capacity-planning.md +++ b/content/infrastructure/rippled/installation/capacity-planning.md @@ -20,7 +20,7 @@ You should consider these factors to ensure that your server has the capacity to The default configuration file contains settings for a broad range of common use cases. You can get better performance by customizing the settings for your specific hardware and intended usage pattern. -The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/ripple/rippled/blob/develop/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server. +The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server. ### Node Size diff --git a/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.ja.md b/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.ja.md index 9a3c1dfddf..53079056e4 100644 --- a/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.ja.md +++ b/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.ja.md @@ -61,8 +61,8 @@ labels: `rippled`の開発バージョンまたはプレリリースバージョンにアクセスするには、`stable`ではなく次のいずれかを使用します。 - - `unstable` - プレインストールビルド（[`release`ブランチ](https://github.com/ripple/rippled/tree/release)） - - `nightly` - 実験/開発ビルド（[`develop`ブランチ](https://github.com/ripple/rippled/tree/develop)） + - `unstable` - プレインストールビルド（[`release`ブランチ](https://github.com/XRPLF/rippled/tree/release)） + - `nightly` - 実験/開発ビルド（[`develop`ブランチ](https://github.com/XRPLF/rippled/tree/develop)） **警告:** 安定版ではないナイトリービルドはいつの時点でも壊れる可能性があります。これらのビルドを本番環境のサーバーに使用しないでください。 diff --git a/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.md b/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.md index 5f960bc97a..dbd9061a35 100644 --- a/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.md +++ b/content/infrastructure/rippled/installation/install-rippled-on-ubuntu.md @@ -62,8 +62,8 @@ Before you install `rippled`, you must meet the [System Requirements](system-req If you want access to development or pre-release versions of `rippled`, use one of the following instead of `stable`: - - `unstable` - Pre-release builds ([`release` branch](https://github.com/ripple/rippled/tree/release)) - - `nightly` - Experimental/development builds ([`develop` branch](https://github.com/ripple/rippled/tree/develop)) + - `unstable` - Pre-release builds ([`release` branch](https://github.com/XRPLF/rippled/tree/release)) + - `nightly` - Experimental/development builds ([`develop` branch](https://github.com/XRPLF/rippled/tree/develop)) **Warning:** Unstable and nightly builds may be broken at any time. Do not use these builds for production servers. diff --git a/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.ja.md b/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.ja.md index 687933b87b..536f6098c9 100644 --- a/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.ja.md +++ b/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.ja.md @@ -12,7 +12,7 @@ blurb: rippled 1.2.4以前のバージョンからrippled v1.3以降に移行す - [CentOSまたはRed Hat Enterprise Linux（RHEL）](#centosまたはred-hat-enterprise-linuxrhelでの移行) - [Ubuntu Linux](#ubuntu-linuxでの移行) -その他のプラットフォームについては、ソースからコンパイルするためのアップデート手順を参照してください。（[Ubuntu](build-run-rippled-ubuntu.html)、[macOS](build-run-rippled-macos.html)、または[Windows](https://github.com/ripple/rippled/tree/develop/Builds/VisualStudio2017)） +その他のプラットフォームについては、ソースからコンパイルするためのアップデート手順を参照してください。（[Ubuntu](build-run-rippled-ubuntu.html)、[macOS](build-run-rippled-macos.html)、または[Windows](https://github.com/XRPLF/rippled/tree/develop/Builds/VisualStudio2017)） ## CentOSまたはRed Hat Enterprise Linux（RHEL）での移行 @@ -91,7 +91,7 @@ Rippleの公式RPMリポジトリとそれを使用するための手順が変 ## 関連項目 -- **[`rippled` v1.3.1リリースノート](https://github.com/ripple/rippled/releases/1.3.1)** +- **[`rippled` v1.3.1リリースノート](https://github.com/XRPLF/rippled/releases/1.3.1)** - **コンセプト:** - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](consensus.html) diff --git a/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.md b/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.md index 5586cea6d8..0437319c40 100644 --- a/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.md +++ b/content/infrastructure/rippled/installation/rippled-1-3-migration-instructions.md @@ -13,7 +13,7 @@ This document provides migration steps for upgrading on supported platforms: - [CentOS or Red Hat Enterprise Linux (RHEL)](#migration-on-centos-or-red-hat-enterprise-linux-rhel) - [Ubuntu Linux](#migration-on-ubuntu-linux) -For other platforms, see the updated instructions for compiling from source. ([Ubuntu](build-run-rippled-ubuntu.html), [macOS](build-run-rippled-macos.html), or [Windows](https://github.com/ripple/rippled/tree/develop/Builds/VisualStudio2017)) +For other platforms, see the updated instructions for compiling from source. ([Ubuntu](build-run-rippled-ubuntu.html), [macOS](build-run-rippled-macos.html), or [Windows](https://github.com/XRPLF/rippled/tree/develop/Builds/VisualStudio2017)) ## Migration on CentOS or Red Hat Enterprise Linux (RHEL) @@ -92,7 +92,7 @@ The `rippled` v1.3 package includes an updated auto-update script that works on ## See Also -- **[`rippled` v1.3.1 Release Notes](https://github.com/ripple/rippled/releases/1.3.1)** +- **[`rippled` v1.3.1 Release Notes](https://github.com/XRPLF/rippled/releases/1.3.1)** - **Concepts:** - [The `rippled` Server](xrpl-servers.html) - [Consensus](consensus.html) diff --git a/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.ja.md b/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.ja.md index b6302ecac7..b4c6c386fa 100644 --- a/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.ja.md +++ b/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.ja.md @@ -17,7 +17,7 @@ rippled -a --start --conf=/path/to/rippled.cfg スタンドアロンモードで`rippled`を起動時に使用できるオプションについての詳細は、[コマンドラインの使用リファレンスのスタンドアロンモードのオプション](commandline-usage.html#スタンドアロンモードのオプション)を参照してください。 -ジェネシスレジャーの[ジェネシスアドレス](accounts.html#特別なアドレス)は1,000億XRPすべてを保有しています。ジェネシスアドレスのキーは以下のように[ハードコーディング](https://github.com/ripple/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 +ジェネシスレジャーの[ジェネシスアドレス](accounts.html#特別なアドレス)は1,000億XRPすべてを保有しています。ジェネシスアドレスのキーは以下のように[ハードコーディング](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 **アドレス:** `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` @@ -30,6 +30,6 @@ rippled -a --start --conf=/path/to/rippled.cfg デフォルトでは、新しいジェネシスレジャーでは[Amendment](amendments.html)が有効になっていません。`--start`を使用して新しいジェネシスレジャーを開始する場合、ジェネシスレジャーには、構成ファイルで明示的に無効にされたAmendmentを除き、`rippled`サーバーでネイティブにサポートされているすべてのAmendmentを有効にする[EnableAmendment疑似トランザクション](enableamendment.html)が含まれています。これらのAmendmentの効果は、直後のレジャーバージョンから反映されます。（留意事項: スタンドアロンモードでは[レジャーを手動で進める](advance-the-ledger-in-stand-alone-mode.html)必要があります。）[新規: rippled 0.50.0][] -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md b/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md index 09f09f44df..1e4af3de29 100644 --- a/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md +++ b/content/infrastructure/rippled/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md @@ -17,7 +17,7 @@ rippled -a --start --conf=/path/to/rippled.cfg For more information on the options you can use when starting `rippled` in stand-alone mode, see [Commandline Usage: Stand-Alone Mode Options](commandline-usage.html#stand-alone-mode-options). -In a genesis ledger, the [genesis address](addresses.html#special-addresses) holds all 100 billion XRP. The keys of the genesis address are [hardcoded](https://github.com/ripple/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184) as follows: +In a genesis ledger, the [genesis address](addresses.html#special-addresses) holds all 100 billion XRP. The keys of the genesis address are [hardcoded](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184) as follows: **Address:** `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` @@ -45,6 +45,6 @@ By default, a new genesis ledger has no [amendments](amendments.html) enabled. I - [Contribute Code to the XRP Ledger](contribute-code-to-rippled.html) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/infrastructure/rippled/troubleshooting/diagnosing-problems.ja.md b/content/infrastructure/rippled/troubleshooting/diagnosing-problems.ja.md index 8d56412717..1ece49d1fe 100644 --- a/content/infrastructure/rippled/troubleshooting/diagnosing-problems.ja.md +++ b/content/infrastructure/rippled/troubleshooting/diagnosing-problems.ja.md @@ -85,7 +85,7 @@ rippled server_info - ピアの数が0の場合、サーバーがネットワークに接続できないか、またはシステムクロックが正しくない可能性があります。（サーバーのクロックを同期するため、すべてのサーバーで[NTP](http://www.ntp.org/)デーモンを実行することが推奨されます。） - - ピアの数が10の場合、`rippled`が[NAT](https://en.wikipedia.org/wiki/Network_address_translation)を使用したルーター経由での着信接続を受信できていない可能性があります。接続を改善するには、ルーターのファイアウォールがピアツーピア接続に使用するポート（[デフォルトでは](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)ポート51235）を転送するように設定します。 + - ピアの数が10の場合、`rippled`が[NAT](https://en.wikipedia.org/wiki/Network_address_translation)を使用したルーター経由での着信接続を受信できていない可能性があります。接続を改善するには、ルーターのファイアウォールがピアツーピア接続に使用するポート（[デフォルトでは](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)ポート51235）を転送するように設定します。 ### サーバーから応答がない場合 @@ -108,7 +108,7 @@ rippled server_info ## サーバーログの確認 -[デフォルトでは](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)`rippled`はサーバーのデバッグログを`/var/log/rippled/debug.log`ファイルに書き込みます。このデバッグログの位置は、サーバーの構成ファイルにより異なる可能性があります。`rippled`サービスを（`systemctl`または`service`を使用して開始するのではなく）直接開始した場合、デフォルトではログメッセージはコンソールにも出力されます。 +[デフォルトでは](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)`rippled`はサーバーのデバッグログを`/var/log/rippled/debug.log`ファイルに書き込みます。このデバッグログの位置は、サーバーの構成ファイルにより異なる可能性があります。`rippled`サービスを（`systemctl`または`service`を使用して開始するのではなく）直接開始した場合、デフォルトではログメッセージはコンソールにも出力されます。 デフォルトの構成ファイルでは、起動時に[log_levelメソッド][]を内部で使用して、すべてのログメッセージカテゴリーでログレベルの重大度は「警告」に設定されています。デバッグログの詳細レベルを制御するには、[起動時に`--silent`コマンドラインオプションを使用し](commandline-usage.html#詳細レベルのオプション)、サーバーの稼働中に[log_levelメソッド][]を使用します。（設定については構成ファイルの`[rpc_startup]`スタンザを参照してください。） diff --git a/content/infrastructure/rippled/troubleshooting/diagnosing-problems.md b/content/infrastructure/rippled/troubleshooting/diagnosing-problems.md index 7e1a48f19d..be56e7c4d3 100644 --- a/content/infrastructure/rippled/troubleshooting/diagnosing-problems.md +++ b/content/infrastructure/rippled/troubleshooting/diagnosing-problems.md @@ -89,7 +89,7 @@ For troubleshooting purposes, the most important fields are (from most commonly - If you have 0 peers, your server may be unable to contact the network, or your system clock may be wrong. (Ripple recommends running an [NTP](http://www.ntp.org/) daemon on all servers to keep their clocks synced.) - - If you have exactly 10 peers, that may indicate that your `rippled` is unable to receive incoming connections through a router using [NAT](https://en.wikipedia.org/wiki/Network_address_translation). You can improve connectivity by configuring your router's firewall to forward the port used for peer-to-peer connections (port 51235 [by default](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)). + - If you have exactly 10 peers, that may indicate that your `rippled` is unable to receive incoming connections through a router using [NAT](https://en.wikipedia.org/wiki/Network_address_translation). You can improve connectivity by configuring your router's firewall to forward the port used for peer-to-peer connections (port 51235 [by default](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)). ### No Response from Server @@ -113,7 +113,7 @@ This generally indicates one of several problems: ## Check the server log -[By default,](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) `rippled` writes the server's debug log to the file `/var/log/rippled/debug.log`. The location of the debug log can differ based on your server's config file. If you start the `rippled` service directly (instead of using `systemctl` or `service` to start it), it also prints log messages to the console by default. +[By default,](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) `rippled` writes the server's debug log to the file `/var/log/rippled/debug.log`. The location of the debug log can differ based on your server's config file. If you start the `rippled` service directly (instead of using `systemctl` or `service` to start it), it also prints log messages to the console by default. The default config file sets the log level to severity "warning" for all categories of log messages by internally using the [log_level method][] during startup. You can control the verbosity of the debug log [using the `--silent` commandline option during startup](commandline-usage.html#verbosity-options) and with the [log_level method][] while the server is running. (See the `[rpc_startup]` stanza of the config file for settings.) @@ -124,9 +124,9 @@ For a more thorough explanation of various types of log messages, see [Understan ## Info Collection Script -If you have problems diagnosing the problem, or you are unable to resolve the problem with any of the common fixes, you may want to ask for help in a support forum or the [GitHub issues](https://github.com/ripple/rippled/issues). When asking for help, you can use an info collection script to gather information about your system to help others diagnose the issue. +If you have problems diagnosing the problem, or you are unable to resolve the problem with any of the common fixes, you may want to ask for help in a support forum or the [GitHub issues](https://github.com/XRPLF/rippled/issues). When asking for help, you can use an info collection script to gather information about your system to help others diagnose the issue. -The official package installation (for [Ubuntu/Debian](install-rippled-on-ubuntu.html) or [CentOS/RedHat](install-rippled-on-centos-rhel-with-yum.html)) installs such a script by default, to `/opt/ripple/bin/getRippledInfo`. [New in: rippled 1.5.0][] If you compiled `rippled` yourself, you can find the same script [in the `rippled` source code repository](https://github.com/ripple/rippled/blob/develop/bin/getRippledInfo). +The official package installation (for [Ubuntu/Debian](install-rippled-on-ubuntu.html) or [CentOS/RedHat](install-rippled-on-centos-rhel-with-yum.html)) installs such a script by default, to `/opt/ripple/bin/getRippledInfo`. [New in: rippled 1.5.0][] If you compiled `rippled` yourself, you can find the same script [in the `rippled` source code repository](https://github.com/XRPLF/rippled/blob/develop/bin/getRippledInfo). To use the script: diff --git a/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.ja.md b/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.ja.md index 21634c0241..d19cbb186c 100644 --- a/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.ja.md +++ b/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.ja.md @@ -27,7 +27,7 @@ SQLiteデータベースの容量は、データベースの_ページサイズ_ いずれの場合でも、問題を検出するには`rippled`のサーバーログへのアクセスが必要です。 -**ヒント:** このデバッグログの位置は、`rippled`サーバーの構成ファイルの設定に応じて異なる可能性があります。[デフォルトの構成](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)では、サーバーのデバッグログは`/var/log/rippled/debug.log`ファイルに書き込まれます。 +**ヒント:** このデバッグログの位置は、`rippled`サーバーの構成ファイルの設定に応じて異なる可能性があります。[デフォルトの構成](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)では、サーバーのデバッグログは`/var/log/rippled/debug.log`ファイルに書き込まれます。 ### 事前の検出 diff --git a/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.md b/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.md index d0c1a9cb9a..11015dc640 100644 --- a/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.md +++ b/content/infrastructure/rippled/troubleshooting/fix-sqlite-tx-db-page-size-issue.md @@ -28,7 +28,7 @@ If your server is vulnerable to this problem, you can detect it two ways: In both cases, detection of the problem requires access to `rippled`'s server logs. -**Tip:** The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) writes the server's debug log to the file `/var/log/rippled/debug.log`. +**Tip:** The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) writes the server's debug log to the file `/var/log/rippled/debug.log`. ### Proactive Detection diff --git a/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.ja.md b/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.ja.md index 389028afc8..4113b42017 100644 --- a/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.ja.md +++ b/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.ja.md @@ -29,7 +29,7 @@ labels: [server_infoメソッド][]で[`server_state`](rippled-server-states.html)が`proposing`または`full`以外の状態であると示され、`server_state_duration_us`が`900000000`（15分のマイクロ秒表記）より大きい場合は、`rippled`サービスをシャットダウンしてから数秒間待ち、再起動してください。場合によっては、マシン全体を再起動します。 -問題が解決しない場合は、このページに記載されている他の原因を確認してください。いずれも当てはまらないと思われる場合は、[`rippled`リポジトリに問題を登録](https://github.com/ripple/rippled/issues)し、「Syncing issue」ラベルを追加します。 +問題が解決しない場合は、このページに記載されている他の原因を確認してください。いずれも当てはまらないと思われる場合は、[`rippled`リポジトリに問題を登録](https://github.com/XRPLF/rippled/issues)し、「Syncing issue」ラベルを追加します。 ## 同期の問題のよくある原因 diff --git a/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.md b/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.md index 68290ed7df..948535904b 100644 --- a/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.md +++ b/content/infrastructure/rippled/troubleshooting/server-doesnt-sync.md @@ -31,7 +31,7 @@ Many syncing issues can be resolved by restarting the server. No matter why it d If the [server_info method][] shows a [`server_state`](rippled-server-states.html) other than `proposing` or `full` and a `server_state_duration_us` of more than `900000000` (15 minutes in microseconds), then you should shut down the `rippled` service, wait a few seconds, and start it again. Optionally, restart the entire machine. -If the problem persists, check the other possibilities listed on this page. If none of them seem to apply, [open an issue in the `rippled` repository](https://github.com/ripple/rippled/issues) and add the "Syncing issue" label. +If the problem persists, check the other possibilities listed on this page. If none of them seem to apply, [open an issue in the `rippled` repository](https://github.com/XRPLF/rippled/issues) and add the "Syncing issue" label. ## Usual Causes of Syncing Issues diff --git a/content/infrastructure/rippled/troubleshooting/server-wont-start.ja.md b/content/infrastructure/rippled/troubleshooting/server-wont-start.ja.md index a3b680cf44..d99b319bd8 100644 --- a/content/infrastructure/rippled/troubleshooting/server-wont-start.ja.md +++ b/content/infrastructure/rippled/troubleshooting/server-wont-start.ja.md @@ -59,7 +59,7 @@ Aborted (core dumped) - `rippled`ユーザーが読み取ることができる構成ファイルを`$HOME/.config/ripple/rippled.cfg`に作成します（`$HOME`は`rippled`ユーザーのホームディレクトリを指しています）。 - **ヒント:** `rippled`リポジトリには、RPMのインストール時にデフォルトの構成として提供される[`rippled.cfg`サンプルファイル](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。 + **ヒント:** `rippled`リポジトリには、RPMのインストール時にデフォルトの構成として提供される[`rippled.cfg`サンプルファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。 - `--conf`[コマンドラインオプション](commandline-usage.html)を使用して、使用する構成ファイルのパスを指定します。 @@ -77,7 +77,7 @@ Aborted (core dumped) - `[validators.txt]`ファイルが存在し、`rippled`ユーザーにこのファイルの読み取り権限があることを確認します。 - **ヒント:** `rippled`リポジトリには、RPMのインストール時にデフォルトの構成として提供される[`validators.txt`サンプルファイル](https://github.com/ripple/rippled/blob/master/cfg/validators-example.txt)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。 + **ヒント:** `rippled`リポジトリには、RPMのインストール時にデフォルトの構成として提供される[`validators.txt`サンプルファイル](https://github.com/XRPLF/rippled/blob/master/cfg/validators-example.txt)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。 - `rippled.cfg`ファイルを編集し、`[validators_file]`設定を変更して、`validators.txt`ファイル（またはこれに相当するファイル）の正しいパスを指定します。ファイル名の前後に余分な空白があるかどうかを確認します。 diff --git a/content/infrastructure/rippled/troubleshooting/server-wont-start.md b/content/infrastructure/rippled/troubleshooting/server-wont-start.md index 50c5d38d40..24992c1b7e 100644 --- a/content/infrastructure/rippled/troubleshooting/server-wont-start.md +++ b/content/infrastructure/rippled/troubleshooting/server-wont-start.md @@ -60,7 +60,7 @@ Possible solutions: - Create a config file that can be read by the `rippled` user at `$HOME/.config/ripple/rippled.cfg` (where `$HOME` points to the `rippled` user's home directory). - **Tip:** The `rippled` repository contains [an example `rippled.cfg` file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) which is provided as the default config when you do an RPM installation. If you do not have the file, you can copy it from there. + **Tip:** The `rippled` repository contains [an example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) which is provided as the default config when you do an RPM installation. If you do not have the file, you can copy it from there. - Specify the path to your preferred config file using the `--conf` [commandline option](commandline-usage.html). @@ -78,7 +78,7 @@ Possible solutions: - Check that the `[validators.txt]` file exists and the `rippled` user has permissions to read it. - **Tip:** The `rippled` repository contains [an example `validators.txt` file](https://github.com/ripple/rippled/blob/master/cfg/validators-example.txt) which is provided as the default config when you do an RPM installation. If you do not have the file, you can copy it from there. + **Tip:** The `rippled` repository contains [an example `validators.txt` file](https://github.com/XRPLF/rippled/blob/master/cfg/validators-example.txt) which is provided as the default config when you do an RPM installation. If you do not have the file, you can copy it from there. - Edit your `rippled.cfg` file and modify the `[validators_file]` setting to have the correct path to your `validators.txt` (or equivalent) file. Check for extra whitespace before or after the filename. diff --git a/content/infrastructure/rippled/troubleshooting/understanding-log-messages.ja.md b/content/infrastructure/rippled/troubleshooting/understanding-log-messages.ja.md index f94fdead5c..43bddd0a50 100644 --- a/content/infrastructure/rippled/troubleshooting/understanding-log-messages.ja.md +++ b/content/infrastructure/rippled/troubleshooting/understanding-log-messages.ja.md @@ -168,7 +168,7 @@ ShardStore:ERR shard 2731: No such file or directory ShardStore:ERR shard 2236: No such file or directory ``` -これは、サーバーが新しい履歴シャードの取得を開始しようとしたものの、シャードを格納するための新しいディレクトリーを作成できなかったことを示します。このバグにより、rippled 1.3.1は新しいシャードを取得できません。[修正は近日リリース予定](https://github.com/ripple/rippled/pull/3014)です。 +これは、サーバーが新しい履歴シャードの取得を開始しようとしたものの、シャードを格納するための新しいディレクトリーを作成できなかったことを示します。このバグにより、rippled 1.3.1は新しいシャードを取得できません。[修正は近日リリース予定](https://github.com/XRPLF/rippled/pull/3014)です。 このエラーは、上記のバグのほかに、`rippled`が**起動後**に基となるファイルシステムに書き込めなくなった場合にも起こります。考えられる原因は次のとおりです。 diff --git a/content/infrastructure/rippled/troubleshooting/understanding-log-messages.md b/content/infrastructure/rippled/troubleshooting/understanding-log-messages.md index c05325ccea..54628b2093 100644 --- a/content/infrastructure/rippled/troubleshooting/understanding-log-messages.md +++ b/content/infrastructure/rippled/troubleshooting/understanding-log-messages.md @@ -124,7 +124,7 @@ The following log message indicates that a client to the server's public API has Resource:WRN Consumer entry 169.55.164.21 dropped with balance 15970 at or above drop threshold 15000 ``` -The entry contains the IP address of the client that exceeded its rate limit, and the client's "balance", which is a score estimating the rate at which the client has been using the API. The threshold for dropping a client is [hardcoded to a score of 15000](https://github.com/ripple/rippled/blob/06c371544acc3b488b9d9c057cee4e51f6bef7a2/src/ripple/resource/impl/Tuning.h#L34-L35). +The entry contains the IP address of the client that exceeded its rate limit, and the client's "balance", which is a score estimating the rate at which the client has been using the API. The threshold for dropping a client is [hardcoded to a score of 15000](https://github.com/XRPLF/rippled/blob/06c371544acc3b488b9d9c057cee4e51f6bef7a2/src/ripple/resource/impl/Tuning.h#L34-L35). If you see frequent messages from the same IP address, you may want to block those IP addresses from your network to reduce the load on your server's public API. (For example, you may be able to configure your firewall to block those IP addresses.) diff --git a/content/references/client-libraries.md b/content/references/client-libraries.md index c47ee7398c..7addb37750 100644 --- a/content/references/client-libraries.md +++ b/content/references/client-libraries.md @@ -13,7 +13,7 @@ For other programming languages, you can access the XRP Ledger through the [HTTP |----------|--------------|-------------|---------------|-------------| | **Python** | `xrpl-py` | [Get Started Using Python](get-started-using-python.html) | [API Reference](https://xrpl-py.readthedocs.io/) | [Repo](https://github.com/XRPLF/xrpl-py) | | **JavaScript** / **TypeScript** | `xrpl.js` | [Get Started](get-started-using-javascript.html) | [API Reference](https://js.xrpl.org/) | [Repo](https://github.com/XRPLF/xrpl.js) | -| **C++** | `rippled` Signing Library | [Get Started](https://github.com/ripple/rippled/tree/develop/Builds/linux#signing-library) | | (Part of [`rippled`](https://github.com/ripple/rippled/)) | +| **C++** | `rippled` Signing Library | [Get Started](https://github.com/XRPLF/rippled/tree/develop/Builds/linux#signing-library) | | (Part of [`rippled`](https://github.com/XRPLF/rippled/)) | | **Java** | `xrpl4j` | [Get Started Using Java](get-started-using-java.html) | [API Reference](https://javadoc.io/doc/org.xrpl/) | [Repo](https://github.com/XRPLF/xrpl4j) | **Tip:** To add a client library not listed here, please [suggest changes to this page]({{target.github_forkurl}}/edit/{{target.github_branch}}/content/{{currentpage.md}})! diff --git a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.ja.md b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.ja.md index ece390b0ff..8d1d524019 100644 --- a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # validation_create -[[ソース]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source") `validation_create`コマンドキーを使用して、[`rippled`サーバーがネットワークに対して自身の身元を識別させるのに使用できる暗号鍵](peer-protocol.html#ノードキーペア)を生成します。[wallet_proposeメソッド][]と同様に、このメソッドでは適切なフォーマットで一連のキーが単に生成されるだけです。XRP Ledgerのデータやサーバー構成は変更されません。 diff --git a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md index 15f7902fdd..4e9a1012c5 100644 --- a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md +++ b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md @@ -7,7 +7,7 @@ labels: - Core Server --- # validation_create -[[Source]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source") Use the `validation_create` command to generate [cryptographic keys a `rippled` server can use to identify itself to the network](peer-protocol.html#node-key-pair). Similar to the [wallet_propose method][], this method only generates a set of keys in the proper format. It does not any makes changes to the XRP Ledger data or server configuration. diff --git a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.ja.md b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.ja.md index 4b5d431848..5d9420be43 100644 --- a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.ja.md @@ -7,7 +7,7 @@ labels: - アカウント --- # wallet_propose -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") `wallet_propose`メソッドを使用して、キーペアとXRP Ledgerアドレスを生成します。このコマンドは単にキーとアドレス値を生成し、XRP Ledger自体には何ら影響しません。レジャー上で資金供給済みのアドレスになるには、そのアドレスで、[必要準備金](reserves.html)を満たすのに十分なXRPの[Paymentトランザクションを受け取る](accounts.html#アカウントの作成)必要があります。 diff --git a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md index de2336ab93..eb89d390a8 100644 --- a/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md +++ b/content/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md @@ -7,7 +7,7 @@ labels: - Accounts --- # wallet_propose -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") +[[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](accounts.html#creating-accounts) that provides enough XRP to meet the [reserve requirement](reserves.html). diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.ja.md index b4fadf3566..68f6eb37e5 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # can_delete -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source") `can_delete`メソッドは[指示による削除が有効なオンライン削除](online-deletion.html#指示による削除)を使用する`rippled`サーバーに削除が可能のレジャーバージョンを通知します。指定したレジャーバージョン以前が削除可能になります。指示による削除が有効ではない場合、このメソッドは何も行いません。 diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md index 1ff3277824..af31748952 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # can_delete -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source") The `can_delete` method informs the `rippled` server of the latest ledger version which may be deleted when using [online deletion with advisory deletion enabled](online-deletion.html#advisory-deletion). If advisory deletion is not enabled, this method does nothing. diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.ja.md index a84816ef0b..26116c610c 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.ja.md @@ -7,7 +7,7 @@ labels: --- # crawl_shards -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") 使用可能な[履歴レジャーデータのシャード](history-sharding.html)に関するピアサーバーからの情報を要求します。[新規: rippled 1.2.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md index 08637b011e..31faaac3dc 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # crawl_shards -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") Requests information from peer servers about which [shards of historical ledger data](history-sharding.html) they have available. [New in: rippled 1.2.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.ja.md index 5cf1044bbb..15d9fdf8f4 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # download_shard -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") サーバーに対し、外部ソースから特定の[履歴レジャーデータのシャード](history-sharding.html)をダウンロードするように指示します。`rippled`サーバーで[履歴シャードが保管されるように設定する](configure-history-sharding.html)必要があります。[新規: rippled 1.1.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md index 42bbf81f12..3fdf863a7a 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # download_shard -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") Instructs the server to download a specific [shard of historical ledger data](history-sharding.html) from an external source. Your `rippled` server must be [configured to store history shards](configure-history-sharding.html). [Updated in: rippled 1.6.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.ja.md index 2345575da2..61858d38b9 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.ja.md @@ -6,9 +6,9 @@ labels: - データ保持 --- # ledger_cleaner -[[ソース]](https://github.com/ripple/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source") -`ledger_cleaner`コマンドは[レジャークリーナー](https://github.com/ripple/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner)を制御します。レジャークリーナーは、`rippled`のレジャーデータベースの破損を検出して修復できる非同期メンテナンスプロセスです。 +`ledger_cleaner`コマンドは[レジャークリーナー](https://github.com/XRPLF/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner)を制御します。レジャークリーナーは、`rippled`のレジャーデータベースの破損を検出して修復できる非同期メンテナンスプロセスです。 _`ledger_cleaner`メソッドは、権限のないユーザーは実行できない[管理メソッド](admin-api-methods.html)です。_ diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md index 4616708664..fb4f8365fe 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md @@ -6,9 +6,9 @@ labels: - Data Retention --- # ledger_cleaner -[[Source]](https://github.com/ripple/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source") -The `ledger_cleaner` command controls the [Ledger Cleaner](https://github.com/ripple/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner), an asynchronous maintenance process that can find and repair corruption in `rippled`'s database of ledgers. +The `ledger_cleaner` command controls the [Ledger Cleaner](https://github.com/XRPLF/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner), an asynchronous maintenance process that can find and repair corruption in `rippled`'s database of ledgers. _The `ledger_cleaner` method is an [admin method](admin-api-methods.html) that cannot be run by unprivileged users._ diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.ja.md index 19c883fa21..3611b05fdd 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # ledger_request -[[ソース]](https://github.com/ripple/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source") `ledger_request`コマンドは、サーバーに対し接続しているピアから特定のレジャーバージョンを取得するように指示します。これは、サーバーが直接接続しているピアの1つにそのレジャーが存在している場合にのみ機能します。場合によっては、レジャーを完全に取得するにはこのコマンドを繰り返し実行する必要があります。 diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md index 5fc0f3988e..6d85f7c94a 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # ledger_request -[[Source]](https://github.com/ripple/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source") The `ledger_request` command tells server to fetch a specific ledger version from its connected peers. This only works if one of the server's immediately-connected peers has that ledger. You may need to run the command several times to completely fetch a ledger. diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.ja.md index 42ce9a6e62..589c28c07c 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # log_level -[[ソース]](https://github.com/ripple/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source") `log_level`コマンドは`rippled`サーバーのログ詳細レベルを変更するか、各ログメッセージカテゴリー（_パーティション_）の現在のログレベルを返します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md index f858aebf7a..3fb0dc86a9 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # log_level -[[Source]](https://github.com/ripple/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source") The `log_level` command changes the `rippled` server's logging verbosity, or returns the current logging level for each category (called a _partition_) of log messages. diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.ja.md index a043758a85..0e24dfbba5 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # logrotate -[[ソース]](https://github.com/ripple/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source") `logrotate`コマンドは、ログファイルを閉じて再度開きます。これは、Linuxファイルシステムでのログローテーションを促進することを目的としています。 diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md index 3a796ec8c2..9374065b02 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # logrotate -[[Source]](https://github.com/ripple/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source") The `logrotate` command closes and reopens the log file. This is intended to help with log rotation on Linux file systems. diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.ja.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.ja.md index ce82099b8d..9be60a489c 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.ja.md @@ -6,7 +6,7 @@ labels: - データ保持 --- # node_to_shard -[[ソース]](https://github.com/ripple/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") `{{currentpage.name}}`メソッドは、レジャーストアから[シャードストア](history-sharding.html)へのデータコピーを管理します。データコピーの開始、停止、状態チェックが可能です。 diff --git a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md index f0e69fbf01..fd80518bde 100644 --- a/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md +++ b/content/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md @@ -6,7 +6,7 @@ labels: - Data Retention --- # node_to_shard -[[Source]](https://github.com/ripple/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") The `{{currentpage.name}}` method manages copying data from the ledger store to the [shard store](history-sharding.html). It can start, stop, or check the status of copying the data. diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.ja.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.ja.md index 1e0b22ded8..230ea6688b 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # connect -[[ソース]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source") `connect`コマンドは、`rippled`サーバーを特定のピア`rippled`サーバーに強制的に接続します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md index ae853964d1..50df98345b 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md @@ -6,7 +6,7 @@ labels: - Core Server --- # connect -[[Source]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source") The `connect` command forces the `rippled` server to connect to a specific peer `rippled` server. diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.ja.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.ja.md index 99a0ccbce9..fe930607cf 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # peer_reservations_add -[[ソース]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source") この`{{currentpage.name}}`メソッドは、XRP Ledger[ピアツーピアネットワーク](peer-protocol.html)内の特定のピアサーバーの予約済みスロットを追加または更新します。[新規: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md index 7036957a2c..ad53b5611b 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md @@ -6,7 +6,7 @@ labels: - Core Server --- # peer_reservations_add -[[Source]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source") The `{{currentpage.name}}` method adds or updates a reserved slot for a specific peer server in the XRP Ledger [peer-to-peer network](peer-protocol.html). [New in: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.ja.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.ja.md index 4f1300cc41..14b394dd1a 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.ja.md @@ -7,7 +7,7 @@ labels: --- # peer_reservations_del -[[ソース]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source") `{{currentpage.name}}`メソッドは、特定の[ピアリザベーション][]を削除します（存在する場合）。[新規: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md index 0053721779..295ba73458 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md @@ -6,7 +6,7 @@ labels: - Core Server --- # peer_reservations_del -[[Source]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source") The `{{currentpage.name}}` method removes a specific [peer reservation][], if one exists. [New in: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.ja.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.ja.md index a00b5492d1..8e2216f067 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # peer_reservations_list -[[ソース]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source") `{{currentpage.name}}`メソッドは、[ピアリザベーション][]を一覧表示します。[新規: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md index e6796b4d08..575b269a4d 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md @@ -6,7 +6,7 @@ labels: - Core Server --- # peer_reservations_list -[[Source]](https://github.com/ripple/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source") The `{{currentpage.name}}` method lists [peer reservations][]. [New in: rippled 1.4.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.ja.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.ja.md index 94ae2df600..2edb4b0e4b 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # peers -[[ソース]](https://github.com/ripple/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source") `peers`コマンドは、[ピアプロトコル](peer-protocol.html)でこのサーバーに現在接続されているその他のすべての`rippled`サーバーのリスト（各サーバーの接続状況と同期状況を含む）を返します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md index d3e8227391..86d6d1c937 100644 --- a/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md +++ b/content/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md @@ -6,7 +6,7 @@ labels: - Core Server --- # peers -[[Source]](https://github.com/ripple/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source") The `peers` command returns a list of all other `rippled` servers currently connected to this one over the [Peer Protocol](peer-protocol.html), including information on their connection and sync status. diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.ja.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.ja.md index e39a0b961d..da0eeb5d79 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # ledger_accept -[[ソース]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source") `ledger_accept`メソッドは、サーバーが現在処理中のレジャーを強制的に終了し、次のレジャー番号に進むようにします。このメソッドはテスト専用であり、`rippled`サーバーがスタンドアロンモードで実行されている場合にのみ使用できます。 diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md index 043d65629e..d7463bb7a1 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md @@ -6,7 +6,7 @@ labels: - Core Server --- # ledger_accept -[[Source]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source") The `ledger_accept` method forces the server to close the current-working ledger and move to the next ledger number. This method is intended for testing purposes only, and is only available when the `rippled` server is running stand-alone mode. diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.ja.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.ja.md index 94aa18546d..50e4b54714 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # stop -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source") サーバーのグレースフルシャットダウンを行います。 diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md index 2a3625a701..08f9bda0ee 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md @@ -6,7 +6,7 @@ labels: - Core Server --- # stop -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source") Gracefully shuts down the server. diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.ja.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.ja.md index 763eeccdc9..16266f5c4a 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.ja.md @@ -7,9 +7,9 @@ labels: - コアサーバー --- # validation_seed -[[ソース]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ValidationSeed.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ValidationSeed.cpp "Source") -`validation_seed`コマンドは、rippledが検証の署名に使用するシークレット値を一時的に設定します。サーバーを再起動すると、この値は構成ファイルに基づいてリセットされます。[rippled 0.29.1 以降では無効](https://github.com/ripple/rippled/releases/tag/0.29.1-rc1 "BADGE_RED") +`validation_seed`コマンドは、rippledが検証の署名に使用するシークレット値を一時的に設定します。サーバーを再起動すると、この値は構成ファイルに基づいてリセットされます。[rippled 0.29.1 以降では無効](https://github.com/XRPLF/rippled/releases/tag/0.29.1-rc1 "BADGE_RED") *`validation_seed`要求は、権限のないユーザーは実行できない[管理メソッド](admin-api-methods.html)です。* diff --git a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md index 58f6359cbf..bebf83b1bd 100644 --- a/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md +++ b/content/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md @@ -7,9 +7,9 @@ labels: - Core Server --- # validation_seed -[[Source]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ValidationSeed.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ValidationSeed.cpp "Source") -The `validation_seed` command temporarily sets the secret value that rippled uses to sign validations. This value resets based on the config file when you restart the server. [Disabled since: rippled 0.29.1](https://github.com/ripple/rippled/releases/tag/0.29.1-rc1 "BADGE_RED") +The `validation_seed` command temporarily sets the secret value that rippled uses to sign validations. This value resets based on the config file when you restart the server. [Disabled since: rippled 0.29.1](https://github.com/XRPLF/rippled/releases/tag/0.29.1-rc1 "BADGE_RED") *The `validation_seed` method is an [admin method](admin-api-methods.html) that cannot be run by unprivileged users!* diff --git a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.ja.md b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.ja.md index 10dffaae74..4de6110774 100644 --- a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.ja.md @@ -6,14 +6,14 @@ labels: - トランザクション送信 --- # sign -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "ソース") `sign`メソッドは[JSONフォーマットのトランザクション](transaction-formats.html)と[シード値](cryptographic-keys.html)を受け取り、トランザクションの署名済みバイナリー表現を返します。[マルチシグトランザクション](multi-signing.html)に署名を付与する場合は、代わりに[sign_forメソッド][]を使用します。 {% include '_snippets/public-signing-note.md' %} -**注意:** 独自の`rippled`サーバーを運用している場合を除き、このコマンドを使用するのではなく、[クライアントライブラリ](client-libraries.html)を実行してください。詳細については[安全な署名の設定](secure-signing.html)を参照してください。 +**注意:** 独自の`rippled`サーバーを運用している場合を除き、このコマンドを使用するのではなく、[クライアントライブラリ](client-libraries.html)を実行してください。詳細については[安全な署名の設定](secure-signing.html)を参照してください。 ## 要求フォーマット 要求フォーマットの例: diff --git a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md index c513010f0b..067168d410 100644 --- a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md +++ b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md @@ -6,7 +6,7 @@ labels: - Transaction Sending --- # sign -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "Source") The `sign` method takes a [transaction in JSON format](transaction-formats.html) and a [seed value](cryptographic-keys.html), and returns a signed binary representation of the transaction. To contribute one signature to a [multi-signed transaction](multi-signing.html), use the [sign_for method][] instead. @@ -92,7 +92,7 @@ The request includes the following parameters: | `passphrase` | String | _(Optional)_ The secret seed of the account supplying the transaction, used to sign it, as a string passphrase. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed`, or `seed_hex`. | | `key_type` | String | _(Optional)_ The [signing algorithm](cryptographic-keys.html#signing-algorithms) of the cryptographic key pair provided. Valid types are `secp256k1` or `ed25519`. Defaults to `secp256k1`. Cannot be used with `secret`. | | `offline` | Boolean | _(Optional)_ If `true`, when constructing the transaction, do not try to [automatically fill](#auto-fillable-fields) any transaction details. The default is `false`. | -| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](transaction-common-fields.html#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](direct-xrp-payments.html) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/ripple/rippled/issues/3272)) | +| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](transaction-common-fields.html#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](direct-xrp-payments.html) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/XRPLF/rippled/issues/3272)) | | `fee_mult_max` | Integer | _(Optional)_ Signing fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](transaction-common-fields.html#auto-fillable-fields) would be greater than the [reference transaction cost](transaction-cost.html#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `10`. | | `fee_div_max` | Integer | _(Optional)_ Signing fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](transaction-common-fields.html#auto-fillable-fields) would be greater than the [reference transaction cost](transaction-cost.html#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. [New in: rippled 0.30.1][] | diff --git a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.ja.md b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.ja.md index f263d1bec9..ee8460e61d 100644 --- a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.ja.md @@ -6,7 +6,7 @@ labels: - トランザクション送信 --- # sign_for -[[ソース]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source") `sign_for`コマンドは、[マルチシグトランザクション](multi-signing.html)の署名を1つ提供します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md index d5e80b3bac..fd61d8cde4 100644 --- a/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md +++ b/content/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md @@ -6,7 +6,7 @@ labels: - Transaction Sending --- # sign_for -[[Source]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source") The `sign_for` command provides one signature for a [multi-signed transaction](multi-signing.html). diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.ja.md index a31cb6b2aa..5702348128 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # consensus_info -[[ソース]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source") `consensus_info`メソッドは、デバッグのための[コンセンサスプロセス](consensus.html)に関する情報を返します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md index 10b7916533..5cc88dcd53 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md @@ -7,7 +7,7 @@ labels: - Core Server --- # consensus_info -[[Source]](https://github.com/ripple/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source") The `consensus_info` command provides information about the [consensus process](consensus.html) for debugging purposes. diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.ja.md index 202effcbaa..39c05e5c7a 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # feature -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source") `feature`コマンドは、[Amendment](amendments.html)に関してこのサーバーが認識している情報（Amendmentが有効であるかどうか、サーバーが[Amendmentプロセス](amendments.html#amendmentプロセス)でこれらのAmendmentに賛成票を投じたかどうかなど）を返します。[新規: rippled 0.31.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md index 0c8c5cb696..d04b73eacc 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md @@ -7,7 +7,7 @@ labels: - Core Server --- # feature -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source") The `feature` command returns information about [amendments](amendments.html) this server knows about, including whether they are enabled and whether the server is voting in favor of those amendments in the [amendment process](amendments.html#amendment-process). [New in: rippled 0.31.0][] diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.ja.md index c87345e431..8202b95a8f 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # fetch_info -[[ソース]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source") `fetch_info`コマンドは、このサーバーが現在ネットワークからフェッチしているオブジェクトに関する情報と、その情報を所有しているピアの数を返します。これは現在の取得操作をリセットする場合にも使用できます。 diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md index 9e5b9a34a3..e16bee3c20 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md @@ -6,7 +6,7 @@ labels: - Core Server --- # fetch_info -[[Source]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source") The `fetch_info` command returns information about objects that this server is currently fetching from the network, and how many peers have that information. It can also be used to reset current fetches. diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.ja.md index 73dc7c9186..cf1bcfe6f8 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # get_counts -[[ソース]](https://github.com/ripple/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source") `get_counts`コマンドは、サーバーの健全性に関するさまざまな統計情報を提供します。そのほとんどは、現在メモリーに格納されている各種オブジェクトの数です。 diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md index 284f960848..ce716449c0 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md @@ -6,7 +6,7 @@ labels: - Core Server --- # get_counts -[[Source]](https://github.com/ripple/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source") The `get_counts` command provides various stats about the health of the server, mostly the number of objects of different types that it currently holds in memory. diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.ja.md index dba37b5fc1..a3c389d7e1 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # print -[[ソース]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source") `print`コマンドは、さまざまな内部サブシステム（ピア、レジャークリーナー、リソースマネージャーなど）の現在の状況を返します。 diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md index 610de05a22..5cf95820f6 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md @@ -6,7 +6,7 @@ labels: - Core Server --- # print -[[Source]](https://github.com/ripple/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source") The `print` command returns the current status of various internal subsystems, including peers, the ledger cleaner, and the resource manager. diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md index 6bb64f2049..1e3a9d2068 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md @@ -7,7 +7,7 @@ labels: - ブロックチェーン --- # validator_info -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ValidatorInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorInfo.cpp "Source") The `{{currentpage.name}}` method returns the current validator settings of the server, if it is configured as a validator. diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.ja.md index 270bc67ec7..72fc08c09b 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # validator_list_sites -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source") `validator_list_sites`コマンドは、バリデータリストを処理するサイトのステータス情報を返します。[新規: rippled 0.80.1][] @@ -129,7 +129,7 @@ Connecting to 127.0.0.1:5005 | `Field` | 型 | 説明 | |:-----------------------|:-----------------|:--------------------------------| -| `last_refresh_status` | 文字列 | 存在する場合は、サイトの最終更新の[`ListDisposition`](https://github.com/ripple/rippled/blob/master/src/ripple/app/misc/ValidatorList.h)です。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | +| `last_refresh_status` | 文字列 | 存在する場合は、サイトの最終更新の[`ListDisposition`](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/ValidatorList.h)です。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | | `last_refresh_time` | 文字列 | サイトの最終照会時刻を人間が読み取れる形式で表示します。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | | `refresh_interval_min` | 符号なし整数 | 更新試行間隔の分数。 | | `uri` | 文字列 | サイトのURI。 | diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md index 9053ea62a1..e10c00b519 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # validator_list_sites -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source") The `validator_list_sites` command returns status information of sites serving validator lists. [New in: rippled 0.80.1][] diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.ja.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.ja.md index 22ebd7d733..43c030bc24 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.ja.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.ja.md @@ -7,7 +7,7 @@ labels: - コアサーバー --- # validators -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source") `validators`コマンドは、サーバーが使用する公開済みの信頼できるバリデータの最新リストに関する情報を、人間が読み取れる形式で返します。[新規: rippled 0.80.1][] diff --git a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md index 7f79dc60c6..feed1004b2 100644 --- a/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md +++ b/content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # validators -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source") The `validators` command returns human readable information about the current list of published and [trusted validators](consensus.html#trust-based-validation) used by the server. diff --git a/content/references/http-websocket-apis/api-conventions/rate-limiting.md b/content/references/http-websocket-apis/api-conventions/rate-limiting.md index 49c3f56701..d337d214ca 100644 --- a/content/references/http-websocket-apis/api-conventions/rate-limiting.md +++ b/content/references/http-websocket-apis/api-conventions/rate-limiting.md @@ -45,7 +45,7 @@ Server is overloaded ``` ## Rate Per Request -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/resource/Fees.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/resource/Fees.h "Source") The server calculates a client's usage rate based on the number of requests made over time, and weighs different types of requests based on approximately how much work the server must do to serve them. Follow-up messages from the server for the [subscribe method][] and [path_find method][] also count towards a client's usage rate. diff --git a/content/references/http-websocket-apis/peer-port-methods/health-check.md b/content/references/http-websocket-apis/peer-port-methods/health-check.md index ec942c043a..20714f554d 100644 --- a/content/references/http-websocket-apis/peer-port-methods/health-check.md +++ b/content/references/http-websocket-apis/peer-port-methods/health-check.md @@ -6,7 +6,7 @@ labels: - Core Server --- # Health Check -[[Source]](https://github.com/ripple/rippled/blob/de0c52738785de8bf837f9124da65c7905e7bb5a/src/ripple/overlay/impl/OverlayImpl.cpp#L1084-L1168 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/de0c52738785de8bf837f9124da65c7905e7bb5a/src/ripple/overlay/impl/OverlayImpl.cpp#L1084-L1168 "Source") The Health Check is a special [peer port method](peer-port-methods.html) for reporting on the health of an individual `rippled` server. This method is intended for use in automated monitoring to recognize outages and prompt automated or manual interventions such as restarting the server. [New in: rippled 1.6.0][] diff --git a/content/references/http-websocket-apis/peer-port-methods/validator-list.md b/content/references/http-websocket-apis/peer-port-methods/validator-list.md index 890077ddfe..575e7fe330 100644 --- a/content/references/http-websocket-apis/peer-port-methods/validator-list.md +++ b/content/references/http-websocket-apis/peer-port-methods/validator-list.md @@ -45,7 +45,7 @@ The JSON object has the following fields: | `public_key` | String | The public key used to verify this validator list data, in hexadecimal. This is a 32-byte Ed25519 public key prefixed with the byte `0xED`. [New in: rippled 1.7.0][] | ### Manifest Data -[[Source]](https://github.com/ripple/rippled/blob/97712107b71a8e2089d2e3fcef9ebf5362951110/src/ripple/app/misc/impl/Manifest.cpp#L43-L66 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/97712107b71a8e2089d2e3fcef9ebf5362951110/src/ripple/app/misc/impl/Manifest.cpp#L43-L66 "Source") A "manifest" contains information uniquely identifying a person or organization involved in the consensus process, either a **validator** or a **list publisher**. A validator's manifest contains the _public_ information from that [validator's token](run-rippled-as-a-validator.html#3-enable-validation-on-your-rippled-server). A list publisher's manifest provides information about the list publisher. Both are typically encoded to binary in the XRP Ledger's standard [binary serialization format](serialization.html). (There is no standard JSON representation of a manifest.) diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.ja.md index c5a73189c3..5b2ad31b1a 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # account_channels -[[ソース]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/AccountChannels.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/AccountChannels.cpp "Source") _（[PayChan Amendment][]が有効になっている必要があります。[新規: rippled 0.33.0][]）_ diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md index 14cdded0f1..6bc730ef18 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # account_channels -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source") _(Added by the [PayChan amendment][]. [New in: rippled 0.33.0][])_ diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.ja.md index 8295e72c2d..bcfe1324e9 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.ja.md @@ -6,7 +6,7 @@ labels: - トークン --- # account_currencies -[[ソース]](https://github.com/ripple/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") `account_currencies`コマンドは、アカウントのトラストラインに基づいてそのアカウントが送金または受領できる通貨のリストを返します。（このリストは完全に確認されたリストではありませんが、ユーザーインターフェイスへの入力に使用できます。） diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md index f39cef509a..9b677d237e 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md @@ -6,7 +6,7 @@ labels: - Tokens --- # account_currencies -[[Source]](https://github.com/ripple/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") The `account_currencies` command retrieves a list of currencies that an account can send or receive, based on its trust lines. (This is not a thoroughly confirmed list, but it can be used to populate user interfaces.) diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.ja.md index df66b7aa1c..08222cce81 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.ja.md @@ -7,7 +7,7 @@ labels: - XRP --- # account_info -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") `account_info`コマンドは、アカウントとそのアクティビティおよびXRP残高についての情報を取得します。取得されたすべての情報は、特定バージョンのレジャーに関連付けられています。 diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.md index 8f3af50e00..335d13b2bb 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_info.md @@ -7,7 +7,7 @@ labels: - XRP --- # account_info -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") The `account_info` command retrieves information about an account, its activity, and its XRP balance. All information retrieved is relative to a particular version of the ledger. diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.ja.md index c3882c9a96..13c16994eb 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.ja.md @@ -6,7 +6,7 @@ labels: - トークン --- # account_lines -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountLines.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountLines.cpp "Source") `account_lines`メソッドは、アカウントのトラストラインに関する情報（XRP以外のあらゆる通貨の残高と資産など）を返します。取得された情報はすべて、特定バージョンのレジャーに関連付けられています。 diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md index 4744c0fb0f..de1a100e5b 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md @@ -6,7 +6,7 @@ labels: - Tokens --- # account_lines -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountLines.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountLines.cpp "Source") The `account_lines` method returns information about an account's trust lines, which contain balances in all non-XRP currencies and assets. All information retrieved is relative to a particular version of the ledger. diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.ja.md index e838496c3f..ffdca1941e 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.ja.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # account_objects -[[ソース]](https://github.com/ripple/rippled/blob/399c43cae6e90a428e9ce6a988123972b0f03c99/src/ripple/rpc/handlers/AccountObjects.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/399c43cae6e90a428e9ce6a988123972b0f03c99/src/ripple/rpc/handlers/AccountObjects.cpp "Source") `account_objects`コマンドは、アカウントが所有するすべてのオブジェクトの生[レジャーフォーマット][]を返します。アカウントのトラストラインと残高の概要については、[account_linesメソッド][]を参照してください。 @@ -70,7 +70,7 @@ rippled account_objects r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 validated | `Field` | 型 | 説明 | |:---------------|:-------------------------------------------|:---------------| | `account` | 文字列 | アカウントの一意のIDであり、最も一般的にはアカウントのアドレスが使用されます。 | -| `type` | 文字列 | _（省略可）_ 指定されている場合、結果をフィルタリングしてこのタイプのレジャーオブジェクトのみが含まれるようにします。有効なタイプは`check`、`deposit_preauth`、`escrow`、`offer`、`payment_channel`、`signer_list`、および`state`（トラストライン）です。 | +| `type` | 文字列 | _（省略可）_ 指定されている場合、結果をフィルタリングしてこのタイプのレジャーオブジェクトのみが含まれるようにします。有効なタイプは`check`、`deposit_preauth`、`escrow`、`offer`、`payment_channel`、`signer_list`、および`state`（トラストライン）です。 | | `ledger_hash` | 文字列 | _（省略可）_ 使用するレジャーバージョンの20バイトの16進文字列。（[レジャーの指定][]を参照してください） | | `ledger_index` | 文字列または符号なし整数 | _（省略可）_ 使用するレジャーの[レジャーインデックス][]、またはレジャーを自動的に選択するためのショートカット文字列。（[レジャーの指定][]を参照してください） | | `limit` | 符号なし整数 | _（省略可）_ 結果に含めることができるオブジェクトの最大数。非管理者接続では10以上400以下の範囲で値を指定する必要があります。デフォルトでは200です。 | diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md index 08336218c5..1b1c574d04 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md @@ -7,7 +7,7 @@ labels: - Data Retention --- # account_objects -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountObjects.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountObjects.cpp "Source") The `account_objects` command returns the raw [ledger format][] for all ledger entries owned by an account. For a higher-level view of an account's trust lines and balances, see the [account_lines method][] instead. diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.ja.md index b0feead5aa..f9a315d07f 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.ja.md @@ -6,7 +6,7 @@ labels: - 分散型取引所 --- # account_offers -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") `account_offers`メソッドは、特定の[アカウント](accounts.html)から出された[オファー](offers.html)のうち、特定の[レジャーバージョン](ledgers.html)で未処理であったオファーのリストを取得します。 diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md index 1b95f93197..152790e286 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md @@ -6,7 +6,7 @@ labels: - Decentralized Exchange --- # account_offers -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") The `account_offers` method retrieves a list of [offers](offers.html) made by a given [account](accounts.html) that are outstanding as of a particular [ledger version](ledgers.html). diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.ja.md index f940ccedd0..57ca2832f7 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.ja.md @@ -7,7 +7,7 @@ labels: - Payments --- # account_tx -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") `account_tx`メソッドは、指定したアカウントに関連するトランザクションのリストを取得します。 diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md b/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md index dab8a2e2bc..8b029ca662 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md @@ -7,7 +7,7 @@ labels: - Accounts --- # account_tx -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") The `account_tx` method retrieves a list of transactions that involved the specified account. diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.ja.md index 738020066f..467dda0086 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.ja.md @@ -7,7 +7,7 @@ labels: - アカウント --- # gateway_balances -[[ソース]](https://github.com/ripple/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") `gateway_balances`コマンドは、特定のアカウントから発行された残高の合計を計算します。オプションで、[運用アドレス](account-types.html)が保有する額を除外できます。[新規: rippled 0.28.2][] diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md b/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md index 603e061689..2945c9abc8 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md @@ -7,7 +7,7 @@ labels: - Accounts --- # gateway_balances -[[Source]](https://github.com/ripple/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") The `gateway_balances` command calculates the total balances issued by a given account, optionally excluding amounts held by [operational addresses](account-types.html). [New in: rippled 0.28.2][] diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.ja.md b/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.ja.md index 4a98c87130..aa00bf5838 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.ja.md @@ -6,7 +6,7 @@ labels: - トークン --- # noripple_check -[[ソース]](https://github.com/ripple/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") `noripple_check`コマンドを使用すると、[アカウントのDefaultRippleフィールドとそのトラストラインのNoRippleフラグ](rippling.html)の状態を、推奨される設定と比較して迅速にチェックできます。 diff --git a/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md b/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md index ff118f86aa..4db16ca014 100644 --- a/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md +++ b/content/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md @@ -6,7 +6,7 @@ labels: - Tokens --- # noripple_check -[[Source]](https://github.com/ripple/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") The `noripple_check` command provides a quick way to check the status of [the Default Ripple field for an account and the No Ripple flag of its trust lines](rippling.html), compared with the recommended settings. diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.ja.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.ja.md index 78f6a7a3ee..717f18e6d3 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.ja.md @@ -6,7 +6,7 @@ label: - ブロックチェーン --- # ledger -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") 公開レジャーに関する情報を取得します。 diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md index f47b2142f8..0d055b0d80 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # ledger -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") Retrieve information about the public [ledger](ledgers.html). diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.ja.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.ja.md index 80ef75e9db..e10d7d5532 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.ja.md @@ -6,7 +6,7 @@ label: - ブロックチェーン --- # ledger_closed -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") `ledger_closed`メソッドは、最新の決済済みレジャーの一意のIDを返します。（このレジャーは必ずしも検証済みで変更不可能ではありません。） diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md index c3c13f51c1..ec536f0286 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # ledger_closed -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") The `ledger_closed` method returns the unique identifiers of the most recently closed ledger. (This ledger is not necessarily validated and immutable yet.) diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.ja.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.ja.md index ec0907f882..2c417f6ed2 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.ja.md @@ -6,7 +6,7 @@ label: - ブロックチェーン --- # ledger_current -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") `ledger_current`メソッドは、現在進行中のレジャーの一意のIDを返します。このコマンドで返されるレジャーは確定されたものではないため、このコマンドは主にテストに有用です。 diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md index b7276ad6e6..8c7adca2ac 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # ledger_current -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") The `ledger_current` method returns the unique identifiers of the current in-progress [ledger](ledgers.html). This command is mostly useful for testing, because the ledger returned is still in flux. diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.ja.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.ja.md index 1e2c9f868c..cd0a145d6e 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.ja.md @@ -7,7 +7,7 @@ label: - データ保持 --- # ledger_data -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") `ledger_data`メソッドは指定されたレジャーの内容を取得します。1つのレジャーバージョンの内容全体を取得するため、複数のコールを繰り返し実行できます。 diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md index 497cd95265..c13039c28d 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md @@ -7,7 +7,7 @@ labels: - Data Retention --- # ledger_data -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") The `ledger_data` method retrieves contents of the specified ledger. You can iterate through several calls to retrieve the entire contents of a single ledger version. diff --git a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index 7c6622a688..4bf6464565 100644 --- a/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/content/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -7,7 +7,7 @@ labels: - Data Retention --- # ledger_entry -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/LedgerEntry.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerEntry.cpp "Source") The `ledger_entry` method returns a single ledger entry from the XRP Ledger in its raw format. See [ledger format][] for information on the different types of entries you can retrieve. diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.ja.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.ja.md index 243a461425..44c8962430 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.ja.md @@ -7,7 +7,7 @@ labels: - 複数通貨間 --- # book_offers -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") `book_offers`メソッドは、[オーダーブック](http://www.investopedia.com/terms/o/order-book.asp)と呼ばれる、2つの通貨間のオファーのリストを取得します。結果が非常に大きい場合、結果の一部がマーカー付きで返されます。これにより、その後の要求は前回の要求で終わった箇所から再開できます。 diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md index d9fe5102d3..a690561894 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md @@ -7,7 +7,7 @@ labels: - Cross-Currency --- # book_offers -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") The `book_offers` method retrieves a list of [Offers](offers.html) between two currencies, also known as an _order book_. The response omits [unfunded Offers](offers.html#lifecycle-of-an-offer) and reports how much of each remaining Offer's total is currently funded. diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.ja.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.ja.md index f7021c3dd2..1cc5871ae9 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.ja.md @@ -7,7 +7,7 @@ labels: - セキュリティ --- # deposit_authorized -[[ソース]](https://github.com/ripple/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") `deposit_authorized`コマンドは、あるアカウントに別のアカウントへ支払を直接送金する権限があるかどうかを示します。アカウントへの送金に承認を義務付ける方法については、[Deposit Authorization](depositauth.html)を参照してください。 diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md index 7b3f1a2463..7059725eb0 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md @@ -7,7 +7,7 @@ labels: - Security --- # deposit_authorized -[[Source]](https://github.com/ripple/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") The `deposit_authorized` command indicates whether one account is authorized to send payments directly to another. See [Deposit Authorization](depositauth.html) for information on how to require authorization to deliver money to your account. diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.ja.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.ja.md index 4484ebb7e4..9b4ca594ad 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.ja.md @@ -7,7 +7,7 @@ labels: - トークン --- # path_find -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") *WebSocket APIのみ。*`path_find`メソッドは、トランザクションが実行される可能性のある[パス](paths.html)を探索し、時間の経過とともにパスが変化する場合に更新を定期的に送信します。JSON-RPCでサポートされているシンプルなバージョンについては、[ripple_path_findメソッド][]を参照してください。完全にXRPで行われる支払いの場合、XRPはどのアカウントにも直接送金できるためパスを探索する必要はありません。 @@ -20,7 +20,7 @@ path_findコマンドには3種類のモード（サブコマンド）があり `rippled`サーバーは支払いを行うにあたり最も安価なパスまたはパスの組み合わせを探索しますが、このメソッドで返されるパスが最良のパスであることは保証されません。サーバーの負荷が原因で、Pathfindingで最良のパスを検出できないことがあります。また、信頼できないサーバーからのPathfindingの結果には注意する必要があります。オペレーターの収益となるように、最良ではないパスを返すようにサーバーが改ざんされる可能性があります。Pathfindingについて信頼できる独自サーバーがない場合は、1つのサーバーから不適切な結果が返されるリスクを最小限に抑えるため、異なる当事者が実行する複数のサーバーからのPathfindingの結果を比較してください。（**注記:** サーバーから最良ではない結果が返されても、必ずしも悪意のある振る舞いの証拠とはなりません。サーバーの負荷が高い場合の症状である可能性もあります。） ## path_find create -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") `path_find`の`create`サブコマンドは、指定された特定アカウントから支払トランザクションを実行できるパスを探索する継続的な要求を作成し、別のアカウントが何らかの通貨で希望する額を受領できるようにします。初期応答には2つのアドレス間で提案されるパスが含まれています。このパスにより、希望する額を受領できます。その後サーバーは、`"type": "path_find"`で有効なパスの更新を含む追加メッセージを送信します。更新の頻度はサーバーにより決定されますが、新しいレジャーバージョンがある場合には通常、数秒間に1回です。 @@ -497,7 +497,7 @@ path_find create要求からの非同期フォローアップの例を次に示 ## path_find close -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") `path_find`の`close`サブコマンドは、サーバーに対して現在実行中のPathfinding要求に関する情報の送信を停止するように指示します。 @@ -542,7 +542,7 @@ Pathfinding要求が正常にクローズされた場合、応答は[`path_find * `noPathRequest` - Pathfinding要求をクローズしようとしましたが、実行中の要求がありませんでした。 ## path_find status -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") `path_find`の`status`サブコマンドは、現在実行中のクライアントのPathfinding要求の即時更新を要求します。 diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md index 60fb78ed77..d987bcbbab 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md @@ -7,7 +7,7 @@ labels: - Tokens --- # path_find -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") *WebSocket API only!* The `path_find` method searches for a [path](paths.html) along which a transaction can possibly be made, and periodically sends updates when the path changes over time. For a simpler version that is supported by JSON-RPC, see the [ripple_path_find method][]. For payments occurring strictly in XRP, it is not necessary to find a path, because XRP can be sent directly to any account. @@ -20,7 +20,7 @@ There are three different modes, or sub-commands, of the path_find command. Spec Although the `rippled` server tries to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers run by different parties, to minimize the risk of a single server returning poor results. (**Note:** A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.) ## path_find create -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") The `create` sub-command of `path_find` creates an ongoing request to find possible paths along which a payment transaction could be made from one specified account such that another account receives a desired amount of some currency. The initial response contains a suggested path between the two addresses that would result in the desired amount being received. After that, the server sends additional messages, with `"type": "path_find"`, with updates to the potential paths. The frequency of updates is left to the discretion of the server, but it usually means once every few seconds when there is a new ledger version. @@ -497,7 +497,7 @@ Here is an example of an asynchronous follow-up from a path_find create request: ## path_find close -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") The `close` sub-command of `path_find` instructs the server to stop sending information about the current open pathfinding request. @@ -542,7 +542,7 @@ If there was no outstanding pathfinding request, an error is returned instead. * `noPathRequest` - You tried to close a pathfinding request when there is not an open one. ## path_find status -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") The `status` sub-command of `path_find` requests an immediate update about the client's currently-open pathfinding request. diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.ja.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.ja.md index 7da085f3b8..3d65925098 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.ja.md @@ -7,7 +7,7 @@ labels: - トークン --- # ripple_path_find -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") `ripple_path_find`メソッドは、[path_findメソッド][]のシンプルなバージョンであり、すぐに利用できる[ペイメントパス](paths.html)を含む1つの応答を返します。WebSocket APIとJSON-RPC APIの両方で使用できます。ただし、結果は時間の経過とともに古くなる傾向にあります。最新の状態を維持するために複数のコールを実行する代わりに、可能な場合には[path_findメソッド][]を使用して、継続的な更新をサブスクライブします。 diff --git a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md index 2c434f1985..9dcb524127 100644 --- a/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md +++ b/content/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md @@ -7,7 +7,7 @@ labels: - Tokens --- # ripple_path_find -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") The `ripple_path_find` method is a simplified version of the [path_find method][] that provides a single response with a [payment path](paths.html) you can use right away. It is available in both the WebSocket and JSON-RPC APIs. However, the results tend to become outdated as time passes. Instead of making multiple calls to stay updated, you should instead use the [path_find method][] to subscribe to continued updates where possible. diff --git a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.ja.md b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.ja.md index 18f7f177c8..739f745642 100644 --- a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # channel_authorize -[[ソース]](https://github.com/ripple/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") _（[PayChan Amendment][]が有効になっている必要があります。[新規: rippled 0.33.0][]）_ diff --git a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md index 7064d26040..f303b38ca8 100644 --- a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md +++ b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # channel_authorize -[[Source]](https://github.com/ripple/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") _(Added by the [PayChan amendment][] to be enabled. [New in: rippled 0.33.0][])_ diff --git a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.ja.md b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.ja.md index cc3300705b..e963bf997d 100644 --- a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # channel_verify -[[ソース]](https://github.com/ripple/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") _（[PayChan Amendment][]が有効になっている必要があります。[新規: rippled 0.33.0][]）_ diff --git a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md index 74c43ca8ca..32c2bbffb9 100644 --- a/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md +++ b/content/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # channel_verify -[[Source]](https://github.com/ripple/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") _(Added by the [PayChan amendment][] to be enabled. [New in: rippled 0.33.0][])_ diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.ja.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.ja.md index 23cdd6e89e..40eedfab2e 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.ja.md @@ -6,7 +6,7 @@ labels: - 手数料 --- # fee -[[ソース]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") `fee`コマンドは、[トランザクションコスト](transaction-cost.html)に関するオープンレジャーの要件の現在の状態を報告します。このコマンドを使用するには、[FeeEscalation Amendment][]が有効になっている必要があります。[新規: rippled 0.31.0][] diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md index 07d9770ac1..1ae40ae18a 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md @@ -6,7 +6,7 @@ labels: - Fees --- # fee -[[Source]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") The `fee` command reports the current state of the open-ledger requirements for the [transaction cost](transaction-cost.html). This requires the [FeeEscalation amendment][] to be enabled. [New in: rippled 0.31.0][] diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md index 5deac9e53b..ad7cd60a32 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # manifest -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Manifest.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Manifest.cpp "Source") The `{{currentpage.name}}` method reports the current "manifest" information for a given validator public key. The "manifest" is a block of data that authorizes an ephemeral signing key with a signature from the validator's master key pair. [Updated in: rippled 1.7.0][] @@ -52,7 +52,7 @@ The request includes the following parameters: |:-------------|:-------|:-----------------------------------| | `public_key` | String | The [base58][]-encoded public key of the validator to look up. This can be the master public key or ephemeral public key. | -**Note:** The commandline format for this method does not work in rippled v1.5.0. See [issue #3317](https://github.com/ripple/rippled/issues/3317) for details. +**Note:** The commandline format for this method does not work in rippled v1.5.0. See [issue #3317](https://github.com/XRPLF/rippled/issues/3317) for details. ### Response Format @@ -122,7 +122,7 @@ Connecting to 127.0.0.1:5005 - + The response follows the [standard format][], with a successful result containing the following fields: diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.ja.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.ja.md index 4893a163aa..5e4b386d7c 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # server_info (rippled) -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") `server_info`コマンドは、問い合わせ中の`rippled`サーバーについての各種情報を、人間が読めるフォーマットでサーバーに要求します。 diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md index c54371dcde..9f6b930360 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md @@ -6,7 +6,7 @@ labels: - Core Server --- # server_info (rippled) -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") The `server_info` command asks the server for a human-readable version of various information about [the `rippled` server](xrpl-servers.html) being queried. For [Clio servers](the-clio-server.html), see [`server_info` (Clio)](server_info-clio.html) instead. diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.ja.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.ja.md index 2df2a9f716..be72ea95e6 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # server_state -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") `server_state`コマンドは、サーバーに対し`rippled`サーバーの現在の状態に関するさまざまな機械可読の情報を問い合わせます。応答は[server_infoメソッド][]の場合とほぼ同じですが、読み取りやすい単位ではなく処理しやすい単位を使用します。（たとえば、XRP値は科学的記数法や10進数値の代わりに整数のdrop数で示され、時刻は秒単位ではなくミリ秒単位で示されます。） diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md index c74f13b371..0257095e84 100644 --- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md +++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md @@ -6,7 +6,7 @@ labels: - Core Server --- # server_state -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") The `server_state` command asks the server for various machine-readable information about the `rippled` server's current state. The response is almost the same as the [server_info method][], but uses units that are easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.) diff --git a/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.ja.md b/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.ja.md index 865a12bc29..006334ecd0 100644 --- a/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.ja.md @@ -9,7 +9,7 @@ labels: - スマートコントラクト --- # subscribe -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Subscribe.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Subscribe.cpp "Source") `subscribe`メソッドは、特定のイベントが発生した場合に、定期的に通知するようサーバーに要求します。 diff --git a/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index ca978f6618..5db9e88485 100644 --- a/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md +++ b/content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md @@ -9,7 +9,7 @@ labels: - Smart Contracts --- # subscribe -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Subscribe.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Subscribe.cpp "Source") The `subscribe` method requests periodic notifications from the server when certain events happen. diff --git a/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.ja.md b/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.ja.md index aa13b3c69d..534ef2e434 100644 --- a/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.ja.md @@ -9,7 +9,7 @@ labels: - スマートコントラクト --- # unsubscribe -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") `unsubscribe`コマンドはサーバーに対して、特定のサブスクリプションまたは一連のサブスクリプションへのメッセージ送信の停止を指示します。 diff --git a/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md b/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md index a06536c278..760d941ecb 100644 --- a/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md +++ b/content/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md @@ -9,7 +9,7 @@ labels: - Smart Contracts --- # unsubscribe -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") The `unsubscribe` command tells the server to stop sending messages for a particular subscription or set of subscriptions. diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.ja.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.ja.md index 72009d349c..787cd66a28 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.ja.md @@ -7,7 +7,7 @@ labels: - 支払い --- # submit -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "ソース") `submit`メソッドは[トランザクション](transaction-formats.html)を適用し、トランザクションの確認と将来のレジャーへの記録が行われるように、ネットワークに送信します。 diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md index f4a5c5bc70..8ef80aa356 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md @@ -7,7 +7,7 @@ labels: - Payments --- # submit -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "Source") The `submit` method applies a [transaction](transaction-formats.html) and sends it to the network to be confirmed and included in future ledgers. @@ -89,7 +89,7 @@ The request includes the following parameters: | `key_type` | String | _(Optional)_ Type of cryptographic key provided in this request. Valid types are `secp256k1` or `ed25519`. Defaults to `secp256k1`. Cannot be used with `secret`. **Caution:** Ed25519 support is experimental. | | `fail_hard` | Boolean | _(Optional)_ If `true`, and the transaction fails locally, do not retry or relay the transaction to other servers. The default is `false`. [Updated in: rippled 1.5.0][] | | `offline` | Boolean | _(Optional)_ If `true`, when constructing the transaction, do not try to automatically fill in or validate values. The default is `false`. | -| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](transaction-common-fields.html#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](direct-xrp-payments.html) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/ripple/rippled/issues/3272)) | +| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](transaction-common-fields.html#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](direct-xrp-payments.html) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/XRPLF/rippled/issues/3272)) | | `fee_mult_max` | Integer | _(Optional)_ Sign-and-submit fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](transaction-common-fields.html#auto-fillable-fields) would be greater than the [reference transaction cost](transaction-cost.html#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `10`. | | `fee_div_max` | Integer | _(Optional)_ Sign-and-submit fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](transaction-common-fields.html#auto-fillable-fields) would be greater than the [reference transaction cost](transaction-cost.html#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. [New in: rippled 0.30.1][] | diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.ja.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.ja.md index 49b6dfaae4..f58386cb79 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.ja.md @@ -6,7 +6,7 @@ labels: - トランザクション送信 --- # submit_multisigned -[[ソース]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") `submit_multisigned`コマンドは[マルチシグ](multi-signing.html)トランザクションを適用し、このトランザクションをネットワークに送信して、今後のレジャーに追加します。（[`submit`コマンドを送信専用モードで](submit.html#送信専用モード)使用して、マルチシグトランザクションをバイナリー形式で送信することもできます。) diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md index a6695fe86f..931690a529 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md @@ -6,7 +6,7 @@ labels: - Transaction Sending --- # submit_multisigned -[[Source]](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") The `submit_multisigned` command applies a [multi-signed](multi-signing.html) transaction and sends it to the network to be included in future ledgers. (You can also submit multi-signed transactions in binary form using the [`submit` command in submit-only mode](submit.html#submit-only-mode).) diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.ja.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.ja.md index b69873b61f..160864738b 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.ja.md @@ -6,7 +6,7 @@ labels: - トランザクション送信 --- # transaction_entry -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") `transaction_entry`メソッドは、特定のレジャーバージョンから1つのトランザクションに関する情報を取得します。（これに対して、[txメソッド][]はすべてのレジャーから指定のトランザクションを検索します。txメソッドの使用をお勧めします。） diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md index 9cdeab59ba..99d77ad583 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md @@ -6,7 +6,7 @@ labels: - Transaction Sending --- # transaction_entry -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") The `transaction_entry` method retrieves information on a single transaction from a specific ledger version. (The [tx method][], by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.) diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.ja.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.ja.md index 6b69207e36..dae2b6636d 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.ja.md @@ -7,7 +7,7 @@ labels: - 支払い --- # tx -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") `tx`メソッドは1つのトランザクションに関する情報を取得します。 diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md index 34e912c84f..9e7490dadf 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md @@ -7,7 +7,7 @@ labels: - Payments --- # tx -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") The `tx` method retrieves information on a single [transaction](transaction-formats.html), by its [identifying hash][]. @@ -450,7 +450,7 @@ The response follows the [standard format][], with a successful result containin | `validated` | Boolean | If `true`, this data comes from a validated ledger version; if omitted or set to `false`, this data is not final. | | (Various) | (Various) | Other fields from the [Transaction object](transaction-formats.html) | -**Note:** `rippled` 1.7.0 has a known issue where the `meta` field contains JSON even if the request asked for binary. ([#3791](https://github.com/ripple/rippled/pull/3791)) +**Note:** `rippled` 1.7.0 has a known issue where the `meta` field contains JSON even if the request asked for binary. ([#3791](https://github.com/XRPLF/rippled/pull/3791)) ### Not Found Response diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.ja.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.ja.md index 2527324e27..7522e51f4b 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.ja.md @@ -4,7 +4,7 @@ parent: transaction-methods.html blurb: 直近に作成されたトランザクションの一部を取得します。 --- # tx_history -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") `tx_history`メソッドは、直近に作成されたトランザクションの一部を取得します。 diff --git a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md index 63b30d7fc8..f23245eecf 100644 --- a/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md +++ b/content/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md @@ -4,7 +4,7 @@ parent: transaction-methods.html blurb: Retrieve info about all recent transactions. --- # tx_history -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") The `tx_history` method retrieves some of the most recent transactions made. diff --git a/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.ja.md b/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.ja.md index 70e6888695..8816bd5818 100644 --- a/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # ping -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") `ping`コマンドは確認応答を返します。これにより、クライアントは接続のステータスと遅延をテストできます。 @@ -86,6 +86,6 @@ rippled ping * [汎用エラータイプ][]のすべて。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.md b/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.md index bfcfd1c396..ee75ba06c0 100644 --- a/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.md +++ b/content/references/http-websocket-apis/public-api-methods/utility-methods/ping.md @@ -6,7 +6,7 @@ labels: - Core Server --- # ping -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") The `ping` command returns an acknowledgement, so that clients can test the connection status and latency. @@ -86,6 +86,6 @@ The response follows the [standard format][], with a successful result containin * Any of the [universal error types][]. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/http-websocket-apis/public-api-methods/utility-methods/random.ja.md b/content/references/http-websocket-apis/public-api-methods/utility-methods/random.ja.md index 1cf5b49be7..e8e5b9a17a 100644 --- a/content/references/http-websocket-apis/public-api-methods/utility-methods/random.ja.md +++ b/content/references/http-websocket-apis/public-api-methods/utility-methods/random.ja.md @@ -6,7 +6,7 @@ labels: - コアサーバー --- # random -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") `random`コマンドは、クライアントが乱数生成のエントロピー生成源として使用する乱数を提供します。 @@ -92,6 +92,6 @@ rippled random * `internal` - 乱数生成機能に関連している可能性がある内部エラーが発生しました。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/http-websocket-apis/public-api-methods/utility-methods/random.md b/content/references/http-websocket-apis/public-api-methods/utility-methods/random.md index cdfdd06d69..17b31ad767 100644 --- a/content/references/http-websocket-apis/public-api-methods/utility-methods/random.md +++ b/content/references/http-websocket-apis/public-api-methods/utility-methods/random.md @@ -6,7 +6,7 @@ labels: - Core Server --- # random -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") The `random` command provides a random number to be used as a source of entropy for random number generation by clients. @@ -103,6 +103,6 @@ The response follows the [standard format][], with a successful result containin * `internal` - Some internal error occurred, possibly relating to the random number generator. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/data-types/basic-data-types.ja.md b/content/references/protocol-reference/data-types/basic-data-types.ja.md index bf90e5c473..544eae4e58 100644 --- a/content/references/protocol-reference/data-types/basic-data-types.ja.md +++ b/content/references/protocol-reference/data-types/basic-data-types.ja.md @@ -27,7 +27,7 @@ blurb: さまざまなタイプのオブジェクトがそれぞれ異なる方 ### ハッシュプレフィクス -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") 多くの場合、XRP Ledgerではオブジェクトのバイナリデータに4バイトのプレフィクスを付けてからハッシュを計算するため、異なるタイプのオブジェクトが同じバイナリフォーマットである場合でも、異なるハッシュが設定されます。既存の4バイトコードは、ASCIIでエンコードされた英字3文字の後に0バイトが続く構成となっています。 @@ -165,6 +165,6 @@ XRPを金額なしで指定する場合は（主に、オーダーブックを Rippleエポック時間を32ビット変数でUNIXエポック時間に変換しないでください。整数のオーバーフローが発生する恐れがあります。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/data-types/basic-data-types.md b/content/references/protocol-reference/data-types/basic-data-types.md index e735bac6ac..79c3e30176 100644 --- a/content/references/protocol-reference/data-types/basic-data-types.md +++ b/content/references/protocol-reference/data-types/basic-data-types.md @@ -27,7 +27,7 @@ Each closed [Ledger](ledger-data-formats.html) has a [Ledger Index][] and a [Has ### Hash Prefixes -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") In many cases, the XRP Ledger prefixes an object's binary data with a 4-byte code before calculating its hash, so that objects of different types have different hashes even if their binary formats are the same. The existing 4-byte codes are structured as three alphabetic characters, encoded as ASCII, followed by a zero byte. @@ -129,6 +129,6 @@ The `rippled` server and its APIs represent time as an unsigned integer. This nu Don't convert Ripple Epoch times to UNIX Epoch times in 32-bit variables: this could lead to integer overflows. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/data-types/currency-formats.ja.md b/content/references/protocol-reference/data-types/currency-formats.ja.md index 74d4aa63c5..647e109010 100644 --- a/content/references/protocol-reference/data-types/currency-formats.ja.md +++ b/content/references/protocol-reference/data-types/currency-formats.ja.md @@ -35,7 +35,7 @@ XRP Ledgerの発行済み通貨は、以下の精度のカスタムフォーマ * 10進15桁の精度 ## 発行済み通貨の計算 -[[ソース]](https://github.com/ripple/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source") ![発行済み通貨額フォーマットの図](img/currency-number-format.ja.png) diff --git a/content/references/protocol-reference/ledger-data/ledger-header.ja.md b/content/references/protocol-reference/ledger-data/ledger-header.ja.md index f7a9855a78..5b48b43ce2 100644 --- a/content/references/protocol-reference/ledger-data/ledger-header.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-header.ja.md @@ -7,7 +7,7 @@ labels: - ブロックチェーン --- # レジャーヘッダー -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") すべてのレジャーバージョンには、その内容を記述する一意のヘッダーが含まれています。[ledgerメソッド][]を使用してレジャーのヘッダー情報を検索できます。レジャーヘッダーの内容を以下に示します。 @@ -43,6 +43,6 @@ labels: -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-header.md b/content/references/protocol-reference/ledger-data/ledger-header.md index ee5b9ceda2..3b927c78fc 100644 --- a/content/references/protocol-reference/ledger-data/ledger-header.md +++ b/content/references/protocol-reference/ledger-data/ledger-header.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # Ledger Header -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") Every [ledger version](ledgers.html) has a unique header that describes the contents. You can look up a ledger's header information with the [ledger method][]. The contents of the ledger header are as follows: @@ -43,6 +43,6 @@ For ledger basics, see [Ledgers](ledgers.html). -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-ids.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-ids.ja.md index dc16327eea..5ce15149f9 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-ids.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-ids.ja.md @@ -8,7 +8,7 @@ labels: # レジャーオブジェクトID -レジャーの状態ツリーのすべてのオブジェクトには一意のIDがあります。このフィールドは、オブジェクトの内容と同じレベルでJSONの`index`フィールドとして返されます。IDは、オブジェクトの重要な内容をハッシュし、[名前空間ID](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/LedgerFormats.h#L99)を使用して生成されます。[レジャーオブジェクトタイプ](ledger-object-types.html)により、使用する名前空間IDとハッシュに含める内容が決定します。これにより、すべてのIDが一意になります。ハッシュを計算するため、`rippled`はSHA-512を使用し、その結果を最初の256バイトで切り捨てます。**SHA-512ハーフ**と呼ばれるこのアルゴリズム出力は、SHA-256と同等のセキュリティで、64ビットプロセッサーでは実行にかかる時間が短くなります。 +レジャーの状態ツリーのすべてのオブジェクトには一意のIDがあります。このフィールドは、オブジェクトの内容と同じレベルでJSONの`index`フィールドとして返されます。IDは、オブジェクトの重要な内容をハッシュし、[名前空間ID](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/LedgerFormats.h#L99)を使用して生成されます。[レジャーオブジェクトタイプ](ledger-object-types.html)により、使用する名前空間IDとハッシュに含める内容が決定します。これにより、すべてのIDが一意になります。ハッシュを計算するため、`rippled`はSHA-512を使用し、その結果を最初の256バイトで切り捨てます。**SHA-512ハーフ**と呼ばれるこのアルゴリズム出力は、SHA-256と同等のセキュリティで、64ビットプロセッサーでは実行にかかる時間が短くなります。 {{ include_svg("img/ledger-object-ids.ja.svg", "図: rippledによる、SHA-512ハーフを使用したレジャーオブジェクトIDの生成。スペースキーは、異なるオブジェクトタイプIDの競合を防止します。") }} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-ids.md b/content/references/protocol-reference/ledger-data/ledger-object-ids.md index aafd8b19b5..bd6a6b51b8 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-ids.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-ids.md @@ -6,10 +6,10 @@ labels: - Data Retention --- # Ledger Object IDs -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp) +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp) -Each [object in a ledger's state data](ledger-object-types.html) has a unique ID. The ID is derived by hashing important contents of the object, along with a [namespace identifier](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/LedgerFormats.h#L99). The [ledger object type](ledger-object-types.html) determines which namespace identifier to use and which contents to include in the hash. This ensures every ID is unique. To calculate the hash, `rippled` uses SHA-512 and then truncates the result to the first 256 bits. This algorithm, informally called **SHA-512Half**, provides an output that has comparable security to SHA-256, but runs faster on 64-bit processors. +Each [object in a ledger's state data](ledger-object-types.html) has a unique ID. The ID is derived by hashing important contents of the object, along with a [namespace identifier](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/LedgerFormats.h#L99). The [ledger object type](ledger-object-types.html) determines which namespace identifier to use and which contents to include in the hash. This ensures every ID is unique. To calculate the hash, `rippled` uses SHA-512 and then truncates the result to the first 256 bits. This algorithm, informally called **SHA-512Half**, provides an output that has comparable security to SHA-256, but runs faster on 64-bit processors. Generally, a ledger object's ID is returned as the `index` field in JSON, at the same level as the object's contents. In [transaction metadata](transaction-metadata.html), the ledger object's ID in JSON is `LedgerIndex`. diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.ja.md index e2ff9e55d0..ce6c456cf0 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.ja.md @@ -6,7 +6,7 @@ labels: - ブロックチェーン --- # Amendments -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L110-L113 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L110-L113 "Source") `Amendments`オブジェクトタイプには、現在アクティブな[Amendment](amendments.html)のリストが含まれています。各レジャーバージョンには**最大で1つの** `Amendments`オブジェクトが含まれています。 @@ -65,6 +65,6 @@ labels: （`Amendments`レジャーオブジェクトタイプのIDと、個々のAmendmentのAmendment IDを混同しないでください。） -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.md b/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.md index 88117e7500..50ebdde2a6 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/amendments.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # Amendments -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L138-L144 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L138-L144 "Source") The `Amendments` object type contains a list of [Amendments](amendments.html) that are currently active. Each ledger version contains **at most one** `Amendments` object. @@ -65,6 +65,6 @@ The `Amendments` object ID is the hash of the `Amendments` space key (`0x0066`) (Don't mix up the ID of the `Amendments` ledger object type with the Amendment ID of an individual amendment.) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/check.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/check.ja.md index 2eba937e94..48fc523c47 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/check.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/check.ja.md @@ -6,7 +6,7 @@ labels: - Checks --- # Check -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L157-L170 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L157-L170 "Source") _（[Checks Amendment][]が必要です）_ @@ -56,7 +56,7 @@ _（[Checks Amendment][]が必要です）_ ## Check IDのフォーマット -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") `Check`オブジェクトのIDは、以下の値がこの順序で連結されている[SHA-512ハーフ][]です。 @@ -65,6 +65,6 @@ _（[Checks Amendment][]が必要です）_ * `Check`オブジェクトを作成した[CheckCreateトランザクション][]のシーケンス番号。 CheckCreateトランザクションが[Ticket](tickets.html)を使用する場合は、代わりに`TicketSequence`値を使用します。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/check.md b/content/references/protocol-reference/ledger-data/ledger-object-types/check.md index 7d333c33c2..88245c00a0 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/check.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/check.md @@ -6,7 +6,7 @@ labels: - Checks --- # Check -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L157-L170 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L157-L170 "Source") _(Added by the [Checks amendment][].)_ @@ -56,7 +56,7 @@ A `Check` object has the following fields: ## Check ID Format -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") The ID of a `Check` object is the [SHA-512Half][] of the following values, concatenated in order: @@ -68,6 +68,6 @@ The ID of a `Check` object is the [SHA-512Half][] of the following values, conca See the tutorial showing how to [Send a Check](send-a-check.html). -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.ja.md index 237e77eec4..810f4dd028 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.ja.md @@ -6,7 +6,7 @@ labels: - セキュリティ --- # DepositPreauth -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source") `DepositPreauth`オブジェクトはアカウント間の事前承認を追跡します。[DepositPreauthトランザクション][]によりこれらのオブジェクトが作成されます。 @@ -51,6 +51,6 @@ labels: * 事前承認されたアカウント（このオブジェクトを作成した[DepositPreauthトランザクション][]の`Authorized`フィールド、つまり事前承認を受けたユーザー）のAccountID。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.md b/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.md index d5b5748b68..58548d5a4a 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/depositpreauth.md @@ -6,7 +6,7 @@ labels: - Security --- # DepositPreauth -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source") A `DepositPreauth` object tracks a preauthorization from one account to another. [DepositPreauth transactions][] create these objects. @@ -51,6 +51,6 @@ The ID of a `DepositPreauth` object is the [SHA-512Half][] of the following valu * The AccountID of the preauthorized account (the `Authorized` field of the [DepositPreauth transaction][] that created this object; in other words, the one that received the preauthorization) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.ja.md index 0545f451b4..7bcba8973d 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.ja.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # DirectoryNode -[[ソース]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L44 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L44 "Source") `DirectoryNode`オブジェクトタイプは、レジャーの状態ツリー内の他オブジェクトへのリンクのリストを提供します。概念上の1つの _ディレクトリー_ は、1つ以上の各DirectoryNodeオブジェクトが含まれる二重リンクリストの形式になっています。各DirectoryNodeオブジェクトには、他オブジェクトの[ID](ledgers.html#ツリーの形式)が最大32個まで含まれています。1番目のオブジェクトはディレクトリーのルートと呼ばれ、ルートオブジェクト以外のオブジェクトはすべて必要に応じて自由に追加または削除できます。 @@ -104,6 +104,6 @@ DirectoryNodeのIDを作成するときには、DirectoryNodeが以下のどの * このオブジェクトのページ番号（ルートDirectoryNodeは0であるため、この値は1以上の整数値です。） -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.md b/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.md index ce7aac4f75..7861ed073a 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/directorynode.md @@ -7,7 +7,7 @@ labels: - Decentralized Exchange --- # DirectoryNode -[[Source]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L44 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L44 "Source") The `DirectoryNode` ledger entry type provides a list of links to other entries in the ledger's state data. A single conceptual _Directory_　takes the form of a doubly linked list, with one or more DirectoryNode entries each containing up to 32 [IDs of other entries](ledger-object-ids.html). The first DirectoryNode entry is called the root of the directory, and all entries other than the root can be added or deleted as necessary. @@ -105,6 +105,6 @@ The lower 64 bits of an Offer Directory's ID represent the `TakerPays` amount di * The page number of this object. (Since 0 is the root DirectoryNode, this value is an integer 1 or higher.) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.ja.md index dfe9c727a3..0a8790b6d2 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.ja.md @@ -6,7 +6,7 @@ labels: - Escrow --- # Escrow -[[ソース]](https://github.com/ripple/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") _（[Escrow Amendment][]が必要です。）_ @@ -70,6 +70,6 @@ _（[Escrow Amendment][]が必要です。）_ * `Escrow`オブジェクトを作成した[EscrowCreateトランザクション][]のシーケンス番号。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.md b/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.md index 98a4d892b2..d34c3b0a76 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/escrow.md @@ -6,7 +6,7 @@ labels: - Escrow --- # Escrow -[[Source]](https://github.com/ripple/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") _(Added by the [Escrow amendment][].)_ @@ -71,6 +71,6 @@ The ID of an `Escrow` object is the [SHA-512Half][] of the following values, con If the EscrowCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.ja.md index 4c311f4f47..2a24807d71 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.ja.md @@ -6,7 +6,7 @@ labels: - 手数料 --- # FeeSettings -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") `FeeSettings`オブジェク トタイプには、現在の基本[トランザクションコスト](transaction-cost.html)と、[手数料投票](fee-voting.html)により決定する[準備金の額](reserves.html)が含まれています。各レジャーバージョンには**最大で1つの** `FeeSettings`オブジェクトが含まれています。 @@ -51,6 +51,6 @@ labels: ``` -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.md b/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.md index cdff8ab23d..0a30811631 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/feesettings.md @@ -6,7 +6,7 @@ labels: - Fees --- # FeeSettings -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") The `FeeSettings` object type contains the current base [transaction cost](transaction-cost.html) and [reserve amounts](reserves.html) as determined by [fee voting](fee-voting.html). Each ledger version contains **at most one** `FeeSettings` object. @@ -63,6 +63,6 @@ The `FeeSettings` object ID is the hash of the `FeeSettings` space key (`0x0065` -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.ja.md index 66c2f6220c..61062a341d 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.ja.md @@ -6,7 +6,7 @@ labels: - ブロックチェーン --- # LedgerHashes -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L104-L108 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L104-L108 "Source") （レジャーバージョンを一意に示す[「ledger hash」文字列データ型][ハッシュ]と混同しないでください。このセクションでは、`LedgerHashes`レジャーオブジェクトタイプについて説明します。） @@ -64,7 +64,7 @@ labels: 「過去の履歴」`LedgerHashes`オブジェクトは[スキップリスト](https://en.wikipedia.org/wiki/Skip_list)として機能するので、任意の履歴フラッグレジャーのハッシュをそのインデックスから取得できます。さらに、フラッグレジャーの「最近の履歴」オブジェクトを使用してその他のレジャーのハッシュを取得できます。 ## LedgerHashes IDのフォーマット -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) `LedgerHashes`オブジェクトIDには2種類のフォーマットがあります。これは、オブジェクトのサブタイプが「最近の履歴」と「過去の履歴」のいずれであるかに応じて決まります。 @@ -78,6 +78,6 @@ labels: **ヒント:** 65536で割ることで最上位16ビットが維持されます。これは、「過去の履歴」オブジェクトに含まれているすべてのフラッグレジャーでのみ同一です。この点を踏まえて、フラッグレジャーのハッシュが含まれている`LedgerHashes`オブジェクトを検索できます。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.md index dde0e7fafb..24014258a2 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ledgerhashes.md @@ -6,7 +6,7 @@ labels: - Blockchain --- # LedgerHashes -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L104-L108 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L104-L108 "Source") (Not to be confused with the ["ledger hash" string data type][Hash], which uniquely identifies a ledger version. This section describes the `LedgerHashes` ledger object type.) @@ -64,7 +64,7 @@ The "previous history" `LedgerHashes` entries collectively contain the hash of e The "previous history" `LedgerHashes` objects act as a [skip list](https://en.wikipedia.org/wiki/Skip_list) so you can get the hash of any historical flag ledger from its index. From there, you can use that flag ledger's "recent history" object to get the hash of any other ledger. ## LedgerHashes ID Formats -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) There are two formats for `LedgerHashes` object IDs, depending on whether the object is a "recent history" sub-type or a "previous history" sub-type. @@ -78,6 +78,6 @@ The **"previous history"** `LedgerHashes` objects have an ID that is the [SHA-51 **Tip:** Dividing by 65536 keeps the most significant 16 bits, which are the same for all the flag ledgers listed in a "previous history" object, and only those ledgers. You can use this fact to look up the `LedgerHashes` object that contains the hash of any flag ledger. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/offer.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/offer.ja.md index a2fcef06eb..1fd92c23b9 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/offer.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/offer.ja.md @@ -6,7 +6,7 @@ labels: - 分散型取引所 --- # Offer -[[ソース]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L57 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L57 "Source") 台帳の`Offer`項目は、XRP Ledgerの[分散型取引所](decentralized-exchange.html)で通貨を交換する[オファー](offers.html)を表しています。（金融ではより伝統的に _オーダー_ として知られています）。[OfferCreateトランザクション][]は台帳にある他のOfferを全額約定できない場合、台帳に`Offer`項目を作成します。 @@ -78,6 +78,6 @@ labels: OfferCreateトランザクションが[Ticket](tickets.html)を使用した場合、代わりに`TicketSequence`値を使用します。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/offer.md b/content/references/protocol-reference/ledger-data/ledger-object-types/offer.md index b96a6e86d4..37b735f59b 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/offer.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/offer.md @@ -6,7 +6,7 @@ labels: - Decentralized Exchange --- # Offer -[[Source]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L57 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L57 "Source") The `Offer` ledger entry describes an [Offer](offers.html) to exchange currencies in the XRP Ledger's [decentralized exchange](decentralized-exchange.html). (In finance, this is more traditionally known as an _order_.) An [OfferCreate transaction][] only creates an `Offer` entry in the ledger when the Offer cannot be fully executed immediately by consuming other Offers already in the ledger. @@ -77,6 +77,6 @@ The ID of an `Offer` object is the [SHA-512Half][] of the following values, conc If the OfferCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.ja.md index a04f0180ad..1f7f72842c 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # PayChannel -[[ソース]](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") _（[PayChan Amendment][]が必要です。）_ @@ -104,6 +104,6 @@ Payment Channelの`Expiration`フィールドは、`CancelAfter`フィールド * Channelを作成したトランザクションのシーケンス番号 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.md b/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.md index 6cc17ca496..1857958e6c 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/paychannel.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # PayChannel -[[Source]](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") _(Added by the [PayChan amendment][].)_ @@ -105,6 +105,6 @@ The ID of a `PayChannel` object is the [SHA-512Half][] of the following values, If the PaymentChannelCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead. -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.ja.md index 72e9fd37b1..1f20bc79f2 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.ja.md @@ -6,7 +6,7 @@ labels: - トークン --- # RippleState -[[ソース]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L70 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L70 "Source") `RippleState`オブジェクトタイプは、1つの通貨で2つのアカウントを接続します。概念的には`RippleState`オブジェクトは、アカウント間の2つの _トラストライン_ を表し、各アカウント側から1つずつ確立されます。各アカウントの`RippleState`オブジェクト設定は、各アカウント側で変更できますが、残高については単一の値を両アカウント間で共有します。完全にデフォルト状態のトラストラインは、存在しないトラストラインと同様に見なされます。このため`rippled` は、プロパティがすべてデフォルトである`RippleState`オブジェクトを削除します。 @@ -111,6 +111,6 @@ RippleStateオブジェクトのIDは、以下の値がこの順序で連結さ * トラストラインの160ビットの通貨コード -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.md index 6009dbb644..7e4cc50b49 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ripplestate.md @@ -6,7 +6,7 @@ labels: - Tokens --- # RippleState -[[Source]](https://github.com/ripple/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L70 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L70 "Source") The `RippleState` object type connects two accounts in a single currency. Conceptually, a `RippleState` object represents two [trust lines](trust-lines-and-issuing.html) between the accounts, one from each side. Each account can change the settings for its side of the `RippleState` object, but the balance is a single shared value. A trust line that is entirely in its default state is considered the same as a trust line that does not exist, so `rippled` deletes `RippleState` objects when their properties are entirely default. @@ -116,6 +116,6 @@ The ID of a RippleState object is the [SHA-512Half][] of the following values, c * The 160-bit currency code of the trust line(s) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.ja.md index c1a828dcdf..0937f2fb24 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.ja.md @@ -6,7 +6,7 @@ labels: - セキュリティ --- # SignerList -[[ソース]](https://github.com/ripple/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") _（[MultiSign Amendment][]が必要です。）_ @@ -106,6 +106,6 @@ SignerListオブジェクトのIDは、以下の値がこの順序で連結さ * SignerListID（現時点では常に`0`） -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.md b/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.md index f6e965c7f7..148ae17c50 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/signerlist.md @@ -6,7 +6,7 @@ labels: - Security --- # SignerList -[[Source]](https://github.com/ripple/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") _(Added by the [MultiSign amendment][].)_ @@ -104,6 +104,6 @@ The ID of a signer list object is the SHA-512Half of the following values, conca * The `SignerListID` (currently always `0`) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.ja.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.ja.md index bd6400a2c8..9b2c304217 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.ja.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.ja.md @@ -7,7 +7,7 @@ labels: --- # Ticket -[[ソース]](https://github.com/ripple/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164) +[[ソース]](https://github.com/XRPLF/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164) _([TicketBatch amendment][]が必要です)_ diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.md b/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.md index 75b403e5c5..f487224382 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/ticket.md @@ -7,7 +7,7 @@ labels: --- # Ticket -[[Source]](https://github.com/ripple/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164) +[[Source]](https://github.com/XRPLF/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164) _(Added by the [TicketBatch amendment][].)_ diff --git a/content/references/protocol-reference/serialization.ja.md b/content/references/protocol-reference/serialization.ja.md index 79a8e80b53..14c33f46ed 100644 --- a/content/references/protocol-reference/serialization.ja.md +++ b/content/references/protocol-reference/serialization.ja.md @@ -14,7 +14,7 @@ curated_anchors: anchor: "#タイプリスト" --- # シリアル化フォーマット -[[ソース]](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp#L696-L718 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp#L696-L718 "Source") このページでは、XRP Ledgerのトランザクションとその他のデータの正規バイナリフォーマットについて説明します。このバイナリフォーマットは、トランザクションの内容のデジタル署名を作成および検証するために必要であり、[サーバー間のピアツーピア通信](peer-protocol.html)を含む他の用途にも使用されます。通常、[`rippled` API](http-websocket-apis.html)は、JSONを使用してクライアントアプリケーションと通信します。ただしJSONは、同じデータをさまざまな同等の方法で表現できるため、デジタル署名を付与するトランザクションをシリアル化するのに適したフォーマットではありません。 @@ -58,7 +58,7 @@ curated_anchors: ここで説明するシリアル化プロセスは複数の場所にさまざまなプログラミング言語で実装されています。 -- C++: [`rippled`コードベース](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp) +- C++: [`rippled`コードベース](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp) - JavaScript: [`ripple-binary-codec`](https://github.com/ripple/ripple-binary-codec/)パッケージ - Python 3: [このリポジトリのコードサンプルセクション]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/) @@ -68,7 +68,7 @@ curated_anchors: ## 内部フォーマット -各フィールドには「内部」バイナリフォーマットがあります。このフォーマットは、`rippled`ソースコードで署名時に（およびその他のほとんどの場合に）そのフィールドを表示するのに使用されます。すべてのフィールドの内部フォーマットは、[`SField.cpp`](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/SField.cpp)のソースコードに定義されています。（このフィールドには、トランザクションフィールド以外のフィールドも含まれています。）[トランザクションフォーマットリファレンス](transaction-formats.html)にも、すべてのトランザクションフィールドの内部フォーマットが記載されています。 +各フィールドには「内部」バイナリフォーマットがあります。このフォーマットは、`rippled`ソースコードで署名時に（およびその他のほとんどの場合に）そのフィールドを表示するのに使用されます。すべてのフィールドの内部フォーマットは、[`SField.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/SField.cpp)のソースコードに定義されています。（このフィールドには、トランザクションフィールド以外のフィールドも含まれています。）[トランザクションフォーマットリファレンス](transaction-formats.html)にも、すべてのトランザクションフィールドの内部フォーマットが記載されています。 たとえば`Flags`[共通トランザクションフィールド](transaction-common-fields.html)はUInt32（32ビット符号なし整数）になります。 @@ -154,17 +154,17 @@ curated_anchors: ### タイプコード -各フィールドタイプには任意のタイプコードが含まれており、番号が小さいコードから最初にソートされます。これらのコードは[`SField.h`](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/SField.h#L57-L74)で定義されています。 +各フィールドタイプには任意のタイプコードが含まれており、番号が小さいコードから最初にソートされます。これらのコードは[`SField.h`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/SField.h#L57-L74)で定義されています。 -たとえば [UInt32のタイプコードが2である](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L59)ので、すべてのUInt32フィールドは、すべての[Amountフィールド（タイプコード6）](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L63)よりも前に位置します。 +たとえば [UInt32のタイプコードが2である](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L59)ので、すべてのUInt32フィールドは、すべての[Amountフィールド（タイプコード6）](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L63)よりも前に位置します。 [定義ファイル](#定義ファイル)には、`TYPES`マップの各タイプのタイプコードがリストされています。 ### フィールドコード -各フィールドにはフィールドコードが含まれています。フィールドコードは、同じタイプのフィールドをソートするときに使用され、番号が小さいコードが最初になるようにソートされます。これらのフィールドは[`SField.cpp`](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L72-L266)で定義されています。 +各フィールドにはフィールドコードが含まれています。フィールドコードは、同じタイプのフィールドをソートするときに使用され、番号が小さいコードが最初になるようにソートされます。これらのフィールドは[`SField.cpp`](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L72-L266)で定義されています。 -たとえば[Paymentトランザクション][]の`Account`フィールドの[ソートコードが1である](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L219)場合、このフィールドは`Destination`フィールド（[ソートコードが3である](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L221)フィールド）よりも前に位置します。 +たとえば[Paymentトランザクション][]の`Account`フィールドの[ソートコードが1である](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L219)場合、このフィールドは`Destination`フィールド（[ソートコードが3である](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L221)フィールド）よりも前に位置します。 フィールドコードは異なるフィールドタイプのフィールドで再利用されますが、同じタイプのフィールドに同じフィールドコードが含まれることはありません。タイプコードとフィールドコードを組み合わせると、フィールドの一意の[フィールドID](#フィールドid)になります。 @@ -274,7 +274,7 @@ XRP LedgerのハッシュタイプにはHash128、Hash160、Hash256がありま [STIssue]: #issueフィールド --> - @@ -301,12 +301,12 @@ Some fields specify a _type_ of asset, which could be XRP or a fungible [token]( 複数通貨間[Paymentトランザクション][]の`Paths`フィールドは、JSONで配列からなる配列として表される「PathSet」です。使用されるパスについての詳細は、[パス](paths.html)を参照してください。 -PathSetは、**1～6**の個別パスとして順序どおりにシリアル化されます[[ソース]](https://github.com/ripple/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source")。それぞれの完全なパスの後には、パスの後に続く内容を示すバイトが配置されます。 +PathSetは、**1～6**の個別パスとして順序どおりにシリアル化されます[[ソース]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source")。それぞれの完全なパスの後には、パスの後に続く内容を示すバイトが配置されます。 - `0xff`は別のパスが続くことを示します。 - `0x00`はPathSetの終わりを示します。 -各パスには**1～8**のパスステップがこの順序で含まれています[[ソース]](https://github.com/ripple/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source")。各ステップは**タイプ**を示すバイトで始まり、その後にパスステップを記述する1つ以上のフィールドが続きます。タイプは、ビット単位のフラグを使用してそのパスステップに含まれるフィールドを示します。（たとえば値が`0x30`の場合、通貨とイシュアーの両方が変更されます。）複数のフィールドが含まれている場合、フィールドは常に特定の順序で配置されます。 +各パスには**1～8**のパスステップがこの順序で含まれています[[ソース]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source")。各ステップは**タイプ**を示すバイトで始まり、その後にパスステップを記述する1つ以上のフィールドが続きます。タイプは、ビット単位のフラグを使用してそのパスステップに含まれるフィールドを示します。（たとえば値が`0x30`の場合、通貨とイシュアーの両方が変更されます。）複数のフィールドが含まれている場合、フィールドは常に特定の順序で配置されます。 以下の表に、有効なフィールドと、タイプバイトでフィールドを示すために設定されるビット単位のフラグを示します。 @@ -342,6 +342,6 @@ JSONオブジェクトにこれらのフィールドが含まれている場合 もう1つの特殊なケースとして`TransactionType`フィールドがあります。JSONではこのフィールドは便宜上、トランザクションタイプの名前の文字列として表現されますが、バイナリではこのフィールドはUInt16です。[定義ファイル](#定義ファイル)内の`TRANSACTION_TYPES`オブジェクトにより、これらの文字列が特定の数値にマップされます。 -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/references/protocol-reference/serialization.md b/content/references/protocol-reference/serialization.md index fa7e0a6e09..fbeba09d62 100644 --- a/content/references/protocol-reference/serialization.md +++ b/content/references/protocol-reference/serialization.md @@ -14,7 +14,7 @@ curated_anchors: anchor: "#type-list" --- # Serialization Format -[[Source]](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp#L696-L718 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp#L696-L718 "Source") This page describes the XRP Ledger's canonical binary format for transactions and other data. This binary format is necessary to create and verify digital signatures of those transactions' contents, and is also used in other places including in the [peer-to-peer communications between servers](peer-protocol.html). The [`rippled` APIs](http-websocket-apis.html) typically use JSON to communicate with client applications. However, JSON is unsuitable as a format for serializing transactions for being digitally signed, because JSON can represent the same data in many different but equivalent ways. @@ -58,7 +58,7 @@ Both signed and unsigned transactions can be represented in both JSON and binary The serialization processes described here are implemented in multiple places and programming languages: -- In C++ [in the `rippled` code base](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp). +- In C++ [in the `rippled` code base](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp). - In JavaScript in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/). - In Python 3 in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/). @@ -68,7 +68,7 @@ Additionally, many [client libraries](client-libraries.html) provide serializati ## Internal Format -Each field has an "internal" binary format used in the `rippled` source code to represent that field when signing (and in most other cases). The internal formats for all fields are defined in the source code of [`SField.cpp`](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/SField.cpp). (This file also includes fields other than transaction fields.) The [Transaction Format Reference](transaction-formats.html) also lists the internal formats for all transaction fields. +Each field has an "internal" binary format used in the `rippled` source code to represent that field when signing (and in most other cases). The internal formats for all fields are defined in the source code of [`SField.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/SField.cpp). (This file also includes fields other than transaction fields.) The [Transaction Format Reference](transaction-formats.html) also lists the internal formats for all transaction fields. For example, the `Flags` [common transaction field](transaction-common-fields.html) becomes a UInt32 (32-bit unsigned integer). @@ -154,17 +154,17 @@ All fields in a transaction are sorted in a specific order based first on the fi ### Type Codes -Each field type has an arbitrary type code, with lower codes sorting first. These codes are defined in [`SField.h`](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/SField.h#L57-L74). +Each field type has an arbitrary type code, with lower codes sorting first. These codes are defined in [`SField.h`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/SField.h#L57-L74). -For example, [UInt32 has type code 2](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L59), so all UInt32 fields come before all [Amount fields, which have type code 6](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L63). +For example, [UInt32 has type code 2](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L59), so all UInt32 fields come before all [Amount fields, which have type code 6](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/SField.h#L63). The [definitions file](#definitions-file) lists the type codes for each type in the `TYPES` map. ### Field Codes -Each field has a field code, which is used to sort fields that have the same type as one another, with lower codes sorting first. These fields are defined in [`SField.cpp`](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L72-L266). +Each field has a field code, which is used to sort fields that have the same type as one another, with lower codes sorting first. These fields are defined in [`SField.cpp`](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L72-L266). -For example, the `Account` field of a [Payment transaction][] [has sort code 1](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L219), so it comes before the `Destination` field which [has sort code 3](https://github.com/ripple/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L221). +For example, the `Account` field of a [Payment transaction][] [has sort code 1](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L219), so it comes before the `Destination` field which [has sort code 3](https://github.com/XRPLF/rippled/blob/72e6005f562a8f0818bc94803d222ac9345e1e40/src/ripple/protocol/impl/SField.cpp#L221). Field codes are reused for fields of different field types, but fields of the same type never have the same field code. When you combine the type code with the field code, you get the field's unique [Field ID](#field-ids). @@ -237,7 +237,7 @@ The following diagram shows the serialization formats for both XRP amounts and t {{ include_svg("img/serialization-amount.svg", 'XRP amounts have a "not XRP" bit, a sign bit, and 62 bits of precision. Token amounts consist of a "not XRP" bit, a sign bit, an exponent (8 bits), significant digits (54 bits), currency code (160 bits), and issuer (160 bits).') }} #### Token Amount Format -[[Source]](https://github.com/ripple/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source") {{ include_svg("img/currency-number-format.svg", "Token Amount Format diagram") }} @@ -328,12 +328,12 @@ The following example shows the serialization format for an object (a single `Me The `Paths` field of a cross-currency [Payment transaction][] is a "PathSet", represented in JSON as an array of arrays. For more information on what paths are used for, see [Paths](paths.html). -A PathSet is serialized as **1 to 6** individual paths in sequence[[Source]](https://github.com/ripple/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source"). Each complete path is followed by a byte that indicates what comes next: +A PathSet is serialized as **1 to 6** individual paths in sequence[[Source]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source"). Each complete path is followed by a byte that indicates what comes next: - `0xff` indicates another path follows - `0x00` indicates the end of the PathSet -Each path consists of **1 to 8** path steps in order[[Source]](https://github.com/ripple/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source"). Each step starts with a **type** byte, followed by one or more fields describing the path step. The type indicates which fields are present in that path step through bitwise flags. (For example, the value `0x30` indicates changing both currency and issuer.) If more than one field is present, the fields are always placed in a specific order. +Each path consists of **1 to 8** path steps in order[[Source]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source"). Each step starts with a **type** byte, followed by one or more fields describing the path step. The type indicates which fields are present in that path step through bitwise flags. (For example, the value `0x30` indicates changing both currency and issuer.) If more than one field is present, the fields are always placed in a specific order. The following table describes the possible fields and the bitwise flags to set in the type byte to indicate them: diff --git a/content/references/protocol-reference/transactions/transaction-results/tec-codes.ja.md b/content/references/protocol-reference/transactions/transaction-results/tec-codes.ja.md index 8a2566e4dd..dd3b23e31e 100644 --- a/content/references/protocol-reference/transactions/transaction-results/tec-codes.ja.md +++ b/content/references/protocol-reference/transactions/transaction-results/tec-codes.ja.md @@ -28,8 +28,8 @@ labels: | `tecINSUF_RESERVE_OFFER` | 123 | 送信側アカウントに、新しいオファーを作成するのに十分なXRPがないため、トランザクションが失敗しました。（[準備金](reserves.html)を参照してください。) | | `tecINSUFF_FEE` | 136 | 指定された[トランザクションコスト](transaction-cost.html)を支払うのに十分なXRPが送金元アカウントにないため、トランザクションが失敗しました。（この場合、送金元のXRPが指定されたトランザクションコストよりも低い場合でも、トランザクション処理によってすべて消却されます。）この結果は、このトランザクションがコンセンサスセットに含まれるのに十分なネットワークに配布された*後に*アカウントの残高が減少した場合にのみ発生します。そうでない場合、トランザクションは配布される前に[`terINSUF_FEE_B`](ter-codes.html)で失敗します。 | | `tecINSUFFICIENT_RESERVE` | 141 | トランザクションによって[必要準備金](reserves.html)が増加し、送信側アカウントの残高を超える可能性があります。[SignerListSet][]、[PaymentChannelCreate][]、[PaymentChannelFund][]、および[EscrowCreate][]からこのエラーコードが返されることがあります。詳細は、[SignerListと準備金](signerlist.html#signerlistと準備金)を参照してください。 | -| `tecINTERNAL` | 144 | 不明な内部エラーが発生し、トランザクションコストは適用されました。通常はこのエラーは返されません。このエラーを再現できる場合は、[問題を報告](https://github.com/ripple/rippled/issues)してください。 | -| `tecINVARIANT_FAILED` | 147 | このトランザクションを実行しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]が必要です。このエラーを再現できる場合は、[問題を報告](https://github.com/ripple/rippled/issues)してください。 | +| `tecINTERNAL` | 144 | 不明な内部エラーが発生し、トランザクションコストは適用されました。通常はこのエラーは返されません。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | +| `tecINVARIANT_FAILED` | 147 | このトランザクションを実行しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]が必要です。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tecKILLED` | 150 | [OfferCreateトランザクション][]がtfFillOrKillフラグを指定しましたが、トランザクションを確定できなかったため、このトランザクションは取り消されました。_（[fix1578 Amendment][]が必要です。）_ | | `tecNEED_MASTER_KEY` | 142 | このトランザクションはマスターキーを必要とする変更（[マスターキーの無効化または残高凍結能力の放棄](accountset.html#accountsetのフラグ)など）を試みました。[新規: rippled 0.28.0][] | | `tecNO_ALTERNATIVE_KEY` | 130 | トランザクションが唯一の[トランザクション承認](transactions.html#トランザクションの承認)メソッドを削除しようとしました。これは、レギュラーキーを削除する[SetRegularKeyトランザクション][]、SignerListを削除する[SignerListSetトランザクション][]、またはマスターキーを無効にする[AccountSetトランザクション][]である可能性があります。（`rippled` 0.30.0より前のバージョンでは、このトランザクションは`tecMASTER_DISABLED`と呼ばれていました。） | diff --git a/content/references/protocol-reference/transactions/transaction-results/tec-codes.md b/content/references/protocol-reference/transactions/transaction-results/tec-codes.md index 07f4957588..3d22fe70ff 100644 --- a/content/references/protocol-reference/transactions/transaction-results/tec-codes.md +++ b/content/references/protocol-reference/transactions/transaction-results/tec-codes.md @@ -38,8 +38,8 @@ Transactions with `tec` codes destroy the XRP paid as a [transaction cost](trans | `tecINSUFFICIENT_FUNDS` | 158 | One of the accounts involved does not hold enough of a necessary asset. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | | `tecINSUFFICIENT_PAYMENT` | 161 | The amount specified is not enough to pay all fees involved in the transaction. For example, when trading a non-fungible token, the buy amount may not be enough to pay both the broker fee and the sell amount. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | | `tecINSUFFICIENT_RESERVE` | 141 | The transaction would increase the [reserve requirement](reserves.html) higher than the sending account's balance. [SignerListSet][], [PaymentChannelCreate][], [PaymentChannelFund][], and [EscrowCreate][] can return this error code. See [Signer Lists and Reserves](signerlist.html#signer-lists-and-reserves) for more information. | -| `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). | -| `tecINVARIANT_FAILED` | 147 | An invariant check failed when trying to execute this transaction. Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). | +| `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | +| `tecINVARIANT_FAILED` | 147 | An invariant check failed when trying to execute this transaction. Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | | `tecKILLED` | 150 | The [OfferCreate transaction][] specified the `tfFillOrKill` flag and could not be filled, so it was killed. _(Added by the [fix1578 amendment][].)_ | | `tecMAX_SEQUENCE_REACHED` | 153 | A sequence number field is already at its maximum. This includes the `MintedNFTokens` field. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | | `tecNEED_MASTER_KEY` | 142 | This transaction tried to cause changes that require the master key, such as [disabling the master key or giving up the ability to freeze balances](accountset.html#accountset-flags). | diff --git a/content/references/protocol-reference/transactions/transaction-results/tef-codes.ja.md b/content/references/protocol-reference/transactions/transaction-results/tef-codes.ja.md index 067a4f6b50..a56c4ecfee 100644 --- a/content/references/protocol-reference/transactions/transaction-results/tef-codes.ja.md +++ b/content/references/protocol-reference/transactions/transaction-results/tef-codes.ja.md @@ -17,14 +17,14 @@ labels: | `tefBAD_ADD_AUTH` | **廃止予定。** | | `tefBAD_AUTH` | このアカウントの署名に使用したキーには、このアカウントを変更する権限がありません。（このアカウントが[レギュラーキー](cryptographic-keys.html)として同じキーセットを持っている場合は変更が承認される可能性があります。） | | `tefBAD_AUTH_MASTER` | このトランザクションを承認するために指定された1つの署名がマスターキーと一致していませんが、このアドレスに関連付けられているレギュラーキーもありません。 | -| `tefBAD_LEDGER` | トランザクションの処理中に、レジャーが予期しない状態にあることが検出されました。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/ripple/rippled/issues)してください。 | +| `tefBAD_LEDGER` | トランザクションの処理中に、レジャーが予期しない状態にあることが検出されました。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tefBAD_QUORUM` | トランザクションは[マルチシグ](multi-signing.html)トランザクションでしたが、そこに含まれるすべての署名の重みの合計が定数を満たしていません。 | | `tefBAD_SIGNATURE` | トランザクションは[マルチシグ](multi-signing.html)トランザクションでしたが、送信側アカウントに関連付けられているSignerListにないアドレスの署名が含まれていました。 | | `tefCREATED` | **廃止予定。** | -| `tefEXCEPTION` | トランザクションの処理中に、サーバーが予期しない状態になりました。この状態は、予期しない入力（トランザクションのバイナリーデータの形式が大幅に誤っている場合など）が原因となった可能性があります。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/ripple/rippled/issues)してください。 | +| `tefEXCEPTION` | トランザクションの処理中に、サーバーが予期しない状態になりました。この状態は、予期しない入力（トランザクションのバイナリーデータの形式が大幅に誤っている場合など）が原因となった可能性があります。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tefFAILURE` | トランザクション適用中の不明な障害。 | -| `tefINTERNAL` | トランザクションの適用を試みた際に、サーバーが予期しない状態になりました。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/ripple/rippled/issues)してください。 | -| `tefINVARIANT_FAILED` | [トランザクションコスト](transaction-cost.html)を請求しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]が必要です。このエラーを再現できる場合は、[問題を報告](https://github.com/ripple/rippled/issues)してください。 | +| `tefINTERNAL` | トランザクションの適用を試みた際に、サーバーが予期しない状態になりました。このエラーを再現できる場合は、修正のため[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | +| `tefINVARIANT_FAILED` | [トランザクションコスト](transaction-cost.html)を請求しようとしたところ、不変性チェックが失敗しました。[EnforceInvariants Amendment][]が必要です。このエラーを再現できる場合は、[問題を報告](https://github.com/XRPLF/rippled/issues)してください。 | | `tefMASTER_DISABLED` | トランザクションはアカウントのマスターキーで署名されていましたが、アカウントに`lsfDisableMaster`フィールドが設定されていました。 | | `tefMAX_LEDGER` | トランザクションには[`LastLedgerSequence`](reliable-transaction-submission.html#lastledgersequence)パラメーターが指定されていましたが、現在のレジャーのシーケンス番号はすでに指定値を上回っています。 | | `tefNO_AUTH_REQUIRED` | [TrustSetトランザクション][]がトラストラインを承認済みとしてマークしようとしましたが、対応するアカウントに対して`lsfRequireAuth`フラグが有効になっていないため、承認は不要です。 | diff --git a/content/references/protocol-reference/transactions/transaction-results/tef-codes.md b/content/references/protocol-reference/transactions/transaction-results/tef-codes.md index 0b6972a184..1ff7eb84eb 100644 --- a/content/references/protocol-reference/transactions/transaction-results/tef-codes.md +++ b/content/references/protocol-reference/transactions/transaction-results/tef-codes.md @@ -18,14 +18,14 @@ These codes indicate that the transaction failed and was not included in a ledge | `tefBAD_ADD_AUTH` | **DEPRECATED.** | | `tefBAD_AUTH` | The key used to sign this account is not authorized to modify this account. (It could be authorized if the account had the same key set as the [Regular Key](cryptographic-keys.html).) | | `tefBAD_AUTH_MASTER` | The single signature provided to authorize this transaction does not match the master key, but no regular key is associated with this address. | -| `tefBAD_LEDGER` | While processing the transaction, the ledger was discovered in an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues) to get it fixed. | +| `tefBAD_LEDGER` | While processing the transaction, the ledger was discovered in an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues) to get it fixed. | | `tefBAD_QUORUM` | The transaction was [multi-signed](multi-signing.html), but the total weights of all included signatures did not meet the quorum. | | `tefBAD_SIGNATURE` | The transaction was [multi-signed](multi-signing.html), but contained a signature for an address not part of a SignerList associated with the sending account. | | `tefCREATED` | **DEPRECATED.** | -| `tefEXCEPTION` | While processing the transaction, the server entered an unexpected state. This may be caused by unexpected inputs, for example if the binary data for the transaction is grossly malformed. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues) to get it fixed. | +| `tefEXCEPTION` | While processing the transaction, the server entered an unexpected state. This may be caused by unexpected inputs, for example if the binary data for the transaction is grossly malformed. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues) to get it fixed. | | `tefFAILURE` | Unspecified failure in applying the transaction. | -| `tefINTERNAL` | When trying to apply the transaction, the server entered an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues) to get it fixed. | -| `tefINVARIANT_FAILED` | An invariant check failed when trying to claim the [transaction cost](transaction-cost.html). Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). | +| `tefINTERNAL` | When trying to apply the transaction, the server entered an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues) to get it fixed. | +| `tefINVARIANT_FAILED` | An invariant check failed when trying to claim the [transaction cost](transaction-cost.html). Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). | | `tefMASTER_DISABLED` | The transaction was signed with the account's master key, but the account has the `lsfDisableMaster` field set. | | `tefMAX_LEDGER` | The transaction included a [`LastLedgerSequence`](reliable-transaction-submission.html#lastledgersequence) parameter, but the current ledger's sequence number is already higher than the specified value. | | `tefNFTOKEN_IS_NOT_TRANSFERABLE` | The transaction attempted to send a [non-fungible token](non-fungible-tokens.html) to another account, but the `NFToken` has the `lsfTransferable` flag disabled and the transfer would not be to or from the issuer. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ | diff --git a/content/references/protocol-reference/transactions/transaction-results/transaction-results.ja.md b/content/references/protocol-reference/transactions/transaction-results/transaction-results.ja.md index a3c1e09176..6ee0380b9d 100644 --- a/content/references/protocol-reference/transactions/transaction-results/transaction-results.ja.md +++ b/content/references/protocol-reference/transactions/transaction-results/transaction-results.ja.md @@ -7,7 +7,7 @@ labels: --- # トランザクションの結果 -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/TER.h "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/TER.h "Source") `rippled`サーバーは、トランザクション結果の要約を結果コードで示し、結果コードは`engine_result`や`meta.TransactionResult`などのフィールドに記述されます。これらのコードは、それぞれ異なるプレフィクスを付加した複数のカテゴリーに分類されます。 diff --git a/content/references/protocol-reference/transactions/transaction-results/transaction-results.md b/content/references/protocol-reference/transactions/transaction-results/transaction-results.md index 65073e171f..73359af9bb 100644 --- a/content/references/protocol-reference/transactions/transaction-results/transaction-results.md +++ b/content/references/protocol-reference/transactions/transaction-results/transaction-results.md @@ -7,7 +7,7 @@ labels: --- # Transaction Results -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/TER.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/TER.h "Source") The `rippled` server summarizes transaction results with result codes, which appear in fields such as `engine_result` and `meta.TransactionResult`. These codes are grouped into several categories of with different prefixes: diff --git a/content/references/protocol-reference/transactions/transaction-types/accountdelete.ja.md b/content/references/protocol-reference/transactions/transaction-types/accountdelete.ja.md index 50b92d1287..7f96288d38 100644 --- a/content/references/protocol-reference/transactions/transaction-types/accountdelete.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/accountdelete.ja.md @@ -7,7 +7,7 @@ labels: --- # AccountDelete -[[ソース]](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/DeleteAccount.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/app/tx/impl/DeleteAccount.cpp "Source") _[DeletableAccounts Amendment](known-amendments.html#deletableaccounts)が必要です_ diff --git a/content/references/protocol-reference/transactions/transaction-types/accountdelete.md b/content/references/protocol-reference/transactions/transaction-types/accountdelete.md index 42925a69c0..3a130c46d7 100644 --- a/content/references/protocol-reference/transactions/transaction-types/accountdelete.md +++ b/content/references/protocol-reference/transactions/transaction-types/accountdelete.md @@ -7,7 +7,7 @@ labels: --- # AccountDelete -[[Source]](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/DeleteAccount.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/app/tx/impl/DeleteAccount.cpp "Source") _Added by the [DeletableAccounts amendment](known-amendments.html#deletableaccounts)_ diff --git a/content/references/protocol-reference/transactions/transaction-types/checkcancel.ja.md b/content/references/protocol-reference/transactions/transaction-types/checkcancel.ja.md index 83fd7bca90..903a16ef0a 100644 --- a/content/references/protocol-reference/transactions/transaction-types/checkcancel.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/checkcancel.ja.md @@ -6,7 +6,7 @@ labels: - Checks --- # CheckCancel -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CancelCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CancelCheck.cpp "Source") _（[Checks Amendment][]が必要です）_ diff --git a/content/references/protocol-reference/transactions/transaction-types/checkcancel.md b/content/references/protocol-reference/transactions/transaction-types/checkcancel.md index fc2e0c4866..cf055b2038 100644 --- a/content/references/protocol-reference/transactions/transaction-types/checkcancel.md +++ b/content/references/protocol-reference/transactions/transaction-types/checkcancel.md @@ -6,7 +6,7 @@ labels: - Checks --- # CheckCancel -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CancelCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CancelCheck.cpp "Source") _(Added by the [Checks amendment][].)_ diff --git a/content/references/protocol-reference/transactions/transaction-types/checkcash.ja.md b/content/references/protocol-reference/transactions/transaction-types/checkcash.ja.md index 63fac02bc3..938390d624 100644 --- a/content/references/protocol-reference/transactions/transaction-types/checkcash.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/checkcash.ja.md @@ -6,7 +6,7 @@ labels: - Checks --- # CheckCash -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CashCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CashCheck.cpp "Source") _（[Checks Amendment][]が必要です）_ diff --git a/content/references/protocol-reference/transactions/transaction-types/checkcash.md b/content/references/protocol-reference/transactions/transaction-types/checkcash.md index 502854a4ba..53d5cce3b2 100644 --- a/content/references/protocol-reference/transactions/transaction-types/checkcash.md +++ b/content/references/protocol-reference/transactions/transaction-types/checkcash.md @@ -6,7 +6,7 @@ labels: - Checks --- # CheckCash -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CashCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CashCheck.cpp "Source") _(Added by the [Checks amendment][].)_ diff --git a/content/references/protocol-reference/transactions/transaction-types/checkcreate.md b/content/references/protocol-reference/transactions/transaction-types/checkcreate.md index 9d026b4c4a..f237c9db62 100644 --- a/content/references/protocol-reference/transactions/transaction-types/checkcreate.md +++ b/content/references/protocol-reference/transactions/transaction-types/checkcreate.md @@ -6,7 +6,7 @@ labels: - Checks --- # CheckCreate -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CreateCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CreateCheck.cpp "Source") _(Added by the [Checks amendment][].)_ diff --git a/content/references/protocol-reference/transactions/transaction-types/depositpreauth.ja.md b/content/references/protocol-reference/transactions/transaction-types/depositpreauth.ja.md index e8d280071e..363af9fbdf 100644 --- a/content/references/protocol-reference/transactions/transaction-types/depositpreauth.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/depositpreauth.ja.md @@ -6,7 +6,7 @@ labels: - セキュリティ --- # DepositPreauth -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/DepositPreauth.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/DepositPreauth.cpp "Source") _[DepositPreauth Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/depositpreauth.md b/content/references/protocol-reference/transactions/transaction-types/depositpreauth.md index 4455b54399..503f5a806f 100644 --- a/content/references/protocol-reference/transactions/transaction-types/depositpreauth.md +++ b/content/references/protocol-reference/transactions/transaction-types/depositpreauth.md @@ -6,7 +6,7 @@ labels: - Security --- # DepositPreauth -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/DepositPreauth.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/DepositPreauth.cpp "Source") _Added by the [DepositPreauth amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowcancel.ja.md b/content/references/protocol-reference/transactions/transaction-types/escrowcancel.ja.md index bb74ffff21..f56691a968 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowcancel.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowcancel.ja.md @@ -7,7 +7,7 @@ labels: --- # EscrowCancel -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _[Escrow Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowcancel.md b/content/references/protocol-reference/transactions/transaction-types/escrowcancel.md index 798e35d3e7..226854fbe3 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowcancel.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowcancel.md @@ -7,7 +7,7 @@ labels: --- # EscrowCancel -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _Added by the [Escrow amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowcreate.ja.md b/content/references/protocol-reference/transactions/transaction-types/escrowcreate.ja.md index 076ee0a0a8..d67a59aadd 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowcreate.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowcreate.ja.md @@ -7,7 +7,7 @@ labels: --- # EscrowCreate -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _[Escrow Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowcreate.md b/content/references/protocol-reference/transactions/transaction-types/escrowcreate.md index b35b4c3879..7466c0aff6 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowcreate.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowcreate.md @@ -7,7 +7,7 @@ labels: --- # EscrowCreate -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _Added by the [Escrow amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowfinish.ja.md b/content/references/protocol-reference/transactions/transaction-types/escrowfinish.ja.md index ddfba9e198..2b19cb175b 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowfinish.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowfinish.ja.md @@ -7,7 +7,7 @@ labels: --- # EscrowFinish -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _[Escrow Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/escrowfinish.md b/content/references/protocol-reference/transactions/transaction-types/escrowfinish.md index 8d52c06248..476e260d36 100644 --- a/content/references/protocol-reference/transactions/transaction-types/escrowfinish.md +++ b/content/references/protocol-reference/transactions/transaction-types/escrowfinish.md @@ -7,7 +7,7 @@ labels: --- # EscrowFinish -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/Escrow.cpp "Source") _Added by the [Escrow amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokenmint.ja.md b/content/references/protocol-reference/transactions/transaction-types/nftokenmint.ja.md index 892d0f8936..397c9f1135 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokenmint.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokenmint.ja.md @@ -6,7 +6,7 @@ labels: - 非代替性トークン, NFT --- # NFTokenMint -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/NFTokenMint.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/NFTokenMint.cpp "Source") `NFTokenMint`トランザクションは非代替性トークンを作成し、`NFTokenMinter`に紐付く[NFTokenPageオブジェクト][]に[NFToken][]オブジェクトとして追加します。このトランザクションの必須パラメータは`Token`フィールドで、実際のトークンを指定します。このトランザクションは`NFTokenMinter`にとって、不変と定義されているトークンフィールド(例えば`Flags`)を設定することができる唯一の方法です。 diff --git a/content/references/protocol-reference/transactions/transaction-types/offercancel.ja.md b/content/references/protocol-reference/transactions/transaction-types/offercancel.ja.md index c49eb60705..7373d3a8bb 100644 --- a/content/references/protocol-reference/transactions/transaction-types/offercancel.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/offercancel.ja.md @@ -7,7 +7,7 @@ labels: --- # OfferCancel -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CancelOffer.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CancelOffer.cpp "Source") OfferCancelトランザクションは、XRP LedgerからOfferオブジェクトを削除します。 diff --git a/content/references/protocol-reference/transactions/transaction-types/offercancel.md b/content/references/protocol-reference/transactions/transaction-types/offercancel.md index 136a5e5bbd..6f400d7782 100644 --- a/content/references/protocol-reference/transactions/transaction-types/offercancel.md +++ b/content/references/protocol-reference/transactions/transaction-types/offercancel.md @@ -7,7 +7,7 @@ labels: --- # OfferCancel -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/CancelOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/CancelOffer.cpp "Source") An OfferCancel transaction removes an Offer object from the XRP Ledger. diff --git a/content/references/protocol-reference/transactions/transaction-types/payment.ja.md b/content/references/protocol-reference/transactions/transaction-types/payment.ja.md index 2e756613cb..af4694fd66 100644 --- a/content/references/protocol-reference/transactions/transaction-types/payment.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/payment.ja.md @@ -9,7 +9,7 @@ labels: - トークン --- # Payment -[[ソース]](https://github.com/ripple/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/transactors/Payment.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/transactors/Payment.cpp "ソース") Paymentトランザクションは、アカウント間での価値の移動を表現するものです(通過するパスによっては、非可分的に発生する追加的な価値交換を伴うことがあります)。このトランザクションタイプはいくつかの[支払いの種類](#paymentの種類)に使用することがでできます。 diff --git a/content/references/protocol-reference/transactions/transaction-types/payment.md b/content/references/protocol-reference/transactions/transaction-types/payment.md index 53be251510..58d3e980a7 100644 --- a/content/references/protocol-reference/transactions/transaction-types/payment.md +++ b/content/references/protocol-reference/transactions/transaction-types/payment.md @@ -9,7 +9,7 @@ labels: - Tokens --- # Payment -[[Source]](https://github.com/ripple/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/transactors/Payment.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/transactors/Payment.cpp "Source") A Payment transaction represents a transfer of value from one account to another. (Depending on the path taken, this can involve additional exchanges of value, which occur atomically.) This transaction type can be used for several [types of payments](#types-of-payments). diff --git a/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.ja.md b/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.ja.md index 5e65df086b..0c6344104a 100644 --- a/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # PaymentChannelClaim -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") _[PayChan Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.md b/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.md index 25a86ed534..733f0940fc 100644 --- a/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.md +++ b/content/references/protocol-reference/transactions/transaction-types/paymentchannelclaim.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # PaymentChannelClaim -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") _Added by the [PayChan amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.ja.md b/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.ja.md index abe2c7e1d8..c2a6abcc5f 100644 --- a/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.ja.md @@ -6,7 +6,7 @@ labels: - Payment Channel --- # PaymentChannelFund -[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") _[PayChan Amendment][]が必要です。_ diff --git a/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.md b/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.md index 23d64d8bae..2901b60f7b 100644 --- a/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.md +++ b/content/references/protocol-reference/transactions/transaction-types/paymentchannelfund.md @@ -6,7 +6,7 @@ labels: - Payment Channels --- # PaymentChannelFund -[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/PayChan.cpp "Source") _Added by the [PayChan amendment][]._ diff --git a/content/references/protocol-reference/transactions/transaction-types/setregularkey.ja.md b/content/references/protocol-reference/transactions/transaction-types/setregularkey.ja.md index 00ff537ba5..6676c550ad 100644 --- a/content/references/protocol-reference/transactions/transaction-types/setregularkey.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/setregularkey.ja.md @@ -7,7 +7,7 @@ labels: --- # SetRegularKey -[[ソース]](https://github.com/ripple/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") `SetRegularKey`トランザクションは、アカウントに関連付けられているレギュラーキーペアの割り当て、変更、削除を行います。 diff --git a/content/references/protocol-reference/transactions/transaction-types/setregularkey.md b/content/references/protocol-reference/transactions/transaction-types/setregularkey.md index bb5504c19f..788384a839 100644 --- a/content/references/protocol-reference/transactions/transaction-types/setregularkey.md +++ b/content/references/protocol-reference/transactions/transaction-types/setregularkey.md @@ -7,7 +7,7 @@ labels: --- # SetRegularKey -[[Source]](https://github.com/ripple/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") A `SetRegularKey` transaction assigns, changes, or removes the regular key pair associated with an account. diff --git a/content/references/protocol-reference/transactions/transaction-types/signerlistset.ja.md b/content/references/protocol-reference/transactions/transaction-types/signerlistset.ja.md index b1db25a8ea..ce7c4aac9b 100644 --- a/content/references/protocol-reference/transactions/transaction-types/signerlistset.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/signerlistset.ja.md @@ -6,7 +6,7 @@ labels: - セキュリティ --- # SignerListSet -[[ソース]](https://github.com/ripple/rippled/blob/ef511282709a6a0721b504c6b7703f9de3eecf38/src/ripple/app/tx/impl/SetSignerList.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/ef511282709a6a0721b504c6b7703f9de3eecf38/src/ripple/app/tx/impl/SetSignerList.cpp "Source") SignerListSetトランザクションは、トランザクションの[マルチシグ](multi-signing.html)に使用できる署名者のリストを作成、置換、削除します。このトランザクションタイプは[MultiSign Amendment][]により導入されました。[新規: rippled 0.31.0][] diff --git a/content/references/protocol-reference/transactions/transaction-types/ticketcreate.ja.md b/content/references/protocol-reference/transactions/transaction-types/ticketcreate.ja.md index a573175df6..3c0b62566e 100644 --- a/content/references/protocol-reference/transactions/transaction-types/ticketcreate.ja.md +++ b/content/references/protocol-reference/transactions/transaction-types/ticketcreate.ja.md @@ -7,7 +7,7 @@ labels: --- # TicketCreate -[[ソース]](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/CreateTicket.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/app/tx/impl/CreateTicket.cpp "Source") _([TicketBatch amendment][]が必要です)_ diff --git a/content/references/protocol-reference/transactions/transaction-types/ticketcreate.md b/content/references/protocol-reference/transactions/transaction-types/ticketcreate.md index 5a7d9d9cd5..b02b6b1966 100644 --- a/content/references/protocol-reference/transactions/transaction-types/ticketcreate.md +++ b/content/references/protocol-reference/transactions/transaction-types/ticketcreate.md @@ -7,7 +7,7 @@ labels: --- # TicketCreate -[[Source]](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/CreateTicket.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/app/tx/impl/CreateTicket.cpp "Source") _(Added by the [TicketBatch amendment][].)_ diff --git a/content/resources/contribute-code/contribute-code.md b/content/resources/contribute-code/contribute-code.md index 4740e40436..c91b8529de 100644 --- a/content/resources/contribute-code/contribute-code.md +++ b/content/resources/contribute-code/contribute-code.md @@ -16,7 +16,7 @@ The software that powers the XRP Ledger is open-source, so anyone can download, | XRP Ledger Source Code | | |:-----------------------|:----------------------------------------------------| | Repository | | -| License | [Multiple; ISC (permissive)](https://github.com/ripple/rippled/blob/develop/LICENSE.md) | +| License | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md) | | Programming Language | C++ | If you're not sure where to start, Dev Null Productions provides a detailed and thorough [**Source Code Guide**](https://xrpintel.com/source) that describes the structure and functions of the core XRP Ledger server (`rippled`) implementation. diff --git a/content/resources/known-amendments.ja.md b/content/resources/known-amendments.ja.md index cfca901618..34f673c623 100644 --- a/content/resources/known-amendments.ja.md +++ b/content/resources/known-amendments.ja.md @@ -1140,7 +1140,7 @@ XRP Ledgerプロトコルの署名要件を変更し、いかなる場合にも この修正により、単独署名のトランザクションは展性になりません。(署名者が必要以上の署名を提供した場合、[マルチシグのトランザクションはまだ展性であるかもしれません](transaction-malleability.html#マルチシグの展性))。すべてのトランザクションは、tfFullyCanonicalSigフラグに関係なく、署名の完全な正規の形式を使用する必要があります。完全に正規化された署名を作成しない署名ユーティリティはサポートされていません。Ripple社が提供するすべての署名ユーティリティは、少なくとも2014年以降、完全に正規化された署名のみを提供するようになっています。 -詳しくは、[`rippled` issue #3042](https://github.com/ripple/rippled/issues/3042)を参照してください。 +詳しくは、[`rippled` issue #3042](https://github.com/XRPLF/rippled/issues/3042)を参照してください。 ### SHAMapV2 diff --git a/content/resources/known-amendments.md b/content/resources/known-amendments.md index ff3908d1d0..905a706101 100644 --- a/content/resources/known-amendments.md +++ b/content/resources/known-amendments.md @@ -1140,7 +1140,7 @@ Without this amendment, a transaction is malleable if it uses a secp256k1 signat With this amendment, no single-signed transactions are malleable. ([Multi-signed transactions may still be malleable](transaction-malleability.html#malleability-with-multi-signatures) if signers provide more signatures than are necessary.) All transactions must use the fully canonical form of the signature, regardless of the `tfFullyCanonicalSig` flag. Signing utilities that do not create fully canonical signatures are not supported. All of Ripple's signing utilities have been providing fully-canonical signatures exclusively since at least 2014. -For more information, see [`rippled` issue #3042](https://github.com/ripple/rippled/issues/3042). +For more information, see [`rippled` issue #3042](https://github.com/XRPLF/rippled/issues/3042). ### SHAMapV2 diff --git a/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md b/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md index 8a4798311b..c94a801da5 100644 --- a/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md +++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md @@ -37,7 +37,7 @@ Rippleは、XRP Ledgerコミュニティ向けにいくつかの公開サーバ `rippled`サーバーの[管理メソッド](admin-api-methods.html)を使用するには、次のように行います。この場合、サーバーのバインド用として設定したIPアドレスとポートを使用する必要があります（例えば`127.0.0.1:54321`）。また、管理機能にアクセスするには、構成ファイルで管理用としてマークされているポートおよびIPアドレスから接続しなければなりません。 -[構成ファイルの例](https://github.com/ripple/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 +[構成ファイルの例](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 ## WebSocket API diff --git a/content/tutorials/get-started/get-started-using-http-websocket-apis.md b/content/tutorials/get-started/get-started-using-http-websocket-apis.md index deac778abd..1969511a93 100644 --- a/content/tutorials/get-started/get-started-using-http-websocket-apis.md +++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.md @@ -29,7 +29,7 @@ Both APIs can be served unencrypted (`http://` and `ws://`) or encrypted using T The API methods are divided into [Public Methods](public-api-methods.html) and [Admin Methods](admin-api-methods.html) so that organizations can offer public servers for the benefit of the community. To access admin methods, or admin functionality of public methods, you must connect to the API on a **port and IP address marked as admin** in the server's config file. -The [example config file](https://github.com/ripple/rippled/blob/f00f263852c472938bf8e993e26c7f96f435935c/cfg/rippled-example.cfg#L1154-L1179) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. +The [example config file](https://github.com/XRPLF/rippled/blob/f00f263852c472938bf8e993e26c7f96f435935c/cfg/rippled-example.cfg#L1154-L1179) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. ## WebSocket API @@ -110,6 +110,6 @@ For a full list of API methods, see: - [rippled API Reference](http-websocket-apis.html) -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/tutorials/get-started/get-started-using-java.md b/content/tutorials/get-started/get-started-using-java.md index e998789cdc..f32dc51f8f 100644 --- a/content/tutorials/get-started/get-started-using-java.md +++ b/content/tutorials/get-started/get-started-using-java.md @@ -102,7 +102,7 @@ The sample code in the previous section shows you how to connect to the Testnet, final HttpUrl rippledUrl = HttpUrl.get("http://localhost:5005/"); XrplClient xrplClient = new XrplClient(rippledUrl); - See the example [core server config file](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. * By using one of the available [public servers][]: @@ -174,10 +174,10 @@ You should see output similar to this example: Running the GetAccountInfo sample... Constructing an XrplClient connected to https://s.altnet.rippletest.net:51234/ Generated KeyPair: KeyPair{ - privateKey=PrivateKey{value=[redacted], destroyed=false}, - publicKey=PublicKey{value=UnsignedByteArray{unsignedBytes=List(size=33)}, - base58Value=aKGgrZL2WTc85HJSkQGuKfinem5oMH1uCJankSWFATGUhqvygxir, - base16Value=EDFB1073327CCBDA342AD685AF1C04530294866B9CB10C21126DC004BFDBA287D1, + privateKey=PrivateKey{value=[redacted], destroyed=false}, + publicKey=PublicKey{value=UnsignedByteArray{unsignedBytes=List(size=33)}, + base58Value=aKGgrZL2WTc85HJSkQGuKfinem5oMH1uCJankSWFATGUhqvygxir, + base16Value=EDFB1073327CCBDA342AD685AF1C04530294866B9CB10C21126DC004BFDBA287D1, keyType=ED25519 } } @@ -185,20 +185,20 @@ Classic Address: rBXHGshqXu3Smy9FUsQTmo49bGpQUQEm3X X-Address: T7yMiiJJCmgY2yg5WB2davUedDeBFAG5B8r9KHjKCxDdvv3 Funded the account using the Testnet faucet. AccountInfoResult{ - status=success, + status=success, accountData=AccountRootObject{ - ledgerEntryType=ACCOUNT_ROOT, - account=rDNwS2t4afhBogKqSFFmsDi1k7gmeGhz4p, - balance=10000000000, - flags=0, + ledgerEntryType=ACCOUNT_ROOT, + account=rDNwS2t4afhBogKqSFFmsDi1k7gmeGhz4p, + balance=10000000000, + flags=0, ownerCount=0, - previousTransactionId=0000000000000000000000000000000000000000000000000000000000000000, - previousTransactionLedgerSequence=0, - sequence=37649083, + previousTransactionId=0000000000000000000000000000000000000000000000000000000000000000, + previousTransactionLedgerSequence=0, + sequence=37649083, signerLists=[], index=F607809578C2A413774B9A240480B8B7B10C3E296CA609337D2F41813F566B92 - }, - ledgerCurrentIndex=37649083, + }, + ledgerCurrentIndex=37649083, validated=false } ``` diff --git a/content/tutorials/get-started/get-started-using-javascript.ja.md b/content/tutorials/get-started/get-started-using-javascript.ja.md index 013b5e15e4..4796b831d4 100644 --- a/content/tutorials/get-started/get-started-using-javascript.ja.md +++ b/content/tutorials/get-started/get-started-using-javascript.ja.md @@ -101,7 +101,7 @@ const xrpl = require("xrpl") const client = new xrpl.Client(MY_SERVER) await client.connect() - デフォルト値の詳細については、[コアサーバー設定ファイル](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562)の例を参照してください。 + デフォルト値の詳細については、[コアサーバー設定ファイル](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562)の例を参照してください。 * 利用可能な[公開サーバー][]を利用する: diff --git a/content/tutorials/get-started/get-started-using-javascript.md b/content/tutorials/get-started/get-started-using-javascript.md index 678c9a0b38..d6de86099a 100644 --- a/content/tutorials/get-started/get-started-using-javascript.md +++ b/content/tutorials/get-started/get-started-using-javascript.md @@ -101,7 +101,7 @@ The sample code in the previous section shows you how to connect to the Testnet, const client = new xrpl.Client(MY_SERVER) await client.connect() - See the example [core server config file](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. * By using one of the available [public servers][]: diff --git a/content/tutorials/get-started/get-started-using-python.md b/content/tutorials/get-started/get-started-using-python.md index 5f579c4fe1..c9f35b4427 100644 --- a/content/tutorials/get-started/get-started-using-python.md +++ b/content/tutorials/get-started/get-started-using-python.md @@ -67,7 +67,7 @@ The sample code in the previous section shows you how to connect to the Testnet, JSON_RPC_URL = "http://localhost:5005/" client = JsonRpcClient(JSON_RPC_URL) - See the example [core server config file](https://github.com/ripple/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. * By using one of the available [public servers][]: @@ -101,7 +101,7 @@ classic_address: raaFKKmgf6CRZttTVABeTcsqzRQ51bNR6Q #### Using the account -In this tutorial we only query details about the generated account from the XRP Ledger, but you can use the values in the `Wallet` instance to prepare, sign, and submit transactions with `xrpl-py`. +In this tutorial we only query details about the generated account from the XRP Ledger, but you can use the values in the `Wallet` instance to prepare, sign, and submit transactions with `xrpl-py`. ##### Prepare @@ -129,7 +129,7 @@ The X-address format [packs the address and destination tag](https://github.com/ ### {{n.next()}}. Query the XRP Ledger -You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exchange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). +You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exchange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). Here, we use `xrpl-py`'s [`xrpl.account`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.account.html) module to look up information about the [account we got](#2-get-account) in the previous step. diff --git a/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.ja.md b/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.ja.md index 792440bea0..538e000480 100644 --- a/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.ja.md +++ b/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.ja.md @@ -13,7 +13,7 @@ _[Checks Amendment][]が必要です。_ ## 1. 特定のアドレスのすべてのCheckの検索 - + 特定のアドレスで受信および送信されるすべてのCheckのリストを取得するには、送金元アカウントのアドレスを指定した`account_objects`コマンドを実行し、要求の`type` フィールドを`checks`に設定します。 diff --git a/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md b/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md index 5dbd71aff7..887385769c 100644 --- a/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md +++ b/content/tutorials/use-specialized-payment-types/use-checks/look-up-checks-by-sender.md @@ -11,7 +11,7 @@ This tutorial shows how to look up [Checks](checks.html) by their sender. You ma ## 1. Look up all Checks for the address - + To get a list of all incoming and outgoing Checks for an account, use the `account_objects` command with the sending account's address and set the `type` field of the request to `checks`. diff --git a/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md b/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md index 4a3b0106e7..1e791e9b91 100644 --- a/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md +++ b/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md @@ -344,7 +344,7 @@ JSON-RPC APIで`channel_verify`を使用する例: - `account_channels`要求に正しいレジャーバージョンが指定されていなかった。（最新の検証済みバージョンを確認するには、`"ledger_index":"validated”`を使用します） - 受取人は以前にXRPを清算したものの、記録し忘れていた。 - 受取人がXRPの清算を試行し、暫定的な結果を記録したが、トランザクションの最終的な検証済みの結果がこれとは異なり、受取人はこの最終検証済み結果を記録し忘れていた。 - - 受取人が照会した`rippled`サーバーが、ネットワークの他の部分と同期していない状態であったか、または不明なバグが発生した。サーバーの状態を確認するには、[server_infoメソッド][]を使用します。（この状況を再現できる場合は、[問題を報告してください](https://github.com/ripple/rippled/issues/)。） + - 受取人が照会した`rippled`サーバーが、ネットワークの他の部分と同期していない状態であったか、または不明なバグが発生した。サーバーの状態を確認するには、[server_infoメソッド][]を使用します。（この状況を再現できる場合は、[問題を報告してください](https://github.com/XRPLF/rippled/issues/)。） 受取人がPayment Channelの署名と現行状態の両方を確認した後で、XRPをまだ受領していない場合、XRPを清算するトランザクションがChannelの有効期限より前に処理される限り、XRPを確実に清算 _できます_ 。 @@ -610,6 +610,6 @@ Channelは期限切れ状態で永久にレジャーに残ることがありま -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/tutorials/use-specialized-payment-types/use-payment-channels.md b/content/tutorials/use-specialized-payment-types/use-payment-channels.md index 35b9068bd0..9d41841655 100644 --- a/content/tutorials/use-specialized-payment-types/use-payment-channels.md +++ b/content/tutorials/use-specialized-payment-types/use-payment-channels.md @@ -368,7 +368,7 @@ The payee should check the following: - The `account_channels` request did not specify the correct ledger version. (Use `"ledger_index": "validated"` to get the latest validated ledger version) - The payee previously redeemed XRP but forgot to record it. - The payee attempted to redeem XRP and recorded the tentative result, but the transaction's final validated result was not the same and the payee neglected to record the final validated result. - - The `rippled` server the payee queried has lost sync with the rest of the network or is experiencing an unknown bug. Use the [server_info method][] to check the state of the server. (If you can reproduce this situation, please [report an issue](https://github.com/ripple/rippled/issues/).) + - The `rippled` server the payee queried has lost sync with the rest of the network or is experiencing an unknown bug. Use the [server_info method][] to check the state of the server. (If you can reproduce this situation, please [report an issue](https://github.com/XRPLF/rippled/issues/).) After confirming both the signature and the current state of the payment channel, the payee has not yet received the XRP, but is certain that he or she _can_ redeem the XRP as long as the transaction to do so is processed before the channel expires. @@ -665,6 +665,6 @@ This concludes the tutorial of Payment Channel usage. Ripple encourages users to -{% include '_snippets/rippled-api-links.md' %} -{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %} diff --git a/content/use-cases/tokenization/authorized-minter.md b/content/use-cases/tokenization/authorized-minter.md index b6855bbd29..a7e64e38dd 100644 --- a/content/use-cases/tokenization/authorized-minter.md +++ b/content/use-cases/tokenization/authorized-minter.md @@ -25,10 +25,14 @@ Rather than designing NFTs yourself, you coordinate with an NFT creator to becom Once you finish creating NFTs, the creator can revoke your privileges and reassert control over the NFTs. You might also transfer the tokens to a marketplace that will handle sales of the NFTs. You can act as a broker to match sell offers to buy offers. See [Running an NFT auction](nftoken-auctions.html). +![Auctioning NFTs](img/uc-nft-transferring-nfts.png) + To mint your first NFTs on behalf of another account, see [Authorizing Another Account to Mint Your NFTs](assign-an-authorized-minter-using-javascript.html). If you, as the owner or issuer, want to be able to burn the token in the future, set the `Flags` field to _1._ To make the NFT transferable, set the `Flags` field to _8_. Set the `Flags` field to _9_ to make the NFT both burnable and transferable. See[ Burnable flag](nftoken.html#nftoken-flags) and [Transferable flag](nftoken.html#nftoken-flags). +![Burning NFTs](img/uc-nft-burn.png) + You can arrange for the creator to receive royalties from future sales by setting a transfer fee. This is a value from 0-50000 representing 0-50% of the sale price. See [Transfer Fee](nftoken.html#transferfee). The NFToken URL is a link to the location where the content of the NFT is stored. One option is create an IPFS account and store the NFToken content at a persistent URL. See [Best Practices for Storing NFT Data](https://docs.ipfs.io/how-to/best-practices-for-nft-data). @@ -52,6 +56,8 @@ You can act as a broker, connecting sellers with bidders, completing the transfe There are several XRP reserve requirements when you mint NFTs for sale. Each NFToken page requires a reserve of 2 XRP. A NFToken page can store 16-32 NFTs. +![Reserves](img/uc-nft-reserves.png) + Each `NFTokenOffer` object requires a reserve of 2 XRP. When you post the `NFTokenOffer` or sell the NFT, there are trivial transfer fees (roughly 6000 drops, or .006 XRP). When you are selling at a high volume, the trivial amounts can add up quickly, and need to be considered as part of your cost of doing business. @@ -66,12 +72,16 @@ See: The most straightforward payment for XRPL NFTs is XRP. For examples of selling and buying NFTs using XRP, see [Transfer NFTokens](transfer-nfts-using-javascript.html). +![Checkout](img/uc-nft-checkout.png) + For trade in other currencies, you can leverage the DEX to accept and convert issued currencies of all kinds. See [Trade in the Decentralized Exchange](trade-in-the-decentralized-exchange.html#trade-in-the-decentralized-exchange). ## Indexing NFTs When listing NFTs for sale, it can be useful to use object metadata to organize them. You can use queries in the XRPL libraries, the Clio server, and extensions in the XRPL API and Bithomp libraries to sort and filter NFTs by creator, price, collection, rarity, and more. +![Indexing NFTs](img/uc-nft-indexing.png) + See: - [Clio setup](install-clio-on-ubuntu.html) diff --git a/content/use-cases/tokenization/digital-artist.md b/content/use-cases/tokenization/digital-artist.md index cc6ccf6369..801d7c96ae 100644 --- a/content/use-cases/tokenization/digital-artist.md +++ b/content/use-cases/tokenization/digital-artist.md @@ -42,6 +42,8 @@ See [Mint and Burn NFTokens](mint-and-burn-nfts-using-javascript.html). You transfer NFTs by creating a sell offer. See [Transfer NFTokens](transfer-nfts-using-javascript.html). +![Transferring NFTs](img/uc-nft-transferring-nfts.png) + You can sell your NFTs in an auction format. See [Running an NFT Auction](nftoken-auctions.html). ### Reserve requirements @@ -50,6 +52,8 @@ There are several XRP reserve requirements when you mint NFTs for sale. Each NFT Each `NFTokenOffer` object requires a reserve of 2 XRP. +![Reserves](img/uc-nft-reserves.png) + When you post the `NFTokenOffer` or sell the NFT, there are trivial transfer fees (roughly 6000 drops, or .006 XRP). When you are selling at a high volume, the trivial amounts can add up quickly, and need to be considered as part of your cost of doing business. See: @@ -62,6 +66,8 @@ See: The most straightforward payment for XRPL NFTs is XRP. For examples of selling and buying NFTs using XRP, see [Transfer NFTokens](transfer-nfts-using-javascript.html). +![Checkout](img/uc-nft-checkout.png) + For trade in other currencies, you can leverage the DEX to accept and convert issued currencies of all kinds. See [Trade in the Decentralized Exchange](trade-in-the-decentralized-exchange.html#trade-in-the-decentralized-exchange). @@ -69,6 +75,8 @@ For trade in other currencies, you can leverage the DEX to accept and convert is When listing NFTs for sale, it can be useful to use object metadata to organize them. You can use queries in the XRPL libraries, the Clio server, and extensions in the XRPL API and Bithomp libraries to sort and filter NFTs by creator, price, collection, rarity, and more. +![Indexing NFTs](img/uc-nft-indexing.png) + See: - [Clio setup](install-clio-on-ubuntu.html) @@ -80,4 +88,6 @@ See: There are some workflows where it makes sense for the issuer to retain the right to burn the token at some point in the future, regardless of the current owner. For example, NFTs used for carbon credits can be minted and traded, but once the carbon is captured, the NFT can be burned so that it is no longer transferable. For these scenarios, set the `lsfBurnable` flag when you mint the NFT. +![Burning NFTs](img/uc-nft-burn.png) + Another example might be burning an in-game asset that is lost by a player after losing a life in the game. You might also burn an NFT ticket after successful redemption to prevent it from being used again. \ No newline at end of file diff --git a/content/use-cases/tokenization/nft-mkt-overview.md b/content/use-cases/tokenization/nft-mkt-overview.md index f0b356e31c..5e6cf94811 100644 --- a/content/use-cases/tokenization/nft-mkt-overview.md +++ b/content/use-cases/tokenization/nft-mkt-overview.md @@ -57,6 +57,8 @@ The NFToken URL is a link to the location where the content of the NFT is stored If you, as the issuer, want to be able to burn the token in the future, set the `Flags` field to _1._ To make the NFT transferable, set the `Flags` field to _8_. Set the `Flags` field to _9_ to make the NFT both burnable and transferable. See [Burnable flag](nftoken.html) and [Transferable flag](nftoken.html). +![Burning a token](img/uc-nft-burn.png) + You can collect royalties from future sales by setting a transfer fee. This is a value from 0-50000 representing 0-50% of the sale price. See [Transfer Fee](nftoken.html#transferfee). You can mint NFTs in logical collections using the `TokenTaxon` field. See [Minting NFTs into Collections](nft-collections.html). @@ -82,6 +84,8 @@ When you set up your account, keep in mind that there is a base reserve requirem You transfer NFTs by creating a sell offer or accepting a buy offer. See [Transfer NFTokens](transfer-nfts-using-javascript.html). +![Transferring NFTs](img/uc-nft-transferring-nfts.png) + You can sell your NFTs in an auction format. See [Running an NFT Auction](nftoken-auctions.html). You can act as a broker, connecting sellers with bidders, completing the transfer and keeping a percentage of the purchase price. See [Broker a NFToken sale](broker-an-nft-sale-using-javascript.html). @@ -92,6 +96,8 @@ There are several XRP reserve requirements when you mint NFTs for sale. Each NFT Each `NFTokenOffer` object requires a reserve of 2 XRP. +![Reserves](img/uc-nft-reserves.png) + When you post the `NFTokenOffer` or sell the NFT, there are trivial transfer fees (roughly 6000 drops, or .006 XRP). When you are selling at a high volume, the trivial amounts can add up quickly, and need to be considered as part of your cost of doing business. See: @@ -104,6 +110,8 @@ See: The most straightforward payment for XRPL NFTs is XRP. For examples of selling and buying NFTs using XRP, see [Transfer NFTokens](transfer-nfts-using-javascript.html). +![Checkout](img/uc-nft-checkout.png) + For trade in other currencies, you can leverage the DEX to accept and convert issued currencies of all kinds. See [Trade in the Decentralized Exchange](trade-in-the-decentralized-exchange.html#trade-in-the-decentralized-exchange).