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 (vl.ripple.com). 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 vl.ripple.com is down for a while. (It might be tough to bring new rippled servers online while vl.ripple.com 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 vl.ripple.com. 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.

Comments

Post a Comment

Popular posts from this blog

portage-2.2 preserve-libs FEATURES explained

Maybe I am not the right person to write about it. But I felt the necessity to write about it. So I will just write something about preserve-libs, leaving other FEATURES to more competent people. Portage-2.2 has already entered unstable tree. Many people has started using it. It has many new features, like preserve-libs, sets, license filter and so on. Please check README and RELEASE-NOTES for a complete list. I will only talk about preserve-libs. To understand why we need it, we have to know some background information. First of all, applications are not built from scratch. Any non trivial apps use lot of libraries. In GNU/Linux, most of them are shared libraries, i.e. .so files. You can use `ldd /usr/bin/mplayer` to check what shared libraries an app has been linked to, replace mplayer to whatever program you'd like to check. Shared libraries have versions. E.g. /usr/lib/libavformat.so.51, here 51 denotes its version. After upgrading, the version number may change. E.g. /usr/lib/...
Read more

Send $SGB (Songbird) to another wallet using a script

You need nodejs and web3 to run it:  const Web3 = require('web3'); // Variables definition const privKey = '8xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2'; // Genesis private key const addressFrom = '0xAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'; const addressTo = '0xBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB'; const web3 = new Web3('https://songbird.towolabs.com/rpc'); // Create transaction const deploy = async () => { console.log( `Attempting to make transaction from ${addressFrom} to ${addressTo}` ); const createTransaction = await web3.eth.accounts.signTransaction( { from: addressFrom, to: addressTo, value: web3.utils.toWei('1', 'ether'), // Send 1 SGB. 'ether' is not a typo here. gasPrice: web3.utils.toWei('225', 'Gwei'), gas: '21000', }, privKey ); // Deploy transaction const createR...
Read more

The diff between the original SEC complaint against Ripple and the amended one

--- original.txt 2021-02-18 18:32:43.171832036 -0800 +++ amended.txt 2021-02-18 18:32:29.103735165 -0800 @@ -1,4 +1,4 @@ -Case 1:20-cv-10832 Document 4 Filed 12/22/20 Page 1 of 71 +Case 1:20-cv-10832-AT Document 46 Filed 02/18/21 Page 1 of 79 Richard Best Kristina Littman @@ -34,9 +34,9 @@ : ------------------------------------------------------------------------x -20 Civ. 10832 +20 Civ. 10832 (AT) ECF Case -Complaint +First Amended Complaint Jury Trial Demanded Plaintiff Securities and Exchange Commission (the “SEC”), for its Complaint against @@ -53,7 +53,7 @@ required by the federal securities laws, and no exemption from this requirement applied. 1 -Case 1:20-cv-10832 Document 4 Filed 12/22/20 Page 2 of 71 +Case 1:20-cv-10832-AT Document 46 Filed 02/18/21 Page 2 of 79 2. @@ -103,7 +103,7 @@ 2 -Case 1:20-cv-10832 Document 4 Filed 12/22/20 Page 3 of 71 +Case 1:20-cv-10832-AT Document 46 Filed 02/18/21 Page 3 of 79 VIOLATIONS 9. @@ -150,...
Read more