mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 23:25:51 +00:00
mDuo13
@@ -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
|
||||
|
||||
@@ -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)
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% 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' %}
|
||||
|
||||
@@ -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
|
||||
}
|
||||
```
|
||||
|
||||
@@ -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)の例を参照してください。
|
||||
|
||||
* 利用可能な[公開サーバー][]を利用する:
|
||||
|
||||
|
||||
@@ -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][]:
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ _[Checks Amendment][]が必要です。_
|
||||
|
||||
## 1. 特定のアドレスのすべてのCheckの検索
|
||||
|
||||
<!--{# TODO: Update if https://github.com/ripple/rippled/issues/2443 gets done #}-->
|
||||
<!--{# TODO: Update if https://github.com/XRPLF/rippled/issues/2443 gets done #}-->
|
||||
|
||||
特定のアドレスで受信および送信されるすべてのCheckのリストを取得するには、送金元アカウントのアドレスを指定した`account_objects`コマンドを実行し、要求の`type` フィールドを`checks`に設定します。
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
<!--{# TODO: Update if https://github.com/ripple/rippled/issues/2443 gets done #}-->
|
||||
<!--{# TODO: Update if https://github.com/XRPLF/rippled/issues/2443 gets done #}-->
|
||||
|
||||
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`.
|
||||
|
||||
|
||||
@@ -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は期限切れ状態で永久にレジャーに残ることがありま
|
||||
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% 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' %}
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% 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' %}
|
||||
|
||||
Reference in New Issue
Block a user