mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-16 01:35:50 +00:00
Get Started organization updates
- Split off "Public Servers" page - Rename and reorder getting started pages by language
This commit is contained in:
mDuo13
@@ -32,6 +32,8 @@
|
||||
[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
|
||||
|
||||
@@ -10,7 +10,7 @@ blurb: rippled is the core peer-to-peer server that manages the XRP Ledger. This
|
||||
|
||||
## Reasons to Run Your Own Server
|
||||
|
||||
For lighter use cases and individual servers, you can often rely on free [public servers](https://xrpl.org/get-started-with-the-rippled-api.html#public-servers). However, the more serious your use of the XRP Ledger becomes, the more important it becomes to have your own infrastructure.
|
||||
For lighter use cases and individual servers, you can often rely on free [public servers][]. However, the more serious your use of the XRP Ledger becomes, the more important it becomes to have your own infrastructure.
|
||||
|
||||
There are lots of reasons you might want to run your own `rippled` server, but most of them can be summarized as: you can trust your own server, you have control over its workload, and you're not at the mercy of others to decide when and how you can access it. Of course, you must practice good network security to protect your server from malicious hackers.
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@ For other programming languages, you can access the XRP Ledger through the [HTTP
|
||||
|
||||
| Language | Library Name | Get Started | API Reference | Source Code |
|
||||
|----------|--------------|-------------|---------------|-------------|
|
||||
| **Python** | `xrpl-py` | [Get Started](get-started-using-python.html) | [API Reference](https://xrpl-py.readthedocs.io/) | [Repo](https://github.com/XRPLF/xrpl-py) |
|
||||
| **JavaScript** / **TypeScript** | `ripple-lib` | [Get Started](get-started-with-rippleapi-for-javascript.html) | [API Reference](rippleapi-reference.html) | [Repo](https://github.com/ripple/ripple-lib) |
|
||||
| **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** | `ripple-lib` | [Get Started](get-started-using-node-js.html) | [API Reference](rippleapi-reference.html) | [Repo](https://github.com/ripple/ripple-lib) |
|
||||
| **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/)) |
|
||||
| **Java** | `xrpl4j` | [README](https://github.com/XRPLF/xrpl4j#readme) | [API Reference](https://github.com/XRPLF/xrpl4j/tree/main/xrpl4j-integration-tests) | [Repo](https://github.com/XRPLF/xrpl4j) |
|
||||
| **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}})!
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
html: get-started-with-the-rippled-api.html
|
||||
html: get-started-using-http-websocket-apis.html
|
||||
parent: get-started.html
|
||||
blurb: XRP Ledgerの操作に使用できるAPIとライブラリを使い始めましょう。
|
||||
cta_text: 開始しよう
|
||||
---
|
||||
# XRP Ledger APIの使用開始
|
||||
# HTTP / WebSocket APIの使用開始
|
||||
|
||||
XRP Ledgerのコアサーバーソフトウェアは[`rippled`](the-rippled-server.html)です。XRP Ledgerでの開発に進むには、`rippled`サーバーのAPIにアクセスします。
|
||||
|
||||
@@ -1,44 +1,35 @@
|
||||
---
|
||||
html: get-started-with-the-rippled-api.html
|
||||
html: get-started-using-http-websocket-apis.html
|
||||
parent: get-started.html
|
||||
blurb: Unleash the full power of the XRP Ledger's native APIs.
|
||||
cta_text: Get Started
|
||||
---
|
||||
# Get Started with XRP Ledger APIs
|
||||
# Get Started Using HTTP / WebSocket APIs
|
||||
|
||||
The XRP Ledger's core server software is [`rippled`](the-rippled-server.html). You can jump straight into developing on the XRP Ledger by accessing the API of a `rippled` server.
|
||||
If you don't have or don't want to use a [client library](client-libraries.html) in your preferred programming language, you can access the XRP Ledger directly through the APIs of its core server software, [`rippled`](the-rippled-server.html). The server provides APIs over JSON-RPC and WebSocket protocols. If you don't [run your own instance of `rippled`](install-rippled.html) you can still use a [public server][public servers].
|
||||
|
||||
The quickest way to dive into the API is with the [**WebSocket API Tool**](websocket-api-tool.html), or use the [XRP Ledger Explorer](https://livenet.xrpl.org/) to watch the progress of the ledger live.
|
||||
**Tip:** You can dive right into the API is with the [**WebSocket API Tool**](websocket-api-tool.html), or use the [XRP Ledger Explorer](https://livenet.xrpl.org/) to watch the progress of the ledger live.
|
||||
|
||||
You can also [run your own instance of `rippled`](install-rippled.html) or use a [public server](#public-servers).
|
||||
## Differences Between JSON-RPC and WebSocket
|
||||
|
||||
## Public Servers
|
||||
Both JSON-RPC and WebSocket are HTTP-based protocols, and for the most part the data provided over both protocols is the same. The major differences are as follows:
|
||||
|
||||
Ripple provides several public servers for the benefit of the XRP Ledger community:
|
||||
- JSON-RPC uses individual HTTP requests and responses for each call, similar to a RESTful API. You can use any common HTTP client such as [curl](https://curl.haxx.se/), [Postman](https://www.postman.com/downloads/), or [Requests](https://docs.python-requests.org/) to access this API.
|
||||
- WebSocket uses a persistent connection that allows the server to push data to the client. Functions that require push messages, like [event subscriptions](subscribe.html), are only available using WebSocket.
|
||||
|
||||
| Operator | [Network][] | JSON-RPC URL | WebSocket URL | Notes |
|
||||
|:----------|:------------|:-------------|:--------------|:---------------------|
|
||||
| XRP Ledger Foundation | **Mainnet** | `https://xrpl.ws/` | `wss://xrpl.ws/` | Full history server cluster. |
|
||||
| Ripple¹ | **Mainnet** | `https://s1.ripple.com:51234/` | `wss://s1.ripple.com/` | General purpose server cluster |
|
||||
| Ripple¹ | **Mainnet** | `https://s2.ripple.com:51234/` | `wss://s2.ripple.com/` | [Full-history server](ledger-history.html#full-history) cluster |
|
||||
| Ripple¹ | Testnet | `https://s.altnet.rippletest.net:51234/` | `wss://s.altnet.rippletest.net/` | Testnet public server |
|
||||
| Ripple¹ | Devnet | `https://s.devnet.rippletest.net:51234/` | `wss://s.devnet.rippletest.net/` | Devnet public server |
|
||||
|
||||
[Network]: parallel-networks.html
|
||||
|
||||
¹Ripple's public servers are not for sustained or business use, and they may become unavailable at any time. For regular use, you should run your own `rippled` server or contract someone you trust to do so. Ripple includes [Reporting Mode][] servers in its public clusters.
|
||||
Both APIs can be served unencrypted (`http://` and `ws://`) or encrypted using TLS (`https://` and `wss://`). Unencrypted connections should not be served over open networks, but can be used when the client is on the same machine as the server.
|
||||
|
||||
|
||||
## Admin Access
|
||||
|
||||
`rippled` API methods are divided into [Public Methods](public-rippled-methods.html) and [Admin Methods](admin-rippled-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 API methods are divided into [Public Methods](public-rippled-methods.html) and [Admin Methods](admin-rippled-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.
|
||||
|
||||
|
||||
## WebSocket API
|
||||
|
||||
If you are looking to try out some methods on the XRP Ledger, you can skip writing your own WebSocket code and go straight to using the API at the [Ripple WebSocket API Tool](websocket-api-tool.html). Later on, when you want to connect to your own `rippled` server, you can [build your own client in the browser](monitor-incoming-payments-with-websocket.html) or [in Node.js](https://www.npmjs.com/package/ws).
|
||||
If you are looking to try out some methods on the XRP Ledger, you can skip writing your own WebSocket code and go straight to using the API at the [WebSocket API Tool](websocket-api-tool.html). Later on, when you want to connect to your own `rippled` server, you can [build your own client](monitor-incoming-payments-with-websocket.html) or use a [client library](client-libraries.html) with WebSocket support.
|
||||
|
||||
Example WebSocket API request:
|
||||
|
||||
@@ -50,7 +41,9 @@ Example WebSocket API request:
|
||||
}
|
||||
```
|
||||
|
||||
The response to [this command][server_info method] shows you the current status of the server. Or, read more about [Request Formatting](request-formatting.html) and [Response Formatting](response-formatting.html).
|
||||
The response to shows you the current status of the server.
|
||||
|
||||
Read more: [Request Formatting >](request-formatting.html) [Response Formatting >](response-formatting.html) [About the server_info method >][server_info method]
|
||||
|
||||
## JSON-RPC
|
||||
|
||||
@@ -38,10 +38,10 @@ In this tutorial, you'll learn:
|
||||
The [`xrpl4j` library](https://github.com/XRPLF/xrpl4j) is available on [Maven Central](https://search.maven.org/artifact/org.xrpl/xrpl4j-parent).
|
||||
`xrpl4j` is split into multiple artifacts, which can be imported as needed.
|
||||
|
||||
In this tutorial, you will need the [xrpl4j-client](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/index.html),
|
||||
[xrpl4j-address-codec](https://javadoc.io/doc/org.xrpl/xrpl4j-address-codec/latest/index.html),
|
||||
[xrpl4j-keypairs](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/index.html), and
|
||||
[xrpl4j-model](https://javadoc.io/doc/org.xrpl/xrpl4j-model/latest/index.html) modules.
|
||||
In this tutorial, you will need the [xrpl4j-client](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/index.html),
|
||||
[xrpl4j-address-codec](https://javadoc.io/doc/org.xrpl/xrpl4j-address-codec/latest/index.html),
|
||||
[xrpl4j-keypairs](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/index.html), and
|
||||
[xrpl4j-model](https://javadoc.io/doc/org.xrpl/xrpl4j-model/latest/index.html) modules.
|
||||
|
||||
To install with Maven, add the following to your project's `pom.xml` file and then run `mvn install`:
|
||||
|
||||
@@ -86,7 +86,7 @@ Here are the basic steps you'll need to cover for almost any XRP Ledger project:
|
||||
|
||||
### {{n.next()}}. Connect to the XRP Ledger
|
||||
|
||||
To make queries and submit transactions, you need to establish a connection to the XRP Ledger. To do this with `xrpl4j`,
|
||||
To make queries and submit transactions, you need to establish a connection to the XRP Ledger. To do this with `xrpl4j`,
|
||||
you can use an [`XrplClient`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html):
|
||||
|
||||
{{ include_code("_code-samples/xrpl4j/GetAccountInfo.java", start_with="// Construct a network client", end_before="// Create a Wallet using a WalletFactory", language="java") }}
|
||||
@@ -102,21 +102,21 @@ The sample code in the previous section shows you how to connect to the Testnet,
|
||||
|
||||
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.
|
||||
|
||||
* By using one of the [available public servers](get-started-with-the-rippled-api.html#public-servers):
|
||||
* By using one of the available [public servers][]:
|
||||
|
||||
final HttpUrl rippledUrl = HttpUrl.get("https://s2.ripple.com:51234/");
|
||||
XrplClient xrplClient = new XrplClient(rippledUrl);
|
||||
|
||||
### {{n.next()}}. Generate wallet
|
||||
|
||||
To store value and execute transactions on the XRP Ledger, you need to create a wallet:
|
||||
a [set of keys](cryptographic-keys.html#key-components) and an [address](accounts.html#addresses) that's
|
||||
been [funded with enough XRP](accounts.html#creating-accounts) to meet the [account reserve](reserves.html).
|
||||
The address is the identifier of your account and you use the [private key](cryptographic-keys.html#private-key) to
|
||||
sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up
|
||||
To store value and execute transactions on the XRP Ledger, you need to create a wallet:
|
||||
a [set of keys](cryptographic-keys.html#key-components) and an [address](accounts.html#addresses) that's
|
||||
been [funded with enough XRP](accounts.html#creating-accounts) to meet the [account reserve](reserves.html).
|
||||
The address is the identifier of your account and you use the [private key](cryptographic-keys.html#private-key) to
|
||||
sign transactions that you submit to the XRP Ledger. For production purposes, you should take care to store your keys and set up
|
||||
a [secure signing method](set-up-secure-signing.html).
|
||||
|
||||
For testing and development purposes, you can use the [XRP Faucets](xrp-testnet-faucet.html) to fund
|
||||
For testing and development purposes, you can use the [XRP Faucets](xrp-testnet-faucet.html) to fund
|
||||
an account on the Testnet or Devnet.
|
||||
|
||||
To make it easy to generate a new, random Wallet, `xrpl4j` provides the [`DefaultWalletFactory`](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/org/xrpl/xrpl4j/wallet/DefaultWalletFactory.html).
|
||||
@@ -131,10 +131,10 @@ System.out.println(testWallet);
|
||||
|
||||
// print output
|
||||
Wallet {
|
||||
privateKey= -HIDDEN-,
|
||||
publicKey=ED90635A6F2A5905D3D5CD2C14905FFB2D838185993576CA4CEE24A920D0D6BD6B,
|
||||
classicAddress=raj5eirfEpbN9YzG9FzB8ZPNyjpFvH6ycV,
|
||||
xAddress=T76mQFr9zLGi2LCjVDgJ7mEQCk4767SdEL32mZFygpdGcFf,
|
||||
privateKey= -HIDDEN-,
|
||||
publicKey=ED90635A6F2A5905D3D5CD2C14905FFB2D838185993576CA4CEE24A920D0D6BD6B,
|
||||
classicAddress=raj5eirfEpbN9YzG9FzB8ZPNyjpFvH6ycV,
|
||||
xAddress=T76mQFr9zLGi2LCjVDgJ7mEQCk4767SdEL32mZFygpdGcFf,
|
||||
isTest=true
|
||||
}
|
||||
```
|
||||
@@ -184,20 +184,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=rBXHGshqXu3Smy9FUsQTmo49bGpQUQEm3X,
|
||||
balance=1000000000,
|
||||
flags=0,
|
||||
ownerCount=0,
|
||||
previousTransactionId=0000000000000000000000000000000000000000000000000000000000000000,
|
||||
previousTransactionLedgerSequence=0,
|
||||
sequence=17178149,
|
||||
signerLists=[],
|
||||
ledgerEntryType=ACCOUNT_ROOT,
|
||||
account=rBXHGshqXu3Smy9FUsQTmo49bGpQUQEm3X,
|
||||
balance=1000000000,
|
||||
flags=0,
|
||||
ownerCount=0,
|
||||
previousTransactionId=0000000000000000000000000000000000000000000000000000000000000000,
|
||||
previousTransactionLedgerSequence=0,
|
||||
sequence=17178149,
|
||||
signerLists=[],
|
||||
index=0DC1B13C73A7F3D2D82446526D0C5D08E88F89BA442D54291117F1A08E447685
|
||||
},
|
||||
ledgerCurrentIndex=17178149,
|
||||
},
|
||||
ledgerCurrentIndex=17178149,
|
||||
validated=false
|
||||
}
|
||||
```
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
html: get-started-with-rippleapi-for-javascript.html
|
||||
html: get-started-using-node-js.html
|
||||
parent: get-started.html
|
||||
blurb: XRP Ledgerに照会するエントリーレベルのJavaScriptアプリケーションを構築します。
|
||||
---
|
||||
@@ -7,7 +7,7 @@ blurb: XRP Ledgerに照会するエントリーレベルのJavaScriptアプリ
|
||||
|
||||
このチュートリアルでは、[Node.js](http://nodejs.org/)と[RippleAPI](rippleapi-reference.html)（XRP LedgerにアクセスするためのJavaScript API）を使用して、XRP Ledgerに接続されるアプリケーションを開発するための基本事項を説明します。
|
||||
|
||||
このガイドで使用しているスクリプトと構成ファイルは、[Ripple開発者ポータルのGitHubリポジトリで入手できます](https://github.com/ripple/ripple-dev-portal/tree/master/content/_code-samples/rippleapi_quickstart)。
|
||||
このガイドで使用しているスクリプトと構成ファイルは、[このサイトのGitHubリポジトリで入手できます](https://github.com/ripple/ripple-dev-portal/tree/master/content/_code-samples/rippleapi_quickstart)。
|
||||
|
||||
|
||||
<!--#{ keep multiple H1s so that all steps are surfaced in sidebar. Do not change H1 titles unless they provide a clear improvement bc they are linked to on external sites. }# -->
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
html: get-started-with-rippleapi-for-javascript.html
|
||||
html: get-started-using-node-js.html
|
||||
parent: get-started.html
|
||||
blurb: Build an entry-level JavaScript application for querying the XRP Ledger in Node.js.
|
||||
---
|
||||
# Get Started with RippleAPI for Node.js
|
||||
# Get Started Using Node.js
|
||||
|
||||
This tutorial guides you through the basics of building an XRP Ledger-connected application using [Node.js](http://nodejs.org/) and [RippleAPI](rippleapi-reference.html), a JavaScript API for accessing the XRP Ledger. You can also use RippleAPI [straight from your browser](get-started.html).
|
||||
This tutorial guides you through the basics of building an XRP Ledger-connected application using [Node.js](http://nodejs.org/) and [RippleAPI](rippleapi-reference.html), a JavaScript/TypeScript client library for accessing the XRP Ledger. You can also use RippleAPI [straight from your browser](get-started.html).
|
||||
|
||||
The scripts and config files used in this guide are [available in the Ripple Dev Portal GitHub Repository](https://github.com/ripple/ripple-dev-portal/tree/master/content/_code-samples/rippleapi_quickstart).
|
||||
The scripts and config files used in this guide are [available in this website's GitHub Repository](https://github.com/ripple/ripple-dev-portal/tree/master/content/_code-samples/rippleapi_quickstart).
|
||||
|
||||
|
||||
<!--#{ keep multiple H1s so that all steps are surfaced in sidebar. Do not change H1 titles unless they provide a clear improvement bc they are linked to on external sites. }# -->
|
||||
@@ -69,7 +69,7 @@ The sample code in the previous section shows you how to connect to the Testnet,
|
||||
|
||||
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.
|
||||
|
||||
* By using one of the [available public servers](get-started-with-the-rippled-api.html#public-servers):
|
||||
* By using one of the available [public servers][]:
|
||||
|
||||
from xrpl.clients import JsonRpcClient
|
||||
JSON_RPC_URL = "https://s2.ripple.com:51234/"
|
||||
|
||||
29
content/tutorials/get-started/public-servers.md
Normal file
29
content/tutorials/get-started/public-servers.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
html: public-servers.html
|
||||
parent: get-started.html
|
||||
blurb: Use these public servers to access the XRP Ledger without needing your own infrastructure.
|
||||
---
|
||||
# Public Servers
|
||||
|
||||
If you don't [run your own `rippled` server](install-rippled.html), you can use the following public servers to submit transactions or read data from the ledger.
|
||||
|
||||
| Operator | [Network][] | JSON-RPC URL | WebSocket URL | Notes |
|
||||
|:----------|:------------|:-------------|:--------------|:---------------------|
|
||||
| XRP Ledger Foundation | **Mainnet** | `https://xrplcluster.com/` <br> `https://xrpl.ws/` [²][] | `wss://xrplcluster.com/` <br> `wss://xrpl.ws/` [²][] | Full history server cluster. |
|
||||
| Ripple[¹][] | **Mainnet** | `https://s1.ripple.com:51234/` | `wss://s1.ripple.com/` | General purpose server cluster |
|
||||
| Ripple[¹][] | **Mainnet** | `https://s2.ripple.com:51234/` | `wss://s2.ripple.com/` | [Full-history server](ledger-history.html#full-history) cluster |
|
||||
| Ripple[¹][] | Testnet | `https://s.altnet.rippletest.net:51234/` | `wss://s.altnet.rippletest.net/` | Testnet public server |
|
||||
| Ripple[¹][] | Devnet | `https://s.devnet.rippletest.net:51234/` | `wss://s.devnet.rippletest.net/` | Devnet public server |
|
||||
|
||||
[Network]: parallel-networks.html
|
||||
[¹]: #footnote-1
|
||||
[²]: #footnote-2
|
||||
|
||||
<a id="footnote-1"></a>¹ Ripple's public servers are not for sustained or business use, and they may become unavailable at any time. For regular use, you should run your own `rippled` server or contract someone you trust to do so. Ripple includes [Reporting Mode][] servers in its public clusters.
|
||||
|
||||
<a id="footnote-2"></a>² `xrpl.ws` is an alias for `xrplcluster.com`. However, the `.ws` top-level domain's reliability may be unsuitable for production uses.
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
{% include '_snippets/tx-type-links.md' %}
|
||||
{% include '_snippets/rippled_versions.md' %}
|
||||
@@ -122,7 +122,7 @@ $ sudo systemctl restart rippled
|
||||
|
||||
It takes about 5 to 15 minutes to sync to the network after a restart. After your server is synced, the [server_info method][] shows the a `validated_ledger` object based on the network you are connected to.
|
||||
|
||||
To verify that your `rippled` is connected to the XRP Testnet or Devnet, compare the results from your server to [a public server](get-started-with-the-rippled-api.html#public-servers) on the Testnet or Devnet. The `seq` field of the `validated_ledger` object should be the same on both servers (possibly off by one or two, if it changed as you were checking).
|
||||
To verify that your `rippled` is connected to the XRP Testnet or Devnet, compare the results from your server to [a public server][public servers] on the Testnet or Devnet. The `seq` field of the `validated_ledger` object should be the same on both servers (possibly off by one or two, if it changed as you were checking).
|
||||
|
||||
The following example shows how to check the latest validated ledger from the commandline:
|
||||
|
||||
@@ -158,7 +158,7 @@ $ rippled --rpc_ip 34.201.59.230:51234 server_info | grep seq
|
||||
|
||||
<!-- MULTICODE_BLOCK_END -->
|
||||
|
||||
**Note:** The IP addresses in these examples are for public servers, and may change periodically. If you get no response, look up the IP address of a [public server](get-started-with-the-rippled-api.html#public-servers), for example using the `dig` command.
|
||||
**Note:** The IP addresses in these examples are for public servers, and may change periodically. If you get no response, look up the IP address of a [public server][public servers], for example using the `dig` command.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -157,7 +157,6 @@ targets:
|
||||
"rippled-server-modes.html#reporting-mode": "rippled-server-modes.html#レポーティングモード"
|
||||
# Fix links for untranslated get-started-using-python.html:
|
||||
"the-rippled-server.html#reasons-to-run-your-own-server": "rippled-server-modes.html#ストックサーバーを運用する理由"
|
||||
"get-started-with-the-rippled-api.html#public-servers": "get-started-with-the-rippled-api.html#公開サーバー"
|
||||
"cryptographic-keys.html#key-components": "cryptographic-keys.html#キーの生成"
|
||||
"accounts.html#addresses": "accounts.html#アドレス"
|
||||
"cryptographic-keys.html#private-key": "cryptographic-keys.html#キーの生成"
|
||||
@@ -1007,31 +1006,57 @@ pages:
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/public-servers.md
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/get-started-using-python.md
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/get-started-using-java.md
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/get-started-with-the-rippled-api.md
|
||||
- md: tutorials/get-started/get-started-using-node-js.md
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: tutorials/get-started/get-started-with-the-rippled-api.ja.md
|
||||
- md: tutorials/get-started/get-started-using-node-js.ja.md
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/get-started-with-rippleapi-for-javascript.md
|
||||
# Redirect for old JS Client Library URL
|
||||
- name: Get Started Using Node.js
|
||||
html: get-started-with-rippleapi-for-javascript.html
|
||||
template: template-redirect.html
|
||||
redirect_url: get-started-using-node-js.html
|
||||
nav_omit: true
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
|
||||
- md: tutorials/get-started/get-started-using-http-websocket-apis.md
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: tutorials/get-started/get-started-with-rippleapi-for-javascript.ja.md
|
||||
- md: tutorials/get-started/get-started-using-http-websocket-apis.ja.md
|
||||
targets:
|
||||
- ja
|
||||
|
||||
# Redirect for old HTTP/WebSocket APIs URL
|
||||
- name: Get Started Using HTTP / WebSocket APIs
|
||||
html: get-started-with-the-rippled-api.html
|
||||
template: template-redirect.html
|
||||
redirect_url: get-started-using-http-websocket-apis.html
|
||||
nav_omit: true
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
|
||||
- md: tutorials/use-simple-xrp-payments/send-xrp.md
|
||||
targets:
|
||||
- en
|
||||
|
||||
Reference in New Issue
Block a user