Ripple's Decentralization Strategy

Copied from the following link:

mDuo13 wrote this. Kudos to him.

To recap the Decentralization Strategy, here's a summary:
  1. Switch to using a validator list site ( This is where we are now.
    • All rippled instances configured to use the site can automatically follow Ripple's updates to the recommended set of validators, in lockstep.
    • In case you're curious, the validator list site publishes cryptographically signed recommendations of validators, so it's not easy to impersonate. And rippled caches the data it gets from the site, so the XRP Ledger won't go down even if is down for a while. (It might be tough to bring new rippled servers online while is down, but I think there are some protections against that, too.)
  2. Update the site and the existing validators to use validator tokens instead of master validator secret keys.
    • This adds security to the existing validators. By using tokens, that Ripple can keep the master validator keys offline and periodically rotate the tokens, for example if an operations engineer who might've had access to the config files leaves the company.
  3. Update the site to add 16 new Ripple-controlled validators to the existing 5.
    • The main reason for this is so that any new individual validator isn't too large a slice of the pie.
  4. Add new third-party validators. For every two third-party validators, Ripple will remove a Ripple-controlled validator from the recommended list.
    • This will probably occur gradually over the course of 2018 and beyond.
  5. Eventually, as the size of the network has grown, Ripple will encourage others to run validator list sites similar to As long as the lists published on the different sites have sufficient overlap, servers using any list won't fork away from each other.
  6. The "Secret Future Stuff" I alluded to, which may also occur before or as part of step 5.


Popular posts from this blog

Several possible attacking modes on XRP ledger

How to file crypto tax for free