mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 15:15:50 +00:00
Migrate content syntax via script
The changes in this commit were auto-generated by running tool/migrate.sh Following this commit, the Dactyl build no longer works but the Redocly build (mostly) should.
This commit is contained in:
mDuo13
@@ -1,9 +0,0 @@
|
||||
Checkを換金するための前提条件は、正確な金額を換金する場合も変動金額を換金する場合も同じです。
|
||||
|
||||
- 現在レジャーに記録されているCheckオブジェクトのIDが必要です。
|
||||
- 例えば、以下の例では、あるCheckのIDとして`838766BA2B995C00744175F69A1B11E32C3DBC40E64801A4056FCBD657F57334`を使用していますが、各ステップをご自分で行う際には、異なるIDを使用する必要があります。
|
||||
- Checkに記載されている受取人の**アドレス**と**秘密鍵**。このアドレスは、Checkオブジェクトの`Destination`アドレスと一致している必要があります。
|
||||
- 発行済み通貨用のCheckの場合は、ご自身（受取人）にイシュアーに対するトラストラインがある必要があります。このトラストライン上のご自身の限度額は、受け取る金額を追加するための残高より十分高くなければなりません。
|
||||
- トラストラインと限度額について詳しくは、[トークン](tokens.html)および[トラストラインと発行](trust-lines-and-issuing.html)を参照してください。
|
||||
- [トランザクションに安全に署名できる手段](secure-signing.html)。
|
||||
- XRP Ledgerに接続できる[クライアントライブラリ](client-libraries.html)か、それとも[HTTPライブラリ、WebSocketライブラリなど](get-started-using-http-websocket-apis.html)。
|
||||
@@ -3,6 +3,6 @@ The prerequisites for cashing a check are the same whether you are cashing it fo
|
||||
- You need the ID of a Check object currently in the ledger.
|
||||
- For example, the ID of one Check in these examples is `838766BA2B995C00744175F69A1B11E32C3DBC40E64801A4056FCBD657F57334`, although you must use a different ID to go through these steps yourself.
|
||||
- The **address** and **secret key** of the Check's stated recipient. The address must match the `Destination` address in the Check object.
|
||||
- If the Check is for a [token](tokens.html), you (the recipient) must have a [trust line](trust-lines-and-issuing.html) to the issuer. Your limit on that trust line must be high enough to hold your previous balance plus the amount you would receive.
|
||||
- A [secure way to sign transactions](secure-signing.html).
|
||||
- A [client library](client-libraries.html) that can connect to the XRP Ledger, or [any HTTP or WebSocket client](get-started-using-http-websocket-apis.html).
|
||||
- If the Check is for a [token](../concepts/tokens/index.md), you (the recipient) must have a [trust line](../concepts/tokens/fungible-tokens/index.md) to the issuer. Your limit on that trust line must be high enough to hold your previous balance plus the amount you would receive.
|
||||
- A [secure way to sign transactions](../concepts/transactions/secure-signing.md).
|
||||
- A [client library](../references/client-libraries.md) that can connect to the XRP Ledger, or [any HTTP or WebSocket client](../tutorials/get-started/get-started-using-http-websocket-apis.md).
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
_[Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-39d-clawback)が必要です。_
|
||||
1070
content/_snippets/common-links.md
Normal file
1070
content/_snippets/common-links.md
Normal file
File diff suppressed because it is too large
Load Diff
@@ -1 +0,0 @@
|
||||
[推奨インストール](install-rippled.html)では、デフォルトで`/etc/opt/ripple/rippled.cfg`という設定ファイルを使用します。その他の場所としては、`$HOME/.config/ripple/rippled.cfg`(`$HOME`は`rippled`を実行しているユーザーのホームディレクトリです)、`$HOME/.local/ripple/rippled.cfg`または`rippled`を起動した現在の作業ディレクトリがあります。
|
||||
@@ -1 +1 @@
|
||||
The [recommended installation](install-rippled.html) uses the config file `/etc/opt/ripple/rippled.cfg` by default. Other places you can put a config file include `$HOME/.config/ripple/rippled.cfg` (where `$HOME` is the home directory of the user running `rippled`), `$HOME/.local/ripple/rippled.cfg`, or the current working directory from where you start `rippled`.
|
||||
The [recommended installation](../infrastructure/installation/index.md) uses the config file `/etc/opt/ripple/rippled.cfg` by default. Other places you can put a config file include `$HOME/.config/ripple/rippled.cfg` (where `$HOME` is the home directory of the user running `rippled`), `$HOME/.local/ripple/rippled.cfg`, or the current working directory from where you start `rippled`.
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
シーケンス番号とは、32ビットの符号なし整数であり、指定された送金元からのトランザクションが正しい順序で1回だけ実行されるようにするために使用されます。
|
||||
|
||||
すべての[XRP Ledgerアカウント](accounts.html)には、`Sequence`フィールドに1つのシーケンス番号があり、アカウントがトランザクションを送信し、そのトランザクションが[検証済みレジャー](ledgers.html)に記録されるたびに、1ずつ増加します。シーケンス番号は各[トランザクション](transactions.html)の`Sequence`フィールドにもあり、そのトランザクションが実行される際にアカウントの現在のシーケンス番号と一致している必要があります。各アカウントで、各シーケンス番号は番号順に一度だけ使用できます。
|
||||
|
||||
[DeletableAccounts Amendment](known-amendments.html#deletableaccounts) を適用する場合、アカウントの`Sequence`番号の始まりが、アカウントが作成されたレジャーバージョンの[レジャーインデックス][]と一致します。DeletableAccountsを適用しない場合、どのアカウントの`Sequence`番号も1で始まります。
|
||||
|
||||
トランザクションがレジャーに記録されると、トランザクションの実行が成功したか[`tec`クラスのエラーコード](tec-codes.html)で失敗したかを問わず、シーケンス番号が1つ消費されます。トランザクションのその他の失敗についてはレジャーに記録されないため、送金元のシーケンス番号は変更されません（その他の影響もありません）。
|
||||
|
||||
レジャー内では、[アドレス][]とシーケンス番号を一緒に使用して、その送金元とシーケンス番号を持つ検証済みトランザクションによって作成されたオブジェクトが識別されることがあります。この方法で識別されたオブジェクトの例として、[Escrow](escrow.html)と[オファー](offers.html)が挙げられます。
|
||||
|
||||
複数の未確定のトランザクションが、同じ送金元と同じシーケンス番号を持つことが可能です。そのようなトランザクションは互いに排他的であり、検証済みレジャーに記録されるのはいずれか一方のみです。（それ以外は最終的に影響ありません。）
|
||||
@@ -1,13 +1,13 @@
|
||||
A sequence number is a 32-bit unsigned integer that is used to make sure transactions from a given sender execute only once each, and in the correct order.
|
||||
|
||||
Every [account in the XRP Ledger](accounts.html) has a sequence number in its `Sequence` field, which increases by 1 whenever that account sends a transaction and that transaction gets included in a [validated ledger](ledgers.html). Each [transaction](transactions.html) also has a sequence number in its `Sequence` field, which must match the account's current sequence number when the transaction executes. For each account, each sequence number can only be used once, in numerical order.
|
||||
Every [account in the XRP Ledger](../../concepts/accounts/accounts.md) has a sequence number in its `Sequence` field, which increases by 1 whenever that account sends a transaction and that transaction gets included in a [validated ledger](../../concepts/ledgers/index.md). Each [transaction](../../concepts/transactions/index.md) also has a sequence number in its `Sequence` field, which must match the account's current sequence number when the transaction executes. For each account, each sequence number can only be used once, in numerical order.
|
||||
|
||||
[Tickets](tickets.html) make some exceptions from these rules so that it is possible to send transactions out of the normal order. Tickets represent sequence numbers reserved for later use; a transaction can use a Ticket instead of a normal sequence number.
|
||||
[Tickets](../../concepts/accounts/tickets.md) make some exceptions from these rules so that it is possible to send transactions out of the normal order. Tickets represent sequence numbers reserved for later use; a transaction can use a Ticket instead of a normal sequence number.
|
||||
|
||||
With the [DeletableAccounts amendment](known-amendments.html#deletableaccounts), the starting `Sequence` number for an account matches the [Ledger Index][] of the ledger version where the account was created. Before DeletableAccounts, every account started with `Sequence` number 1.
|
||||
With the [DeletableAccounts amendment](../../resources/known-amendments.md#deletableaccounts), the starting `Sequence` number for an account matches the [Ledger Index][] of the ledger version where the account was created. Before DeletableAccounts, every account started with `Sequence` number 1.
|
||||
|
||||
Whenever a transaction is included in a ledger, it uses up a sequence number (or Ticket) regardless of whether the transaction executed successfully or failed with a [`tec`-class error code](tec-codes.html). Other transaction failures don't get included in ledgers, so they don't change the sender's sequence number (or have any other effects).
|
||||
Whenever a transaction is included in a ledger, it uses up a sequence number (or Ticket) regardless of whether the transaction executed successfully or failed with a [`tec`-class error code](../../references/protocol/transactions/transaction-results/tec-codes.md). Other transaction failures don't get included in ledgers, so they don't change the sender's sequence number (or have any other effects).
|
||||
|
||||
Within the ledger, an [Address][] and a sequence number are sometimes used together to identify an object that was created by the validated transaction with that sender and sequence number. [Escrows](escrow.html) and [Offers](offers.html) are examples of objects identified this way.
|
||||
Within the ledger, an [Address][] and a sequence number are sometimes used together to identify an object that was created by the validated transaction with that sender and sequence number. [Escrows](../../concepts/payment-types/escrow.md) and [Offers](../../concepts/tokens/decentralized-exchange/offers.md) are examples of objects identified this way.
|
||||
|
||||
It is possible for multiple unconfirmed transactions to have the same sender and sequence number. Such transactions are mutually exclusive, and at most one of them can be included in a validated ledger. (Any others ultimately have no effect.)
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
XRP Ledgerのアカウントは、XRP Ledgerの[base58][]フォーマットのアドレスで識別されます。このアドレスはアカウントのマスター[公開鍵](https://en.wikipedia.org/wiki/Public-key_cryptography)から生成され、マスター公開鍵は秘密鍵から生成されます。アドレスはJSON文字列で記述され、以下の特徴があります。
|
||||
|
||||
* 長さは25から35文字
|
||||
* 文字`r`から始まる
|
||||
* 数字"`0`"、大文字"`O`"、大文字"`I`"、小文字"`l`"を除く英数字
|
||||
* 大文字と小文字を区別
|
||||
* 4バイトのチェックサムが含まれており、ランダムな文字から有効なアドレスが生成される確率はおよそ2<sup>32</sup>分の1
|
||||
|
||||
> **注記:** [宛先タグ](source-and-destination-tags.html)をアドレスに「組み込む」**X**アドレス形式もあります。これらのアドレスは`X`（メインネット用）または`T`（[テストネットワーク](parallel-networks.html)用）で始まります。取引所とウォレットは、顧客が知る必要のあるすべてのデータを1つの値で表すためにXアドレスを使用できます。詳細については、[Xアドレスフォーマットサイト](https://xrpaddress.info/)と[コーデック](https://github.com/xrp-community/xrpl-tagged-address-codec)をご覧ください
|
||||
>
|
||||
> XRP Ledgerプロトコルは「クラシック」アドレスのみをネイティブにサポートしていますが、多くの[クライアントライブラリ](client-libraries.html)はXアドレスもサポートしています。
|
||||
|
||||
@@ -6,6 +6,8 @@ Accounts in the XRP Ledger are identified by an address in the XRP Ledger's [bas
|
||||
* Case-sensitive
|
||||
* Includes a 4-byte checksum so that the probability of generating a valid address from random characters is approximately 1 in 2<sup>32</sup>
|
||||
|
||||
> **Note:** There is also an **X**-address format that "packs" a [destination tag](source-and-destination-tags.html) into the address. These addresses start with an `X` (for Mainnet) or a `T` (for [test networks](parallel-networks.html)). Exchanges and wallets can use X-addresses to represent all the data a customer needs to know in one value. For more information, see the [X-address format site](https://xrpaddress.info/) and [codec](https://github.com/xrp-community/xrpl-tagged-address-codec).
|
||||
>
|
||||
> The XRP Ledger protocol only supports "classic" addresses natively, but many [client libraries](client-libraries.html) support X-addresses too.
|
||||
{% admonition type="info" name="Note" %}
|
||||
There is also an **X**-address format that "packs" a [destination tag](../../concepts/transactions/source-and-destination-tags.md) into the address. These addresses start with an `X` (for Mainnet) or a `T` (for [test networks](../../concepts/networks-and-servers/parallel-networks.md)). Exchanges and wallets can use X-addresses to represent all the data a customer needs to know in one value. For more information, see the [X-address format site](https://xrpaddress.info/) and [codec](https://github.com/xrp-community/xrpl-tagged-address-codec).
|
||||
|
||||
The XRP Ledger protocol only supports "classic" addresses natively, but many [client libraries](../../references/client-libraries.md) support X-addresses too.
|
||||
{% /admonition %}
|
||||
|
||||
@@ -1,6 +0,0 @@
|
||||
[HTTP / WebSocket API](http-websocket-apis.html)は、2種類の通貨コードをサポートしています。
|
||||
|
||||
- **[標準通貨コード](currency-formats.html#標準通貨コード):** `"EUR"`や "USD"`のような3文字の文字列
|
||||
- **[非標準通貨コード](currency-formats.html#非標準通貨コード):** `"0158415500000000C1F76FFF6ECB0BAC600000000"`のような160ビットの16進数の文字列。これは一般的ではありません。
|
||||
|
||||
同じコードを持つトークンは、接続されたトラストラインを越えて[rippling(波及)](rippling.html)することができます。通貨コードには、XRP Ledgerに組み込まれた他の動作はありません。
|
||||
@@ -1,6 +1,6 @@
|
||||
The [HTTP / WebSocket APIs](http-websocket-apis.html) support two formats of currency code:
|
||||
The [HTTP / WebSocket APIs](../../references/http-websocket-apis/index.md) support two formats of currency code:
|
||||
|
||||
- **[Standard Currency Codes](currency-formats.html#standard-currency-codes):** As a 3-character string such as `"EUR"` or `"USD"`.
|
||||
- **[Nonstandard Currency Codes](currency-formats.html#nonstandard-currency-codes):** As a 160-bit hexadecimal string, such as `"0158415500000000C1F76FF6ECB0BAC600000000"`. This is uncommon.
|
||||
- **[Standard Currency Codes](../../references/protocol/data-types/currency-formats.md#standard-currency-codes):** As a 3-character string such as `"EUR"` or `"USD"`.
|
||||
- **[Nonstandard Currency Codes](../../references/protocol/data-types/currency-formats.md#nonstandard-currency-codes):** As a 160-bit hexadecimal string, such as `"0158415500000000C1F76FF6ECB0BAC600000000"`. This is uncommon.
|
||||
|
||||
Tokens with the same code can [ripple](rippling.html) across connected trust lines. Currency codes have no other behavior built into the XRP Ledger.
|
||||
Tokens with the same code can [ripple](../../concepts/tokens/fungible-tokens/rippling.md) across connected trust lines. Currency codes have no other behavior built into the XRP Ledger.
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
XRP Ledger内の多くのオブジェクト、特にトランザクションとレジャーは、256ビットのハッシュ値で一意に識別されます。通常、この値は「SHA-512ハーフ」として算出されます。SHA-512ハーフは、あるコンテンツから[SHA-512](http://dx.doi.org/10.6028/NIST.FIPS.180-4)ハッシュを計算し、出力の前半を取得したものです。（これは256ビット、つまり32バイトで、16進数表記では64文字です。）オブジェクトのハッシュは、極めて競合の発生しにくい方法でコンテンツから生成されるため、2つのオブジェクトが同じハッシュを持つ場合、それらのオブジェクトは同じものと見なされます。
|
||||
|
||||
XRP Ledgerのハッシュ値には、以下の特徴があります。
|
||||
|
||||
* 長さは64文字ちょうどです
|
||||
* [16進数](https://en.wikipedia.org/wiki/Hexadecimal)の文字セット: 0-9およびA-Fです。
|
||||
* 通常は大文字で記述されます。
|
||||
|
||||
**注記:** SHA-512ハーフは、公式に定義されている _SHA-512/256_ ハッシュ関数とほぼ同等のセキュリティーを持ちます。しかし、XRP LedgerはSHA-512/256より前から利用されているため、既存のSHA-512関数上に実装することも容易にできます。（この記事の時点で、暗号ライブラリーでのSHA-512のサポートはSHA-512/256よりはるかに一般的です。）
|
||||
@@ -1,7 +0,0 @@
|
||||
レジャーインデックスは、32ビットの符号なし整数であり、レジャーを識別するために使用します。レジャーインデックスは、レジャーの _シーケンス番号_ と呼ばれることもあります。（[アカウントシーケンス](basic-data-types.html#アカウントシーケンス)とは異なります。）一番最初のレジャーでは、レジャーインデックスは1でした。新しいレジャーのレジャーインデックスは、その直前のレジャーのレジャーインデックスに1を加算した値になります。
|
||||
|
||||
レジャーインデックスがレジャーの順番を示すのに対し、[ハッシュ][]値はレジャーの正確なコンテンツを示します。2つのレジャーが同じハッシュ値を持つ場合、それらは必ず同じものです。検証済みレジャーでは、ハッシュ値とレジャーインデックスは等しく有効で、1:1の関係です。しかし、進行中のレジャーに対しては、以下の理由によりその限りでありません。
|
||||
|
||||
* ネットワーク全体でのトランザクションの伝搬遅延が原因で、2つの異なる`rippled`サーバーで、同じレジャーインデックスを持つ現行レジャーに対するコンテンツが異なる場合があります。
|
||||
* 決済済みレジャーバージョンが複数あり、コンセンサスによる検証が競合している場合があります。このようなレジャーバージョンでは、レジャーインデックスは同じですが、コンテンツは異なります（ハッシュも異なります）。これらの決済済みレジャーのうち、検証済みになるのは1つだけです。
|
||||
* 現行のオープンレジャーのハッシュは計算されません。これは、現行レジャーのレジャーインデックスは同じままであっても、コンテンツは時間とともに変化し、ハッシュが変わる可能性があるためです。レジャーのハッシュは、レジャーが閉鎖されるときにのみ計算されます。
|
||||
@@ -1,4 +1,4 @@
|
||||
A ledger index is a 32-bit unsigned integer used to identify a ledger. The ledger index is sometimes known as the ledger's _sequence number_. (This is different from an [account sequence](basic-data-types.html#account-sequence).) The very first ledger was ledger index 1, and each new ledger has a ledger index that is 1 higher than the ledger index of the ledger immediately before it.
|
||||
A ledger index is a 32-bit unsigned integer used to identify a ledger. The ledger index is sometimes known as the ledger's _sequence number_. (This is different from an [account sequence](../../references/protocol/data-types/basic-data-types.md#account-sequence).) The very first ledger was ledger index 1, and each new ledger has a ledger index that is 1 higher than the ledger index of the ledger immediately before it.
|
||||
|
||||
The ledger index indicates the order of the ledgers; the [Hash][] value identifies the exact contents of the ledger. Two ledgers with the same hash are always the same. For validated ledgers, hash values and ledger indexes are equally valid and correlate 1:1. However, this is not true for in-progress ledgers:
|
||||
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
XRP Ledgerは、以下のようなさまざまな状況で暗号署名を検証するために、公開鍵を使用します。
|
||||
|
||||
* トランザクションを承認するため。トランザクションに公開鍵が添付されます。公開鍵は、送信元のXRP Ledgerのアドレスか送信者のレギュラーキーアドレスに数学的に関連付けられている必要があります。
|
||||
* `rippled`サーバー間のピアツーピア通信の安全を確保するため。これには、データベースが空の状態でサーバーが起動する場合に、サーバーがランダムに生成する「ノード公開鍵」が使用されます。
|
||||
* コンセンサスプロセスの一環として検証投票に署名するため。これには、サーバーの運用者が[設定ファイルに定義](run-rippled-as-a-validator.html)した「バリデータ公開鍵」が使用されます。
|
||||
|
||||
バリデータ公開鍵とノード公開鍵は、まったく同じフォーマットを使用します。
|
||||
|
||||
公開鍵は、16進数かbase-58で表すことができます。16進数では、公開鍵は3種類すべて、長さが33バイト（66文字）です。
|
||||
|
||||
base-58フォーマットでは、バリデータ公開鍵とノード公開鍵は必ず文字`n`から始まり、その後に文字`9`が続くのが一般的です。base-58フォーマットのバリデータ公開鍵は、最長で53文字にできます。ノード公開鍵の例を以下に示します。`n9Mxf6qD4J55XeLSCEpqaePW4GjoCR5U1ZeGZGJUCNe3bQa4yQbG`。
|
||||
|
||||
XRP Ledgerのアドレスは、公開鍵に数学的に関連付けられます。この公開鍵がbase-58でエンコードされることはめったにありませんが、その場合は文字`a`から始まります。
|
||||
@@ -2,7 +2,7 @@ The XRP Ledger uses public keys to verify cryptographic signatures in several pl
|
||||
|
||||
* To authorize transactions, a public key is attached to the transaction. The public key must be mathematically associated with the sending XRP Ledger address or the sender's regular key address.
|
||||
* To secure peer-to-peer communications between `rippled` servers. This uses a "node public key" that the server generates randomly when it starts with an empty database.
|
||||
* To sign validation votes as part of the consensus process. This uses a "validator public key" that the server operator [defines in the config file](run-rippled-as-a-validator.html).
|
||||
* To sign validation votes as part of the consensus process. This uses a "validator public key" that the server operator [defines in the config file](../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md).
|
||||
|
||||
Validator public keys and node public keys use the exact same format.
|
||||
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
### ETLソースオブジェクト
|
||||
<!-- このネストされたオブジェクトの定義は、server_stateとserver_infoで共通です。 -->
|
||||
|
||||
レポートモードサーバでは、`etl_sources`フィールドの各メンバは以下のフィールドを持つオブジェクトです。
|
||||
|
||||
| フィールド | 型 | 説明 |
|
||||
|-----------------------------|-------|-------------|
|
||||
| `connected` | 真偽値 | `true`の場合、レポートモードサーバがこのP2Pモードサーバに接続していることを示します。`false`の場合、サーバに接続していないことを示します。これは設定ミスやネットワーク障害によるものか、P2Pモードサーバが停止している可能性があります。 |
|
||||
| `grpc_port` | 文字列 | このレポート モードサーバが接続し、gRPCを介してレジャーデータを取得するように設定されている P2P モード サーバのポート番号。 |
|
||||
| `ip` | 文字列 | P2PモードサーバのIPアドレス（IPv4またはIPv6）。 |
|
||||
| `last_message_arrival_time` | 文字列 | レポートモードサーバがこのP2Pサーバからメッセージを受信した最新の時刻を示すISO 8601タイムスタンプ。 |
|
||||
| `validated_ledgers_range` | 文字列 | `complete_ledgers`と同じ形式で、このP2Pモードサーバが利用可能であると報告する、有効なレジャーのバージョンの範囲。 |
|
||||
| `websocket_port` | 文字列 | このレポートモードサーバが、レポートモードから直接提供できないWebSocketリクエストを転送するように設定されているP2Pサーバのポート番号。 |
|
||||
@@ -10,4 +10,4 @@ On a reporting mode server, each member of the `etl_sources` field is an object
|
||||
| `ip` | String | The IP address (IPv4 or IPv6) of the P2P mode server. |
|
||||
| `last_message_arrival_time` | String | An ISO 8601 timestamp indicating the most recent time the reporting mode server received a message from this P2P server. |
|
||||
| `validated_ledgers_range` | String | The range of validated ledger versions this P2P mode server reports that it has available, in the same format as `complete_ledgers`. |
|
||||
| `websocket_port` | String | The port number on the P2P server where this reporting mode server is configured to forward WebSocket requests that cannot be served directly from reporting mode. |
|
||||
| `websocket_port` | String | The port number on the P2P server where this reporting mode server is configured to forward WebSocket requests that cannot be served directly from reporting mode. |
|
||||
|
||||
@@ -1,20 +0,0 @@
|
||||
{% if use_network is undefined or use_network == "Testnet" %}
|
||||
{% set ws_url = "wss://s.altnet.rippletest.net:51233" %}
|
||||
{% set explorer_url = "https://testnet.xrpl.org" %}
|
||||
{% set use_network = "Testnet" %}
|
||||
{% elif use_network == "Devnet" %}
|
||||
{% set ws_url = "wss://s.devnet.rippletest.net:51233" %}
|
||||
{% set explorer_url = "https://devnet.xrpl.org" %}
|
||||
{% elif use_network == "Mainnet" %}
|
||||
{% set ws_url = "wss://xrplcluster.com" %}
|
||||
{% set explorer_url = "https://livenet.xrpl.org" %}
|
||||
{% endif %}
|
||||
|
||||
{{ start_step("Connect") }}
|
||||
<button id="connect-button" class="btn btn-primary" data-wsurl="{{ws_url}}" data-explorer="{{explorer_url}}">{{use_network}}に接続する</button>
|
||||
<div>
|
||||
<strong>接続ステータス：</strong>
|
||||
<span id="connection-status">接続されていません</span>
|
||||
<div class="loader collapse" id="loader-connect"><img class="throbber" src="assets/img/xrp-loader-96.png"></div>
|
||||
</div>
|
||||
{{ end_step() }}
|
||||
@@ -1,15 +0,0 @@
|
||||
{% if use_network is undefined or use_network == "Testnet" %}
|
||||
{% set use_network = "Testnet" %}
|
||||
{% set faucet_url = "https://faucet.altnet.rippletest.net/accounts" %}
|
||||
{% elif use_network == "Devnet" %}
|
||||
{% set faucet_url = "https://faucet.devnet.rippletest.net/accounts" %}
|
||||
{# No faucet for Mainnet! #}
|
||||
{% endif %}
|
||||
|
||||
{{ start_step("Generate") }}
|
||||
<button id="generate-creds-button" class="btn btn-primary" data-fauceturl="{{faucet_url}}">{{use_network}}の暗号鍵を作成する</button>
|
||||
<div class="loader collapse"><img class="throbber" src="assets/img/xrp-loader-96.png">暗号鍵を作成しています…</div>
|
||||
<div class="output-area"></div>
|
||||
{{ end_step() }}
|
||||
|
||||
**注意:** Rippleは[TestnetとDevnet](parallel-networks.html)をテストの目的でのみ運用しており、その状態とすべての残高を定期的にリセットしています。予防措置として、Testnet、DevnetとMainnetで同じアドレスを使用**しない**ことをお勧めします。
|
||||
@@ -12,4 +12,4 @@
|
||||
<div class="output-area"></div>
|
||||
{{ end_step() }}
|
||||
|
||||
**Caution:** Ripple provides the [Testnet and Devnet](parallel-networks.html) for testing purposes only, and sometimes resets the state of these test networks along with all balances. As a precaution, **do not** use the same addresses on Testnet/Devnet and Mainnet.
|
||||
**Caution:** Ripple provides the [Testnet and Devnet](../../concepts/networks-and-servers/parallel-networks.md) for testing purposes only, and sometimes resets the state of these test networks along with all balances. As a precaution, **do not** use the same addresses on Testnet/Devnet and Mainnet.
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
{% if use_network is undefined or use_network == "Testnet" %}
|
||||
{% set explorer_url = "https://testnet.xrpl.org" %}
|
||||
{% elif use_network == "Devnet" %}
|
||||
{% set explorer_url = "https://devnet.xrpl.org" %}
|
||||
{% elif use_network == "Mainnet" %}
|
||||
{% set explorer_url = "https://livenet.xrpl.org" %}
|
||||
{% endif %}
|
||||
|
||||
<table class="wait-step" data-explorerurl="{{explorer_url}}">
|
||||
<tr>
|
||||
<th>トランザクションのID:</th>
|
||||
<td class="waiting-for-tx">(無）</td>
|
||||
<tr>
|
||||
<th>最新の検証レジャーインデックス：</th>
|
||||
<td class="validated-ledger-version">接続されていません</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>送信時のレジャーインデックス：</th>
|
||||
<td class="earliest-ledger-version">（まだ送信されません）</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>トランザクションの<code>LastLedgerSequence</code>:</th>
|
||||
<td class="lastledgersequence">(準備されません）</td>
|
||||
</tr>
|
||||
<tr class="tx-validation-status">
|
||||
</tr>
|
||||
</table>
|
||||
@@ -1,5 +0,0 @@
|
||||
XRP Ledgerでは、金融機関は秘密鍵の漏えいに関連するリスクを最小限に抑えるために、複数のXRP Ledgerアドレスを使用するのが一般的です。業界標準では、以下のような役割分担をしています。
|
||||
|
||||
* 1つの**発行アドレス**。「コールドウォレット」とも呼ばれます。このアドレスは、レジャーでの金融機関の会計上の関係の中心となるものですが、トランザクションの送信は可能な限り少なく抑えます。
|
||||
* 1つ以上の**運用アドレス**。「ホットウォレット」とも呼ばれます。インターネットに接続した自動システムが、これらのアドレスへの秘密鍵を使用して、顧客やパートナーへの送金といった日常業務を実施します。
|
||||
* オプションの**待機アドレス**。「ウォームウォレット」とも呼ばれます。信頼できる人間のオペレーターが、これらのアドレスを使用して運用アドレスに送金します。
|
||||
@@ -1,3 +0,0 @@
|
||||
各[レジャー](ledgers.html)の状態ツリーは**レジャーオブジェクト**のセットで構成されており、それらが総合して共有レジャーのすべての設定、残高、関係を表します。
|
||||
|
||||
rippledサーバーが互いに通信するために使用する[ピアプロトコル](peer-protocol.html)では、レジャーオブジェクトは生[バイナリーフォーマット](serialization.html)で表されます。rippled APIでは、レジャーオブジェクトはJSONオブジェクトとして表されます。
|
||||
@@ -1,5 +1,5 @@
|
||||
Each [ledger version](ledgers.html)'s state data is a set of **ledger objects**, sometimes called _ledger entries_, which collectively represent all settings, balances, and relationships at a given point in time. To store or retrieve an object in the state data, the protocol uses that object's unique **[Ledger Object ID](ledger-object-ids.html)**.
|
||||
Each [ledger version](../concepts/ledgers/index.md)'s state data is a set of **ledger objects**, sometimes called _ledger entries_, which collectively represent all settings, balances, and relationships at a given point in time. To store or retrieve an object in the state data, the protocol uses that object's unique **[Ledger Object ID](../references/protocol/ledger-data/common-fields.md)**.
|
||||
|
||||
In the [peer protocol](peer-protocol.html), ledger objects have a [canonical binary format](serialization.html). In `rippled` APIs, ledger objects are represented as JSON objects.
|
||||
In the [peer protocol](../concepts/networks-and-servers/peer-protocol.md), ledger objects have a [canonical binary format](../references/protocol/binary-format.md). In `rippled` APIs, ledger objects are represented as JSON objects.
|
||||
|
||||
A ledger object's data fields depend on the type of object; the XRP Ledger supports the following types:
|
||||
|
||||
@@ -1 +1 @@
|
||||
The valid types are: `account`, `amendments`, `amm` :not_enabled:, `check`, `deposit_preauth`, `directory`, `escrow`, `fee`, `hashes`, `nft_offer`, `offer`, `payment_channel`, `signer_list`, `state` (trust line), and `ticket`.
|
||||
The valid types are: `account`, `amendments`, `amm` {% not-enabled /%}, `check`, `deposit_preauth`, `directory`, `escrow`, `fee`, `hashes`, `nft_offer`, `offer`, `payment_channel`, `signer_list`, `state` (trust line), and `ticket`.
|
||||
|
||||
@@ -1,16 +1 @@
|
||||
{% macro page_children(pg, depth, max_depth, show_blurbs) %}
|
||||
{% if pg.children %}
|
||||
{% if depth == 1 %}<ul class="children-display">{% endif %}
|
||||
{% for child in pg.children %}
|
||||
<li class="level-{{depth}}"><a href="{{child.html}}">{{child.name}}</a>
|
||||
{% if child.status == "not_enabled" %}:not_enabled:{% endif %}
|
||||
<p class="blurb child-blurb">{{child.blurb}}</p>
|
||||
</li>
|
||||
{% if child.children and depth < max_depth %}
|
||||
{{ page_children(child, depth+1, max_depth, show_blurbs) }}
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
{% if depth == 1 %}</ul><!--/.children-display-->{% endif %}
|
||||
{% endif %}
|
||||
{% endmacro %}
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
**注記:** このメソッドにはコマンドライン構文がありません。代わりに[jsonメソッド][]を使って、コマンドラインからこのメソッドにアクセスすることができます。
|
||||
@@ -1 +1,3 @@
|
||||
**Note:** There is no commandline syntax for this method. You can use the [json method][] to access this method from the commandline instead.
|
||||
{% admonition type="info" name="Note" %}
|
||||
There is no commandline syntax for this method. You can use the [json method][] to access this method from the commandline instead.
|
||||
{% /admonition %}
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
| `Field` | 型 | 説明 |
|
||||
|:--------------|:-------|:----------------------------------------------------|
|
||||
| `node` | 文字列 | この予約の対象となるピアサーバーの[ノード公開鍵][]（[base58][]）。 |
|
||||
| `description` | 文字列 | _（省略される場合があります）_ このピアリザベーションの説明（ある場合）。 |
|
||||
@@ -1,11 +0,0 @@
|
||||
### ポート記述子オブジェクト
|
||||
<!-- このネストされたオブジェクトの定義は、server_stateとserver_infoで共通です。 -->
|
||||
|
||||
`ports`配列の各メンバーは以下のフィールドを持つオブジェクトです。
|
||||
|
||||
| フィールド | 値 | 説明 |
|
||||
|------------|-------------|-------------|
|
||||
| `port` | 文字列 - 数値 | サーバがリッスンしているポート番号。 |
|
||||
| `protocol` | 文字列の配列 | このポートに接続されているプロトコルの一覧。有効なプロトコルには、JSON-RPCの`http`または`https`、WebSocketの`ws`、`ws2`、`wss`、`wss2`、[gRPC](configure-grpc.html)の`grpc`、[XRP Ledgerピアプロトコル](peer-protocol.html)の`peer`があります。 |
|
||||
|
||||
**注記:** ネットワークインフラによっては、ここで報告されるポートやプロトコルが、外部のネットワークからサーバに到達する方法と一致しないことがあります。例えば、TLSがロードバランサやプロキシで終了する場合、サーバはあるポートで`http`と報告するかもしれませんが、外部からはポート443の`https`でしか到達できないかもしれません。
|
||||
@@ -6,6 +6,6 @@ Each member of the `ports` array is an object with the following fields:
|
||||
| Field | Value | Description |
|
||||
|------------|-----------------|-------------|
|
||||
| `port` | String - Number | A port number where the server is listening. |
|
||||
| `protocol` | Array of String | A list of protocols being served on this port. Valid protocols include `http` or `https` for JSON-RPC, `ws`, `ws2`, `wss`, `wss2` for WebSocket, `grpc` for [gRPC](configure-grpc.html), and `peer` for the [XRP Ledger Peer Protocol](peer-protocol.html). |
|
||||
| `protocol` | Array of String | A list of protocols being served on this port. Valid protocols include `http` or `https` for JSON-RPC, `ws`, `ws2`, `wss`, `wss2` for WebSocket, `grpc` for [gRPC](../infrastructure/configuration/configure-grpc.md), and `peer` for the [XRP Ledger Peer Protocol](../concepts/networks-and-servers/peer-protocol.md). |
|
||||
|
||||
**Note:** Depending on network infrastructure, the ports and protocols reported here may not match how the server can be reached from the outside network. For example, if TLS terminates at a load balancer or proxy, the server may report `http` on one port, but might only be reachable through `https` on port 443 from outside.
|
||||
**Note:** Depending on network infrastructure, the ports and protocols reported here may not match how the server can be reached from the outside network. For example, if TLS terminates at a load balancer or proxy, the server may report `http` on one port, but might only be reachable through `https` on port 443 from outside.
|
||||
|
||||
@@ -1,33 +0,0 @@
|
||||
`rippled`が残りのネットワークと同期されるまでには数分かかることがあります。その間、レジャーがない旨を知らせる警告が出力されます。
|
||||
|
||||
`rippled`ログメッセージの詳細は、[ログメッセージについて](understanding-log-messages.html)を参照してください。
|
||||
|
||||
`rippled`が残りのネットワークと同期されたら、ストック`rippled`サーバーが完全に機能するようになります。このサーバーを、ローカル署名やXRP LedgerへのAPIアクセスに使用できます。`rippled`サーバーがネットワークと同期されているかどうかを判別するには、[`rippled`サーバーの状況](rippled-server-states.html)を使用します。[`rippled`のコマンドラインインターフェイス](get-started-using-http-websocket-apis.html#コマンドライン)を使用すれば、これを迅速にテストできます。
|
||||
|
||||
```sh
|
||||
rippled server_info
|
||||
```
|
||||
|
||||
rippled APIを使用した`rippled`サーバーとの通信について詳しくは、[rippled API reference](http-websocket-apis.html)を参照してください。
|
||||
|
||||
ストック`rippled`サーバーを実行できたら、次に検証サーバーとして実行してみましょう。検証サーバーについて、そして検証サーバーを実行する理由については、[バリデータとしてのrippledの実行](run-rippled-as-a-validator.html)を参照してください。
|
||||
|
||||
`rippled`サーバーの起動でお困りですか? [rippledサーバーが起動しない](server-wont-start.html)を参照してください。
|
||||
|
||||
### その他の構成
|
||||
|
||||
`rippled`は、デフォルト構成でXRP Ledgerに接続する必要があります。ただし、`rippled.cfg`ファイルを編集すれば、設定を変更できます。推奨される構成設定については、[容量の計画](capacity-planning.html)を参照してください。
|
||||
|
||||
{% include '_snippets/conf-file-location.ja.md' %}<!--_ -->
|
||||
|
||||
すべての構成オプションの説明については、[`rippled` GitHubリポジトリー](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)を参照してください。
|
||||
|
||||
構成の変更を有効にするには、`rippled`を再起動する必要があります。
|
||||
|
||||
`[debug_logfile]`セクションまたは`[database_path]`セクションを変更すると、`rippled`を実行するユーザーに、新しく構成したパスの所有権を付与する必要が生じる場合があります。
|
||||
|
||||
### 更新
|
||||
|
||||
`rippled`を定期的に更新して、残りのXRP Ledgerネットワークと同期させておく必要があります。[rippledのGoogleグループ](https://groups.google.com/forum/#!forum/ripple-server)をサブスクライブすれば、`rippled`の新しいリリースに関する通知を受け取ることができます。
|
||||
|
||||
`rippled`のパッケージには、[Linuxでの自動更新を有効にする](update-rippled-automatically-on-linux.html)ために使用できるスクリプトが含まれています。その他のプラットフォームでは、手動での更新が必要です。
|
||||
@@ -1,24 +1,24 @@
|
||||
It can take several minutes to sync with the rest of the XRP Ledger network, during which time the server outputs various warnings. For information about log messages, see [Understanding Log Messages](understanding-log-messages.html).
|
||||
It can take several minutes to sync with the rest of the XRP Ledger network, during which time the server outputs various warnings. For information about log messages, see [Understanding Log Messages](../infrastructure/troubleshooting/understanding-log-messages.md).
|
||||
|
||||
You can use the [`rippled` commandline interface](get-started-using-http-websocket-apis.html#commandline) to see if your server is synced with the network:
|
||||
You can use the [`rippled` commandline interface](../tutorials/get-started/get-started-using-http-websocket-apis.md#commandline) to see if your server is synced with the network:
|
||||
|
||||
```sh
|
||||
rippled server_info
|
||||
```
|
||||
|
||||
If the `server_state` in the response is `full` or `proposing`, then your server is fully synced to the network. Otherwise, you may need to wait longer. Fresh servers usually sync within 15 minutes; servers that already have [ledger history](ledger-history.html) stored can take longer.
|
||||
If the `server_state` in the response is `full` or `proposing`, then your server is fully synced to the network. Otherwise, you may need to wait longer. Fresh servers usually sync within 15 minutes; servers that already have [ledger history](../concepts/networks-and-servers/ledger-history.md) stored can take longer.
|
||||
|
||||
After your server has synchronized with the rest of the network, you have a fully functional XRP Ledger peer-to-peer server that you can use to submit transactions or get API access to the XRP Ledger. See [Client Libraries](client-libraries.html) or [HTTP / WebSocket APIs](http-websocket-apis.html) for different ways to communicate with the server.
|
||||
After your server has synchronized with the rest of the network, you have a fully functional XRP Ledger peer-to-peer server that you can use to submit transactions or get API access to the XRP Ledger. See [Client Libraries](../references/client-libraries.md) or [HTTP / WebSocket APIs](../references/http-websocket-apis/index.md) for different ways to communicate with the server.
|
||||
|
||||
If you use the XRP Ledger for your business or you want to contribute to the stability of the network, you should run one server as a validator. For information about validating servers and why you might want to run one, see [Run rippled as a Validator](run-rippled-as-a-validator.html).
|
||||
If you use the XRP Ledger for your business or you want to contribute to the stability of the network, you should run one server as a validator. For information about validating servers and why you might want to run one, see [Run rippled as a Validator](../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md).
|
||||
|
||||
Having trouble getting your server started? See [rippled Server Won't Start](server-wont-start.html).
|
||||
Having trouble getting your server started? See [rippled Server Won't Start](../infrastructure/troubleshooting/server-wont-start.md).
|
||||
|
||||
### Additional Configuration
|
||||
|
||||
`rippled` should connect to the XRP Ledger with the default configuration. However, you can change your settings by editing the `rippled.cfg` file. For recommendations about configuration settings, see [Capacity Planning](capacity-planning.html).
|
||||
`rippled` should connect to the XRP Ledger with the default configuration. However, you can change your settings by editing the `rippled.cfg` file. For recommendations about configuration settings, see [Capacity Planning](../infrastructure/installation/capacity-planning.md).
|
||||
|
||||
{% include '_snippets/conf-file-location.md' %}
|
||||
{% partial file="/_snippets/conf-file-location.md" /%}
|
||||
|
||||
See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options.
|
||||
|
||||
@@ -31,4 +31,4 @@ If you change the `[debug_logfile]` or `[database_path]` sections, you may need
|
||||
|
||||
You must update `rippled` regularly to remain synced with the rest of the XRP Ledger network. You can subscribe to the [rippled Google Group](https://groups.google.com/forum/#!forum/ripple-server) to receive notifications of new `rippled` releases.
|
||||
|
||||
The `rippled` package includes a script you can use to [enable automatic updates on Linux](update-rippled-automatically-on-linux.html). On other platforms, you must update manually.
|
||||
The `rippled` package includes a script you can use to [enable automatic updates on Linux](../infrastructure/installation/update-rippled-automatically-on-linux.md). On other platforms, you must update manually.
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
## {{currentpage.name}} Fields
|
||||
## {% $frontmatter.seo.title %} Fields
|
||||
|
||||
In addition to the [common fields](pseudo-transaction-types.html), {{currentpage.name}} pseudo-transactions use the following fields:
|
||||
In addition to the [common fields](../references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types.md), {% $frontmatter.seo.title %} pseudo-transactions use the following fields:
|
||||
|
||||
@@ -1 +1 @@
|
||||
_By default, this method is [admin-only](admin-api-methods.html). It can be used as a public method if the server admin has [enabled public signing](enable-public-signing.html)._
|
||||
_By default, this method is [admin-only](../references/http-websocket-apis/admin-api-methods/index.md). It can be used as a public method if the server admin has [enabled public signing](../infrastructure/configuration/enable-public-signing.md)._
|
||||
|
||||
@@ -1,261 +1 @@
|
||||
<!--{# Links within the dev portal #}-->
|
||||
[Address]: basic-data-types.html#addresses
|
||||
[アドレス]: basic-data-types.html#アドレス
|
||||
[admin command]: admin-api-methods.html
|
||||
[API v1]: request-formatting.html#api-versioning
|
||||
[API v2]: request-formatting.html#api-versioning
|
||||
[base58]: base58-encodings.html
|
||||
[common fields]: transaction-common-fields.html
|
||||
[共通フィールド]: transaction-common-fields.html
|
||||
[Currency Amount]: basic-data-types.html#specifying-currency-amounts
|
||||
[通貨額]: basic-data-types.html#通貨額の指定
|
||||
[通貨額の指定]: basic-data-types.html#通貨額の指定
|
||||
[Currency Code]: currency-formats.html#currency-codes
|
||||
[通貨コード]: currency-formats.html#通貨コード
|
||||
[drops of XRP]: basic-data-types.html#specifying-currency-amounts
|
||||
[fee levels]: transaction-cost.html#fee-levels
|
||||
[手数料レベル]: transaction-cost.html#手数料レベル
|
||||
[XRPのdrop数]: basic-data-types.html#通貨額の指定
|
||||
[Hash]: basic-data-types.html#hashes
|
||||
[ハッシュ]: basic-data-types.html#ハッシュ
|
||||
[identifying hash]: transactions.html#identifying-transactions
|
||||
[識別用ハッシュ]: transactions.html#トランザクションの識別
|
||||
[Internal Type]: serialization.html
|
||||
[内部の型]: serialization.html
|
||||
[Ledger Index]: basic-data-types.html#ledger-index
|
||||
[ledger index]: basic-data-types.html#ledger-index
|
||||
[レジャーインデックス]: basic-data-types.html#レジャーインデックス
|
||||
[ledger format]: ledger-object-types.html
|
||||
[レジャーフォーマット]: ledger-data-formats.html
|
||||
[Marker]: markers-and-pagination.html
|
||||
[マーカー]: markers-and-pagination.html
|
||||
[node public key]: peer-protocol.html#node-key-pair
|
||||
[ノード公開鍵]: peer-protocol.html#ノードキーペア
|
||||
[node key pair]: peer-protocol.html#node-key-pair
|
||||
[ノードキーペア]: peer-protocol.html#ノードキーペア
|
||||
[peer reservation]: peer-protocol.html#fixed-peers-and-peer-reservations
|
||||
[peer reservations]: peer-protocol.html#fixed-peers-and-peer-reservations
|
||||
[ピアリザベーション]: peer-protocol.html#固定ピアとピアリザベーション
|
||||
[public servers]: public-servers.html
|
||||
[公開サーバー]: public-servers.html
|
||||
[result code]: transaction-results.html
|
||||
[seconds since the Ripple Epoch]: basic-data-types.html#specifying-time
|
||||
[Reporting Mode]: rippled-server-modes.html#reporting-mode
|
||||
[レポートモード]: rippled-server-modes.html#レポートモード
|
||||
[Rippleエポック以降の経過秒数]: basic-data-types.html#時間の指定
|
||||
[Sequence Number]: basic-data-types.html#account-sequence
|
||||
[シーケンス番号]: basic-data-types.html#アカウントシーケンス
|
||||
[SHA-512Half]: basic-data-types.html#hashes
|
||||
[SHA-512ハーフ]: basic-data-types.html#ハッシュ
|
||||
[Specifying Currency Amounts]: basic-data-types.html#specifying-currency-amounts
|
||||
[Specifying Ledgers]: basic-data-types.html#specifying-ledgers
|
||||
[レジャーの指定]: basic-data-types.html#レジャーの指定
|
||||
[Specifying Time]: basic-data-types.html#specifying-time
|
||||
[時間の指定]: basic-data-types.html#時間の指定
|
||||
[stand-alone mode]: rippled-server-modes.html#stand-alone-mode
|
||||
[スタンドアロンモード]: rippled-server-modes.html#スタンドアロンモード
|
||||
[standard format]: response-formatting.html
|
||||
[標準フォーマット]: response-formatting.html
|
||||
[Transaction Cost]: transaction-cost.html
|
||||
[transaction cost]: transaction-cost.html
|
||||
[トランザクションコスト]: transaction-cost.html
|
||||
[universal error types]: error-formatting.html#universal-errors
|
||||
[汎用エラータイプ]: error-formatting.html#汎用エラー
|
||||
[XRP, in drops]: basic-data-types.html#specifying-currency-amounts
|
||||
[XRP、drop単位]: basic-data-types.html#通貨額の指定
|
||||
[NFToken]: nftoken.html
|
||||
|
||||
<!-- API object types -->
|
||||
{% set ledger_entries = [
|
||||
"AccountRoot",
|
||||
"Amendments",
|
||||
"AMM",
|
||||
"Check",
|
||||
"DepositPreauth",
|
||||
"DirectoryNode",
|
||||
"Escrow",
|
||||
"FeeSettings",
|
||||
"LedgerHashes",
|
||||
"NegativeUNL",
|
||||
"NFTokenOffer",
|
||||
"NFTokenPage",
|
||||
"Offer",
|
||||
"PayChannel",
|
||||
"RippleState",
|
||||
"SignerList",
|
||||
"Ticket"
|
||||
] %}
|
||||
|
||||
{% for ledger_entry in ledger_entries %}
|
||||
{% if ledger_entry in ["amendments", "depositpreauth", "escrow"] %}
|
||||
{# objects where the naive URL is already taken #}
|
||||
[{{ledger_entry}} object]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}} entry]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}}オブジェクト]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}} オブジェクト]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}}エントリ]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}} エントリ]: {{ledger_entry|lower}}-object.html
|
||||
{% else %}
|
||||
[{{ledger_entry}} object]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}} entry]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}}オブジェクト]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}} オブジェクト]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}}エントリ]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}} エントリ]: {{ledger_entry|lower}}.html
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
|
||||
<!--{# Links to external sites #}-->
|
||||
[crypto-condition]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[crypto-conditions]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[Crypto-Conditions Specification]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[hexadecimal]: https://en.wikipedia.org/wiki/Hexadecimal
|
||||
[Interledger Protocol]: https://interledger.org/
|
||||
[RFC-1751]: https://tools.ietf.org/html/rfc1751
|
||||
[ripple-lib]: https://github.com/XRPLF/xrpl.js
|
||||
|
||||
<!--{# rippled API methods #}-->
|
||||
{% set api_methods = [
|
||||
"account_channels",
|
||||
"account_currencies",
|
||||
"account_info",
|
||||
"account_lines",
|
||||
"account_nfts",
|
||||
"account_objects",
|
||||
"account_offers",
|
||||
"account_tx",
|
||||
"amm_info",
|
||||
"book_offers",
|
||||
"can_delete",
|
||||
"channel_authorize",
|
||||
"channel_verify",
|
||||
"connect",
|
||||
"consensus_info",
|
||||
"crawl_shards",
|
||||
"deposit_authorized",
|
||||
"download_shard",
|
||||
"feature",
|
||||
"fee",
|
||||
"fetch_info",
|
||||
"gateway_balances",
|
||||
"get_counts",
|
||||
"json",
|
||||
"ledger",
|
||||
"ledger_accept",
|
||||
"ledger_cleaner",
|
||||
"ledger_closed",
|
||||
"ledger_current",
|
||||
"ledger_data",
|
||||
"ledger_entry",
|
||||
"ledger_request",
|
||||
"log_level",
|
||||
"logrotate",
|
||||
"manifest",
|
||||
"nft_buy_offers",
|
||||
"nft_info",
|
||||
"nft_sell_offers",
|
||||
"noripple_check",
|
||||
"path_find",
|
||||
"peer_reservations_add",
|
||||
"peer_reservations_del",
|
||||
"peer_reservations_list",
|
||||
"peers",
|
||||
"ping",
|
||||
"print",
|
||||
"random",
|
||||
"ripple_path_find",
|
||||
"server_info",
|
||||
"server_state",
|
||||
"sign",
|
||||
"sign_for",
|
||||
"stop",
|
||||
"submit",
|
||||
"submit_multisigned",
|
||||
"subscribe",
|
||||
"transaction_entry",
|
||||
"tx",
|
||||
"tx_history",
|
||||
"unsubscribe",
|
||||
"validation_create",
|
||||
"validation_seed",
|
||||
"validator_info",
|
||||
"validator_list_sites",
|
||||
"validators",
|
||||
"wallet_propose"
|
||||
] %}
|
||||
|
||||
{% for method in api_methods %}
|
||||
[{{method}} method]: {{method|lower}}.html
|
||||
[{{method}} command]: {{method|lower}}.html
|
||||
[{{method}}メソッド]: {{method|lower}}.html
|
||||
[{{method}} メソッド]: {{method|lower}}.html
|
||||
{% endfor %}
|
||||
|
||||
<!--{# Amendment links #}-->
|
||||
{% set amendment_names = [
|
||||
"AMM",
|
||||
"Checks",
|
||||
"CheckCashMakesTrustLine",
|
||||
"Clawback",
|
||||
"CryptoConditions",
|
||||
"CryptoConditionsSuite",
|
||||
"DeletableAccounts",
|
||||
"DepositAuth",
|
||||
"DepositPreauth",
|
||||
"DID",
|
||||
"DisallowIncoming",
|
||||
"EnforceInvariants",
|
||||
"Escrow",
|
||||
"ExpandedSignerList",
|
||||
"FeeEscalation",
|
||||
"fix1201",
|
||||
"fix1368",
|
||||
"fix1373",
|
||||
"fix1512",
|
||||
"fix1513",
|
||||
"fix1515",
|
||||
"fix1523",
|
||||
"fix1528",
|
||||
"fix1543",
|
||||
"fix1571",
|
||||
"fix1578",
|
||||
"fix1623",
|
||||
"fixCheckThreading",
|
||||
"fixDisallowIncomingV1",
|
||||
"fixFillOrKill",
|
||||
"fixMasterKeyAsRegularKey",
|
||||
"fixNFTokenDirV1",
|
||||
"fixNFTokenRemint",
|
||||
"fixPayChanRecipientOwnerDir",
|
||||
"fixRemoveNFTokenAutoTrustLine",
|
||||
"fixQualityUpperBound",
|
||||
"fixTakerDryOfferRemoval",
|
||||
"fixTrustLinesToSelf",
|
||||
"Flow",
|
||||
"FlowCross",
|
||||
"FlowV2",
|
||||
"ImmediateOfferKilled",
|
||||
"MultiSign",
|
||||
"MultiSignReserve",
|
||||
"NegativeUNL",
|
||||
"NonFungibleTokensV1",
|
||||
"NonFungibleTokensV1_1",
|
||||
"OwnerPaysFee",
|
||||
"PayChan",
|
||||
"RequireFullyCanonicalSig",
|
||||
"SHAMapV2",
|
||||
"SortedDirectories",
|
||||
"SusPay",
|
||||
"TicketBatch",
|
||||
"Tickets",
|
||||
"TickSize",
|
||||
"TrustSetAuth",
|
||||
"XChainBridge",
|
||||
"XRPFees"
|
||||
] %}
|
||||
|
||||
{% for amd in amendment_names %}
|
||||
[{{amd}} amendment]: known-amendments.html#{{amd|lower}}
|
||||
[{{amd}}の修正]: known-amendments.html#{{amd|lower}}
|
||||
{% endfor %}
|
||||
|
||||
@@ -1,59 +1 @@
|
||||
<!-- rippled release notes links -->
|
||||
|
||||
{% set rippled_versions = [
|
||||
"0.26.0",
|
||||
"0.26.1",
|
||||
"0.26.2",
|
||||
"0.26.3-sp1",
|
||||
"0.26.4",
|
||||
"0.26.4-sp1",
|
||||
"0.27.0",
|
||||
"0.27.1",
|
||||
"0.27.2",
|
||||
"0.27.3",
|
||||
"0.27.3-sp1",
|
||||
"0.27.3-sp2",
|
||||
"0.27.4",
|
||||
"0.28.0",
|
||||
"0.28.2",
|
||||
"0.29.0",
|
||||
"0.29.0-hf1",
|
||||
"0.30.0",
|
||||
"0.30.1",
|
||||
"0.31.0",
|
||||
"0.32.0",
|
||||
"0.32.1",
|
||||
"0.33.0",
|
||||
"0.50.0",
|
||||
"0.70.0",
|
||||
"0.70.2",
|
||||
"0.80.0",
|
||||
"0.80.1",
|
||||
"0.90.0",
|
||||
"1.0.0",
|
||||
"1.1.0",
|
||||
"1.2.0",
|
||||
"1.2.1",
|
||||
"1.3.1",
|
||||
"1.4.0",
|
||||
"1.5.0",
|
||||
"1.6.0",
|
||||
"1.7.0",
|
||||
"1.7.2",
|
||||
"1.8.1",
|
||||
"1.10.0",
|
||||
"1.11.0",
|
||||
"1.12.0",
|
||||
"2.0.0"
|
||||
] %}
|
||||
|
||||
{% for v in rippled_versions %}
|
||||
[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 %}
|
||||
|
||||
@@ -1 +1,3 @@
|
||||
**Caution:** Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
|
||||
{% admonition type="warning" name="Caution" %}
|
||||
Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
|
||||
{% /admonition %}
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
**注記:** XRP Ledgerの全履歴では、トランザクションハッシュは一意であるというルールに例外があります。初期の2つの[SetFee疑似トランザクション][]にはまったく同じフィールドがあったため、ハッシュが同じ`1C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B`になっています。これらのトランザクションのうち1つ目は[レジャー3715073に](websocket-api-tool.html?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3715073%7D)表示され、2つ目は[レジャー3721729に](websocket-api-tool.html?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3721729%7D)表示されます。新しい[SetFee疑似トランザクション][]には`LedgerSequence`フィールドが含まれるため、ハッシュは一意であることが保証されています。
|
||||
@@ -1 +1,3 @@
|
||||
**Note:** In the full history of the XRP Ledger, there is an exception to the rule that transaction hashes are unique. Two early [SetFee pseudo-transactions][] had the exact same fields, resulting in the same hash, `1C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B`. The first of these transactions appears [in ledger 3715073](websocket-api-tool.html?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3715073%7D) and the second is [in ledger 3721729](websocket-api-tool.html?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3721729%7D). Newer [SetFee pseudo-transactions][] include a `LedgerSequence` field so that they are guaranteed to be unique.
|
||||
{% admonition type="info" name="Note" %}
|
||||
In the full history of the XRP Ledger, there is an exception to the rule that transaction hashes are unique. Two early [SetFee pseudo-transactions][] had the exact same fields, resulting in the same hash, `1C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B`. The first of these transactions appears [in ledger 3715073](/resources/dev-tools/websocket-api-tool?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3715073%7D) and the second is [in ledger 3721729](/resources/dev-tools/websocket-api-tool?server=wss%3A%2F%2Fs2.ripple.com%2F&req=%7B%22id%22%3A%22setfee_nonunique_hash_1%22%2C%22command%22%3A%22transaction_entry%22%2C%22tx_hash%22%3A%221C15FEA3E1D50F96B6598607FC773FF1F6E0125F30160144BE0C5CBC52F5151B%22%2C%22ledger_index%22%3A3721729%7D). Newer [SetFee pseudo-transactions][] include a `LedgerSequence` field so that they are guaranteed to be unique.
|
||||
{% /admonition %}
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
XRP LedgerのAPIでは、[XRP](what-is-xrp.html)と[トークン](tokens.html)の両方で、通貨の金額を数値で表現するために、JSONのネイティブの数値ではなく文字列を使用します。これは、JSONパーサーが自動的にすべてのJSON数値を浮動小数点形式で表現しようとする可能性がある場合に、精度の低下を防ぐためです。String値の中では、数値はネイティブのJSON数値と同じ方法で処理されます。
|
||||
|
||||
* 10進数
|
||||
* ゼロの接頭辞なし
|
||||
* 小数点として`.`を含むことができます。例えば、½は`0.5`と表されます
|
||||
* 負の金額は`-`から始まります
|
||||
* `E`または`e`は10の累乗（科学的記数法）を表します。例えば`1.2E5`は1.2×10<sup>5</sup>つまり`120000`と同じです。負の指数も可能です。
|
||||
* カンマ(`,`)は使用しません。
|
||||
@@ -1,4 +1,4 @@
|
||||
XRP Ledger APIs generally use strings, rather than native JSON numbers, to represent numeric amounts of currency for both [XRP](what-is-xrp.html) and [tokens](tokens.html). This protects against a loss of precision when using JSON parsers, which may automatically try to represent all JSON numbers in a floating-point format. Within the String value, the numbers are serialized in the same way as native JSON numbers:
|
||||
XRP Ledger APIs generally use strings, rather than native JSON numbers, to represent numeric amounts of currency for both [XRP](../introduction/what-is-xrp.md) and [tokens](../concepts/tokens/index.md). This protects against a loss of precision when using JSON parsers, which may automatically try to represent all JSON numbers in a floating-point format. Within the String value, the numbers are serialized in the same way as native JSON numbers:
|
||||
|
||||
* Base-10.
|
||||
* Non-zero-prefaced.
|
||||
|
||||
@@ -1,3 +0,0 @@
|
||||
トランザクションに署名する最も安全な方法は、[クライアントライブラリ](client-libraries.html)を使用してローカルで署名することです。[signメソッド](sign.html)を使用してトランザクションに署名することもできますが、その場合は信頼できる暗号化された接続を使用するか、ローカル接続を使用して、自分が管理しているサーバーに対してのみに行うようにしてください。
|
||||
|
||||
いずれの場合も、後のために、署名したトランザクションの識別用ハッシュを書き留めておいてください。
|
||||
@@ -1,3 +1,3 @@
|
||||
The most secure way to sign a transaction is to [sign locally with a client library](secure-signing.html#local-signing-example). Alternatively, if you run your own `rippled` node you can sign the transaction using the [sign method](sign.html), but this must be done through a trusted and encrypted connection, or through a local (same-machine) connection.
|
||||
The most secure way to sign a transaction is to [sign locally with a client library](../concepts/transactions/secure-signing.md#local-signing-example). Alternatively, if you run your own `rippled` node you can sign the transaction using the [sign method](../references/http-websocket-apis/admin-api-methods/signing-methods/sign.md), but this must be done through a trusted and encrypted connection, or through a local (same-machine) connection.
|
||||
|
||||
In all cases, note the signed transaction's identifying hash for later.
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
Take the signed transaction blob from the previous step and submit it to a `rippled` server. You can do this safely even if you do not run the `rippled` server. The response contains a provisional result, which should be `tesSUCCESS`, but this result is [usually not final](finality-of-results.html). A provisional response of `terQUEUED` is also OK, since [queued transactions](transaction-cost.html#queued-transactions) are generally included in the next open ledger version (usually about 10 seconds after submission).
|
||||
Take the signed transaction blob from the previous step and submit it to a `rippled` server. You can do this safely even if you do not run the `rippled` server. The response contains a provisional result, which should be `tesSUCCESS`, but this result is [usually not final](../concepts/transactions/finality-of-results/index.md). A provisional response of `terQUEUED` is also OK, since [queued transactions](../concepts/transactions/transaction-cost.md#queued-transactions) are generally included in the next open ledger version (usually about 10 seconds after submission).
|
||||
|
||||
**Tip:** If the preliminary result is `tefMAX_LEDGER`, the transaction has failed permanently because its `LastLedgerSequence` parameter is lower than the current ledger. This happens when you take longer than the expected number of ledger versions between preparing and submitting the transaction. If this occurs, [start over from step 1]({{step_1_link}}) with a higher `LastLedgerSequence` value.
|
||||
|
||||
@@ -1,3 +0,0 @@
|
||||
## {{currentpage.name}} フィールド
|
||||
|
||||
[共通フィールド][]に加えて、{{currentpage.name}}トランザクションは以下のフィールドを使用します。
|
||||
@@ -1,3 +1,3 @@
|
||||
## {{currentpage.name}} Fields
|
||||
## {% $frontmatter.seo.title %} Fields
|
||||
|
||||
In addition to the [common fields][], {{currentpage.name}} transactions use the following fields:
|
||||
In addition to the [common fields][], {% $frontmatter.seo.title %} transactions use the following fields:
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
| フィールド | 値 | 説明 |
|
||||
|:--------------------------------------|:--------------------|:---------------|
|
||||
| `AffectedNodes` | 配列 | このトランザクションで作成、削除、または修正された[レジャーオブジェクト](ledger-object-types.html)のリストと、個々のオブジェクトに対する具体的な変更内容。 |
|
||||
| `DeliveredAmount` | [通貨額][] | **廃止予定。**`delivered_amount`で置き換えられます。Partial Paymentsでない場合は省略されます。 |
|
||||
| `TransactionIndex` | 符号なし整数 | トランザクションが記録されているレジャーでのトランザクションの位置。この配列は0から始まります。（例えば、値が`2`の場合、そのレジャーの3番目のトランザクションであったことを意味します）。 |
|
||||
| `TransactionResult` | 文字列 | トランザクションが成功したか、どのような理由で失敗したかを示す[結果コード](transaction-results.html)。 |
|
||||
| [`delivered_amount`](transaction-metadata.html#delivered_amount) | [通貨額][] | `Destination`アカウントが実際に受取った[通貨額][]。このフィールドは、トランザクションが[Partial Payments](partial-payments.html)であるかどうかにかかわらず、送金された金額を特定するために使用します。[新規: rippled 0.27.0][] |
|
||||
@@ -1,7 +1,7 @@
|
||||
| Field | Value | Description |
|
||||
|:----------------------------------------|:--------------------|:-------------|
|
||||
| `AffectedNodes` | Array | List of [ledger entries](ledger-object-types.html) that were created, deleted, or modified by this transaction, and specific changes to each. |
|
||||
| `DeliveredAmount` | [Currency Amount][] | _(May be omitted)_ For a [partial payment](partial-payments.html), this field records the amount of currency actually delivered to the destination. To avoid errors when reading transactions, instead use the `delivered_amount` field, which is provided for all Payment transactions, partial or not. |
|
||||
| `AffectedNodes` | Array | List of [ledger entries](../references/protocol/ledger-data/ledger-entry-types/index.md) that were created, deleted, or modified by this transaction, and specific changes to each. |
|
||||
| `DeliveredAmount` | [Currency Amount][] | _(May be omitted)_ For a [partial payment](../concepts/payment-types/partial-payments.md), this field records the amount of currency actually delivered to the destination. To avoid errors when reading transactions, instead use the `delivered_amount` field, which is provided for all Payment transactions, partial or not. |
|
||||
| `TransactionIndex` | Unsigned Integer | The transaction's position within the ledger that included it. This is zero-indexed. (For example, the value `2` means it was the 3rd transaction in that ledger.) |
|
||||
| `TransactionResult` | String | A [result code](transaction-results.html) indicating whether the transaction succeeded or how it failed. |
|
||||
| [`delivered_amount`](transaction-metadata.html#delivered_amount) | [Currency Amount][] | _(Omitted for non-Payment transactions)_ The [Currency Amount][] actually received by the `Destination` account. Use this field to determine how much was delivered, regardless of whether the transaction is a [partial payment](partial-payments.html). See [this description](transaction-metadata.html#delivered_amount) for details. |
|
||||
| `TransactionResult` | String | A [result code](../references/protocol/transactions/transaction-results/transaction-results.md) indicating whether the transaction succeeded or how it failed. |
|
||||
| [`delivered_amount`](../references/protocol/transactions/metadata.md#delivered_amount) | [Currency Amount][] | _(Omitted for non-Payment transactions)_ The [Currency Amount][] actually received by the `Destination` account. Use this field to determine how much was delivered, regardless of whether the transaction is a [partial payment](../concepts/payment-types/partial-payments.md). See [this description](../references/protocol/transactions/metadata.md#delivered_amount) for details. |
|
||||
|
||||
@@ -1,53 +1 @@
|
||||
{% set txtypes = [
|
||||
"AccountDelete",
|
||||
"AccountSet",
|
||||
"AMMBid",
|
||||
"AMMDelete",
|
||||
"AMMDeposit",
|
||||
"AMMCreate",
|
||||
"AMMVote",
|
||||
"AMMWithdraw",
|
||||
"CheckCancel",
|
||||
"CheckCash",
|
||||
"CheckCreate",
|
||||
"DepositPreauth",
|
||||
"EscrowCancel",
|
||||
"EscrowCreate",
|
||||
"EscrowFinish",
|
||||
"NFTokenAcceptOffer",
|
||||
"NFTokenBurn",
|
||||
"NFTokenCancelOffer",
|
||||
"NFTokenCreateOffer",
|
||||
"NFTokenMint",
|
||||
"OfferCancel",
|
||||
"OfferCreate",
|
||||
"Payment",
|
||||
"PaymentChannelClaim",
|
||||
"PaymentChannelCreate",
|
||||
"PaymentChannelFund",
|
||||
"SetRegularKey",
|
||||
"SignerListSet",
|
||||
"TicketCreate",
|
||||
"TrustSet"
|
||||
] %}
|
||||
{% set pstxtypes = [
|
||||
"EnableAmendment",
|
||||
"SetFee",
|
||||
"UNLModify"
|
||||
] %}
|
||||
|
||||
|
||||
{% for tx in txtypes %}
|
||||
[{{tx}}]: {{tx|lower}}.html
|
||||
[{{tx}} transaction]: {{tx|lower}}.html
|
||||
[{{tx}} transactions]: {{tx|lower}}.html
|
||||
[{{tx}}トランザクション]: {{tx|lower}}.html
|
||||
[{{tx}} トランザクション]: {{tx|lower}}.html
|
||||
{% endfor %}
|
||||
|
||||
{% for tx in pstxtypes %}
|
||||
[{{tx}}]: {{tx|lower}}.html
|
||||
[{{tx}} pseudo-transaction]: {{tx|lower}}.html
|
||||
[{{tx}} pseudo-transactions]: {{tx|lower}}.html
|
||||
[{{tx}}疑似トランザクション]: {{tx|lower}}.html
|
||||
{% endfor %}
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
サーバー起動後の最初の5～15分間に、サーバーがネットワークの他の部分と同期せず、このようなメッセージが出力されることは特に異常な動作ではありません。サーバー起動後かなり経過してからこれらのメッセージが書き込まれる場合は、問題が発生している可能性があります。一般的な原因としては、ネットワーク接続の信頼性が低いことや、[ハードウェアのスペック](system-requirements.html)が不十分であることが考えられます。また、同じハードウェアで実行されている他のプロセスがリソースをめぐって`rippled`と競合している場合にも発生する可能性があります。（`rippled`とリソースをめぐって競合する可能性のある他のプロセスの例としては、スケジュール済みバックアップ、ウィルススキャナー、定期的なデータベースクリーナーなどがあります。）
|
||||
@@ -1 +1 @@
|
||||
During the first 5 to 15 minutes after the server starts up, it is normal for it to be out of sync with the rest of the network and print messages such as these. If the server writes these messages long after starting up, it could indicate a problem. Common causes include unreliable network connections and insufficient [hardware specs](system-requirements.html). This can also happen when other processes running on the same hardware are competing with `rippled` for resources. (Examples of other processes that may compete with `rippled` for resources include scheduled backups, virus scanners, and periodic database cleaners.)
|
||||
During the first 5 to 15 minutes after the server starts up, it is normal for it to be out of sync with the rest of the network and print messages such as these. If the server writes these messages long after starting up, it could indicate a problem. Common causes include unreliable network connections and insufficient [hardware specs](../infrastructure/installation/system-requirements.md). This can also happen when other processes running on the same hardware are competing with `rippled` for resources. (Examples of other processes that may compete with `rippled` for resources include scheduled backups, virus scanners, and periodic database cleaners.)
|
||||
|
||||
@@ -1,3 +0,0 @@
|
||||
本番環境のネットワークやTestnetでは、レジャーが自動的に閉鎖するまでに4～7秒かかる場合があります。
|
||||
|
||||
スタンドアロンモードで`rippled`を実行している場合は、[ledger_acceptメソッド][]を使用してレジャーを手動で閉鎖します。
|
||||
Reference in New Issue
Block a user