Let me quickly go through how #XRPL performs and #scales on these metrics:
βΆοΈ Scale up "vertically"
βΆοΈ Scale out "horizontally"
βΆοΈ High volume & High value TX
βΆοΈ High value & Low speed
[2/17] π Asynchronous TX speedβScale up "vertically"
In contrast to #DAG-based systems, which operate in "chaotic order" and execute transactions in parallel, the #XRPL validates transactions in canonical transaction orderβone Ledger at a time.
β The approach for #DLT/#Blockchain-based systems such as #XRPL:
βοΈ "Payment Channels"
π§ It's a sophisticated feature for transmitting "asynchronous" #XRP#payments that may be broken into extremely small amounts and paid in total order afterwards.
. . .
2β£ With "#PaymentChannels":
Alice is continually wrapping up new toys (#TX) and NOT delivering them over to @bob_way (async. authorized claim with a single validated #TX), while also reminding him:
"They are yours whenever you want them π" (redeem a claim)
. . .
This restriction is mostly determined by the speed of the participants' #hardware and the complexity of the #signature#algorithms.
. . .
[8/17] . . .
In 2011, research proved the capacity to produce over #Ed25519 100,000 #signatures per second and verify over 70,000 per second on commodity #hardware.
If adding #servers isn't enough to #scale out enough to handle all of the #transactions on the #XRPL itself, there's always the possibility of spinning up a new #sidechain with purpose-fit rules if the #mainchain becomes overloaded.
β We've prev. addressed how the #XRPL will manage large volume load, but how will it handle liquidity issues for high value #TX when the trading-pair is not liquid enough?
The solution proposed for this specific problem:
βΆοΈ #AMM
. . .
[14/17] . . .
The [A]utomated[M]arket[M]aker (#XLS30d) liquidity pools enable #liquidity provisioning without the need of smart-contracts, further enhancing the #CLOB-based #XRPL#DEX.
[16/17] βοΈ As you can see, there are numerous methods to scale up and out, including adding #servers, boosting #CPU power, adding #sidechains, or leveraging #XRPL features such as #escrows and #payment-channels to meet transaction demand without overburdening the #XRPLedger.
[17/17] Thank you to everyone who took the time to read this lengthy topic β€οΈ
If you enjoyed the thread, please follow me: @krippenreiter
Please feel free to contribute by sharing here π
The TL;DR is that pDomains are restricted environments on the XRPL that let users with permission use certain functions within the domain, like a DEX, in case the user owns the correct credentials. π§
[1/π§΅] The bullrun seems to be just around the corner, and everyone is teasing us with yield and XRPFi protocols. π§
Regardless of whether you decide to hold or sell...
Let's take a look at "Lending" and check if it's worth it. π
[2/14] β 1β£ Money Markets β
Before we do just that, let's quickly clarify a specific word first.
Behind the terms "Lending" and "Borrowing" actually hides another term that you will see from time to time:
πΈ Money Markets
[3/14] β 2β£ Money Markets β
Besides AMMs, lending is currently the most important pillar for on-chain DeFi, as it removes the middleman in the pooling, management, and lending of funds.
The goal? π€¨
Positive yield or in other words, interest on the liquidity you provide.
[1/π§΅] A MASSIVE attack on the JavaScript ecosystem is currently underway. βΉοΈ
Since JavaScript is at the heart of what we use every day to browse the internet, you MUST be extra vigilant.
Let's take a look at a possible solution for the XRP ecosystem. ππ§΅
[2/13] β 1β£ First things first β
Although the entire JavaScript ecosystem is at risk, the malware appears to be targeting only a few blockchain ecosystems, based on the addresses it uses to steal funds:
βΌοΈ At risk π
[3/13] β 2β£ First things first β
The reason this is such a big deal is because of the sheer volume of weekly downloads of the maliciously patched packages.
[1/π§΅] You've probably heard about new yield opportunities with XRP that promise a return of around 20% APY. π§
How much truth is there to this, and what happens if you actually connect to @moremarketsxyz and deposit funds? π
[2/14] β 1β£ First things first β
π I want you to repeat after me:
"I will not deposit all my XRP into completely new DeFi protocols right after their launch, no matter the yield"
[3/14] β 2β£ First things first β
When you join any DeFi protocol, start with very small amounts (e.g., 1 XRP) to get a feel for how things work, and try to regularly withdraw everything to test whether you can realize your profits with the protocol or not. π
[1/π§΅] What's still upcoming and in the pipeline for the XRP Ledger? π§
My attempt to summarize what the brilliant @aanchalmalhotre "casually" laid out in a 25-minute talk at XRPL Apex this year. π
[2/15] β 1β£ Key-Challenges β
Privacy and compliance are at odds with each other, and balance is key.
A lot of what the TradFi world is used to and expects still doesn't exist or is purposefully different in blockchains, like transparent transactions or low confidentiality.
[3/15] β 2β£ Key-Challenges β
Institutions also expect their on-chain operations, aka transactions, to be highly customizable and controllable because of factors like internal risk management.
π They expect the XRPL to be programmable for their dedicated policies.
With all these new integrations and partnerships, I bet you are pretty much overwhelmed by all the alien-like jargon. π€¨
A little vocabulary crash course ahead π
[2/20] β 1β£ Overview β
What just happened today is nothing less than the complete onboarding of the XRPL to the vast and entire web3 blockchain ecosystem (+ Bridging protocols and available liquidity).
π All via the XRPLEVM sidechain, Axelar and @squidrouter.
[3/20] β 2β£ Overview β
What does this mean in practice? π§
πΈ New tokens on the XRPL DEX (bridged by @axelar)
πΈ Literal (and easy) any-to-any swaps (via Squid)
πΈ Liquidity from the entire web3 ecosystem (via CORAL)
πΈ Bridged XRP accessible on 80+ chains (through XRPLEVM)