Updated Ripple/XRP stats

[hammertoe]

• Renamed Ripple to XRP
• Updated stats for XRP
• Updated notes on consensus process and reasoning

[DZGoldman]

@hammertoe thanks, a few things:

• Can you point me to a source for the 7/26 number? I followed the links on the validator list sites, but couldn't find it.
• I'd rather not tweek the names of the classes/files because they're set to correspond with a few APIs; I do think it makes sense to list it as XRP, so the only thing that needs be changed is the name key in the xml file (beyond that, it'll only say ripple within the codebase, which I think is fine)
• Can you justify/explain "consensus_distribution: 0"?
• I've edited the text to pare it down and make it a bit less tendentious, let me know what you think:

By default, rippled comes configured to point to a list of validators (UNL)
at https://vl.ripple.com (https://github.com/ripple/rippled/blob/develop/cfg/validators-example.txt);. currently Ripple control 7/26 of the validators (27%).
Node operators can edit the config file to change this or choose their own
list of validators; this list must contain a minimum overlap of 41% with the UNLs of the rest of the
network.
``

[hammertoe]

@hammertoe thanks, a few things:

• Can you point me to a source for the 7/26 number? I followed the links on the validator list sites, but couldn't find it.

https://minivalist.cinn.app/

It has changed even more since my PR and is now 7/28

• I'd rather not tweek the names of the classes/files because they're set to correspond with a few APIs; I do think it makes sense to list it as XRP, so the only thing that needs be changed is the name key in the xml file (beyond that, it'll only say ripple within the codebase, which I think is fine)

Sure , that sounds reasonable

• Can you justify/explain "consensus_distribution: 0"?

If I understand this correctly, according to the source code, this figure is "# of entities in control of >50% of voting/mining power". On the XRP ledger there are 0 entities with > 50% of the voting/mining power.

• I've edited the text to pare it down and make it a bit less tendentious, let me know what you think:

By default, rippled comes configured to point to a list of validators (UNL)
at https://vl.ripple.com (https://github.com/ripple/rippled/blob/develop/cfg/validators-example.txt);. currently Ripple control 7/26 of the validators (27%).
Node operators can edit the config file to change this or choose their own
list of validators; this list must contain a minimum overlap of 41% with the UNLs of the rest of the
network.
``

Yes, that is fine by me.

[hammertoe]

I have just realised I think I misunderstood the consensus distribution metric above, and it is "the number of entities required to collude to gain over 50% of the hashrate/control"? In this case you would say there are currently 22 different entities in Ripple's default UNL whom all vote on transaction order, so you would need to control/coerce 11 of them to control 50%. However with XRP you need 80% majority vote in order to control the order, so it would be 80% of 22 so the number would be 18.