XRP Hidden Ledger - Alternative Theory

[Guest1]

I know that some form of a hidden ledger theory was previously known to the community and many people told me it was debunked.

I have an alternative theory and it would be appreciated if you @BobWay could have a read and let me know if it makes sense or if it's not possible/feasible.

------------------------------------------------------------------------------------------------------------------------------------------------------

How Ripple can create (or possibly already have created) a hidden ledger, and subsequently turn the switch on to redirect the volume to the public ledger.

Step 1 - Create another copy of XRP Ledger Test Net, henceforth referred to as 'Hidden Ledger'
Current Test Net address: https://s.altnet.rippletest.net:51234 
Example Hidden Ledger address: https://s.altnet.xrphiddenledger.net:51234 (just an example to illustrate my point - no dns entry for this actually exists)



Step 2 - Make a educated guess about the total circulating supply of XRP:
- Take total 99.xx billion supply
- Deduct escrowed XRPs
- Deduct sum of XRPs in wallets that have been reasonably dormant (e.g. 80%+ of wallet balance not traded) for the last 1 year or longer

Step 3 - In the Hidden Ledger, limit the total number of XRPs to the total circulating supply of XRP from Step 2 above, in order to reasonably simulate the short-term real-world XRP supply and price dynamics.

Step 4 – Mimick the total number of UNLs to the current number in the public XRP Ledger by launching additional computer instances in the cloud that are accessible only by Ripple. Configure these servers as close to real-world as possible.

Step 5 - Provide the Hidden Ledger address from Step 1 to all the current and prospective partners (including NDA partners), and provide them instructions on how to direct daily transactional volumes to this Hidden Ledger for testing.

Step 6 (continued) Such information may contain API related details such as the Websocket Server address, format of the JSON message (e.g. {wallet address: '', transaction type: '', etc}, and API function names to send transactions to the Hidden Ledger

Step 7 – Ensure that access to the Hidden Ledger is confined to these institutions only by making use of firewall / security groups and network access control lists (NACLs) that only allow specific IP addresses to connect.

Step 8 – Set up stress test by requesting all participants to direct ALL volumes to Hidden Ledger over 24-48 hours. e.g. DTCC, CLS, ACI, TARGET2, as well as central banks, R3 and Hyperledger. Combined volumes may potentially be in the order of USD 20+ trillion PER DAY.

Step 9 - Stress test the Hidden Ledger environment throughput (max 1500 TPS) and observe the impact on the XRP price when the volume is at its peak.

Step 10 – Tweak the price of XRP (e.g. $500 - $1500) as well as the frequency of transactions (e.g. frequency of bulk settlements) such that the price of XRP is stable during such stress tests. This gives an idea of the final value of XRP required for total volume.

Step 11 – Perform such stress test from Step 9 and Step 10 for a single participant only and observe the price impact on XRP. Do this for each participant.

Step 12 – Perform any additional tests in the Hidden Ledger such as the impact of including a test version of Cobalt or any other tests as deemed necessary

Step 13 – Make sure to keep the Hidden Ledger private so that such tests are not observable to the retail market at all times at all costs.

Step 14 – Provide the Hidden Ledger participants with the address of the real-world public XRP Ledger ('wss://s1.ripple.com:443') and, if necessary, provide instructions on how to change the address from the Hidden Ledger to the public XRP ledger.

Step 15 – Perform a gradual switch over from the Hidden Ledger to the Public Ledger by asking each participant to change the address from the former to the latter, while closely observing the actual vs expected impact on the retail market dynamics and the price of XRP.