ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-26 14:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

AMM-Devnet connection info

Browse Source
This commit is contained in:
mDuo13
2022-12-16 16:18:49 -08:00
parent daeabe6c9d
commit 116ce417d7
5 changed files with 127 additions and 88 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.ja.md
View File

@@ -84,17 +84,11 @@ Rippleは[代替となるテスト用および開発用ネットワーク](paral
4. `rippled`がXRP TestnetまたはDevnetに接続していることを確認するため、サーバーで[server_infoメソッド][]を使用して、その結果をTestnetまたはDevnetの公開サーバーの結果と比較します。両方のサーバーで`validated_ledger`オブジェクトの`seq`フィールドが同一である必要があります（確認中にこの数が変化した場合は、1～2の差が生じる可能性があります）。
以下のコマンドは、Testnetサーバーの最新の検証済みレジャーをチェックします。
以下のコマンドは、ローカルの`rippled`の最新検証済みレジャーインデックスをチェックします。
$ ./rippled --rpc_ip s.altnet.rippletest.net:51234 server_info | grep seq
$ ./rippled server_info | grep seq
以下のコマンドは、Devnetサーバーの最新の検証済みレジャーをチェックします。
$ ./rippled --rpc_ip s.devnet.rippletest.net:51234 server_info | grep seq
以下のコマンドは、ローカルの`rippled`の最新検証済みレジャーインデックスをチェックします。
$ ./rippled server_info | grep seq
[WebSocket Toolのserver_info](websocket-api-tool.html#server_info)でネットワークのレジャーインデックスをチェックします。
## 関連項目

91
content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md
View File

@@ -47,6 +47,11 @@ Edit your `rippled.cfg` file.
[ips]
xls20-sandbox.rippletest.net 51235
*AMM-Devnet*
[ips]
amm.devnet.rippletest.net 51235
<!-- MULTICODE_BLOCK_END -->
2. Comment out the previous `[ips]` stanza, if there is one:
@@ -80,6 +85,11 @@ Edit your `rippled.cfg` file.
[network_id]
20
*AMM-Devnet*
[network_id]
25
<!-- MULTICODE_BLOCK_END -->
For sidechains and custom networks, everyone who connects to the network should use a value unique to that network. When creating a new network, choose a network ID at random from the integers 11 to 4,294,967,295.
@@ -127,9 +137,17 @@ Edit your `validators.txt` file. This file is located in the same folder as your
[validator_list_keys]
ED8E43A943A174190BA2FAE91F44AC6E2D1D8202EFDCC2EA3DBB39814576D690F7
*AMM-Devnet*
[validator_list_sites]
http://vlamm.devnet.rippletest.net/
[validator_list_keys]
03553F67DC5A6FE0EBFE1B3B4742833D14AF7C65E79E5760EC76EC56EAFD254CE9
<!-- MULTICODE_BLOCK_END -->
**Tip:** The packages for the NFT preview should already contain the necessary stanzas, but check them just in case.
**Tip:** Preview packages might come with the necessary stanzas pre-configured, but check them just in case.
1. Comment out any previous `[validator_list_sites]`, `[validator_list_keys]`, or `[validators]` stanzas.
@@ -151,15 +169,51 @@ Edit your `validators.txt` file. This file is located in the same folder as your
# n9LiE1gpUGws1kFGKCM9rVFNYPVS4QziwkQn281EFXX7TViCp2RC
# n9Jq9w1R8UrvV1u2SQqGhSXLroeWNmPNc3AVszRXhpUr1fmbLyhS
## 3. (NFT-Devnet Only) Enable Features
## 3. Enable (or Disable) Features
To connect to the NFT-Devnet, you must also forcefully enable the NFT feature, `XLS20`. Add or modify the `[features]` stanza of your config file as follows:
For some test networks using experimental features, you must also forcefully enable the appropriate feature in the config file. For other networks, you should not use the `[features]` stanza. Add or modify the `[features]` stanza of your config file as follows:
<!-- MULTICODE_BLOCK_START -->
_Testnet_
```
# [features]
# Delete or comment out. Don't force-enable features on Testnet.
```
_Devnet_
```
# [features]
# Delete or comment out. Don't force-enable features on Devnet.
```
_Mainnet_
```
# [features]
# Delete or comment out. Don't force-enable features on Mainnet.
```
_NFT-Devnet_
```
[features]
NonFungibleTokensV1
```
_AMM-Devnet_
```
[features]
AMM
```
<!-- MULTICODE_BLOCK_END -->
(On Mainnet, Testnet, and Devnet, no you)
**Warning:** Do not use the `[features]` stanza when connecting to Mainnet or Testnet. Forcefully enabling different features than the rest of the network could cause your server to diverge from the network.
## 4. Restart the server.
@@ -172,40 +226,15 @@ $ 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][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 right network, 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:
<!-- MULTICODE_BLOCK_START -->
*Local Server*
The following example shows how to check your server's latest validated ledger from the commandline:
```sh
rippled server_info | grep seq
```
*Testnet*
```sh
rippled --rpc_ip s.altnet.rippletest.net:51234 server_info | grep seq
```
*Devnet*
```sh
rippled --rpc_ip s.devnet.rippletest.net:51234 server_info | grep seq
```
*Mainnet*
```sh
rippled --rpc_ip s1.ripple.com:51234 server_info | grep seq
```
<!-- MULTICODE_BLOCK_END -->
You can use [server_info in the WebSocket Tool](websocket-api-tool.html#server_info) to look up the latest ledger index on the intended network.