From 0edaa21f474c1ebe4f45340d76c46dd18d3e3065 Mon Sep 17 00:00:00 2001 From: Oliver Eggert Date: Wed, 16 Nov 2022 10:15:06 -0800 Subject: [PATCH] Remove Enable Negative UNL section. --- content/concepts/consensus-network/negative-unl.md | 6 ------ dactyl-config.yml | 1 + 2 files changed, 1 insertion(+), 6 deletions(-) diff --git a/content/concepts/consensus-network/negative-unl.md b/content/concepts/consensus-network/negative-unl.md index 239980f109..5fd532c698 100644 --- a/content/concepts/consensus-network/negative-unl.md +++ b/content/concepts/consensus-network/negative-unl.md @@ -36,12 +36,6 @@ If more than 20% of validators suddenly go offline all at once, the remaining se Negative UNL has no effect on [stand-alone mode](rippled-server-modes.html) since the server does not use consensus in stand-alone mode. -## 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). - - - ## How It Works The Negative UNL is closely tied to the [consensus process](consensus.html) and is designed with safeguards to maintain the continuity and reliability of the network in adverse situations. When all trusted validators are operating normally, the Negative UNL is unused and has no effect. When some validators appear to be offline or out of sync, the Negative UNL rules take effect. diff --git a/dactyl-config.yml b/dactyl-config.yml index 345040f8c3..c38c897ff1 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -914,6 +914,7 @@ pages: targets: - en + # TODO: update translation - md: concepts/consensus-network/negative-unl.ja.md targets: - ja