Devnet instructions for enabling NegativeUNL

This commit is contained in:
mDuo13
2020-10-16 17:07:02 -07:00
parent 8b5c5385c0
commit bd15a7429d
3 changed files with 27 additions and 8 deletions

View File

@@ -22,6 +22,10 @@ Therefore, if more than 20% of trusted validators go offline or become unable to
However, this means that the network could stop making forward progress if a few widely-trusted validators went offline. As of 2020-10-06, there are 34 validators in Ripple's recommended UNL, so the network would stop making forward progress if 7 or more of them were offline. Furthermore, if one or two validators are out for an extended period of time, the network has less room for disagreement between the remaining validators, which can make it take longer to achieve a consensus.
## Enabling the Negative UNL for Testing
Negative UNL functionality is currently available for testing on [Devnet](parallel-networks.html). You can test the Negative UNL feature by adding or modifying a `[features]` stanza in your `rippled.cfg` file, as described in [Connect Your rippled to a Parallel Network](connect-your-rippled-to-the-xrp-test-net.html).
## Summary
@@ -35,6 +39,8 @@ In cases where validators go offline one or two at a time, the remaining validat
The Negative UNL does not help against situations where greater than 20% of trusted validators suddenly go offline all at once. In that case, the remaining validators would not be able to reach the consensus necessary to adjust the Negative UNL.
Negative UNL has no effect on [stand-alone mode](rippled-server-modes.html) since the server does not use consensus in stand-alone mode.
## How It Works

View File

@@ -1,3 +1,11 @@
---
html: connect-your-rippled-to-the-xrp-test-net.html
funnel: Build
doc_type: Tutorials
category: Manage the rippled Server
subcategory: Configuration
blurb: Connect your rippled server to the test net to try out new features or test functionality with fake money.
---
# Connect Your rippled to a Parallel Network
Ripple hosts [alternative test and development networks](parallel-networks.html) for developers to test their apps on the latest non-production version of the XRP Ledger (Testnet) or to test and experiment with features on the latest beta version (Devnet). **The funds used on these networks are not real funds and are intended for testing only.** You can connect your [`rippled` server](the-rippled-server.html) to either the Testnet or Devnet.
@@ -96,13 +104,24 @@ Edit your `validators.txt` file. This file is located in the same folder as your
# n9LiE1gpUGws1kFGKCM9rVFNYPVS4QziwkQn281EFXX7TViCp2RC
# n9Jq9w1R8UrvV1u2SQqGhSXLroeWNmPNc3AVszRXhpUr1fmbLyhS
## 3. Restart the server.
## 3. (Devnet Only) Enable Features
To connect to Devnet, you must also forcefully enable any experimental features that are currently in testing on Devnet. Add or modify the `[features]` stanza of your config file as follows:
```
[features]
NegativeUNL
```
**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.
```sh
$ sudo systemctl restart rippled
```
## 4. Verify that your server syncs.
## 5. Verify that your server syncs.
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.

View File

@@ -2600,12 +2600,6 @@ pages:
- ja
- md: tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md
html: connect-your-rippled-to-the-xrp-test-net.html
funnel: Build
doc_type: Tutorials
category: Manage the rippled Server
subcategory: Configuration
blurb: Connect your rippled server to the test net to try out new features or test functionality with fake money.
targets:
- en