From 075f794cedb8a7a726cce5e8fa47ca55f2cc17e5 Mon Sep 17 00:00:00 2001 From: MarkusTeufelberger Date: Sat, 6 Apr 2019 10:24:06 +0200 Subject: [PATCH 1/2] Refer to Ripple's recommended list For quite a while now best practice and the default setting in rippled has been to trust anything that's published at https://vl.ripple.com instead of only Ripple's validators. --- content/concepts/consensus-network/amendments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/consensus-network/amendments.md b/content/concepts/consensus-network/amendments.md index 429bdf8062..268a0ee489 100644 --- a/content/concepts/consensus-network/amendments.md +++ b/content/concepts/consensus-network/amendments.md @@ -54,7 +54,7 @@ Each version of `rippled` is compiled with a list of known amendments and the co To become enabled, an amendment must be supported by at least 80% of trusted validators continuously for two weeks. If support for an amendment goes below 80% of trusted validators, the amendment is temporarily rejected. The two week period starts over if the amendment regains support of at least 80% of trusted validators. (This can occur if validators vote differently, or if there is a change in which validators are trusted.) An amendment can gain and lose a majority any number of times before it becomes permanently enabled. An amendment cannot be permanently rejected, but it becomes very unlikely for an amendment to become enabled if new versions of `rippled` do not have the amendment in their known amendments list. -As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the default validators that Ripple operates. For now, trusting only those validators is enough to coordinate with Ripple on releasing new features. +As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the validators on the validator registry that Ripple publishes at https://vl.ripple.com. For now, trusting only those validators is enough to coordinate with Ripple on releasing new features. ### Configuring Amendment Voting From ba706906437a06b241febbecada27eab167cfd69 Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Mon, 8 Apr 2019 15:11:42 -0700 Subject: [PATCH 2/2] Slight tweaks to validator list site description --- content/concepts/consensus-network/amendments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/consensus-network/amendments.md b/content/concepts/consensus-network/amendments.md index 268a0ee489..109e65641d 100644 --- a/content/concepts/consensus-network/amendments.md +++ b/content/concepts/consensus-network/amendments.md @@ -54,7 +54,7 @@ Each version of `rippled` is compiled with a list of known amendments and the co To become enabled, an amendment must be supported by at least 80% of trusted validators continuously for two weeks. If support for an amendment goes below 80% of trusted validators, the amendment is temporarily rejected. The two week period starts over if the amendment regains support of at least 80% of trusted validators. (This can occur if validators vote differently, or if there is a change in which validators are trusted.) An amendment can gain and lose a majority any number of times before it becomes permanently enabled. An amendment cannot be permanently rejected, but it becomes very unlikely for an amendment to become enabled if new versions of `rippled` do not have the amendment in their known amendments list. -As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the validators on the validator registry that Ripple publishes at https://vl.ripple.com. For now, trusting only those validators is enough to coordinate with Ripple on releasing new features. +As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the validators on the validator list that Ripple publishes at . For now, trusting only those validators is enough to coordinate with Ripple on releasing new features. ### Configuring Amendment Voting