Thread by @krippenreiter

@WKahneman 1/ Certainly one of the finest tedious rants I've heard in a long time 😉

But let me add a few more facts to your fantastic thread:
🧵👇

@WKahneman 2/ First and foremost, if you're looking for a quick way to find the first or oldest commit, often known as changes to the repository, ever recorded on XRPLF/rippled, here it is: 👇

github.com/XRPLF/rippled/…

@WKahneman 3/ You can see when the #XRPL was initially built, who was involved in the early stages, what issues were addressed, and what improvements were implemented at what point in time. 🧐

@WKahneman 4/ The "DIY and just copy the code" theory has always confused me. How on earth do you want to "clone" liquidity, active DEVs working on actual code on a regular basis, and maintain trustless decentralization as a government? 😅

@WKahneman 5/ Just a reminder: #XRPL as a medium of exchange—neutral bridge currency—only works BECAUSE it is #decentralized and eliminates the need for a middleman in the #trustless exchange of value between two parties who no longer need to trust each other.

@WKahneman 6/ When discussing Parallel Networks, it is also worth noting that "Canary Networks" exist. "#Songbird ( $SGB )" and "#Shimmer ( $SMR )" are two very promising examples. 👀

@WKahneman 7/ Canary networks are used to bring "real genuine value or skin in the game" to a #DLT that is a little more "cutting edge with features" than the "original network" in order to provide an incentive to break it. 🧐

@WKahneman 8/ Both of these #Mainnets may be subdivided further into #Testnets and #Devnets. AFAIK, the #XRPL does not yet have a canary network. 😟

@WKahneman 9/ As "state data," all 100B #XRP (the balance of each account) is correctly recorded and synced to every closed #ledger. According to the #XRPL documentation, "each instance of #rippled keeps a full copy of the ledger [...]"

@WKahneman 10/ This is why, unlike #BTC, one does not need to know the genesis closed #ledger. Because the #XRPLCP is a #BFT algorithmic variation, finality is set in stone when the ledger is validated, . . .

@WKahneman 11/ . . . as opposed to #BTC, where one must wait at least 6 blocks "depth" to be "somewhat" confident of the payment's #finality.

@WKahneman 12/ Was it ever disclosed if the "Private #Ledger" was a fork of the public #XRPL or a #sidechain?

Endgame will most likely take the shape of a #federated #sidechain, in my opinion.

@WKahneman 13/ It is not only forbidden but also impossible to issue additional #XRP out of thin air owing to "#InvariantCheck."

#Docs here:
xrpl.org/invariant-chec…

#Code here:
github.com/XRPLF/rippled/…

@WKahneman 14/ When discussing tokens, the #XRPL docs state that "all assets other than #XRP can be represented in the #XRP Ledger as #tokens."

As a result, the #token criteria do not apply to #XRP (e.g. creating new coins)

#Docs here:
xrpl.org/tokens.html

@WKahneman 15/🧵FIN

<Also heads into the Friday nite>

@WKahneman @threadreaderapp unroll