of $XRP Amendments to the Ledger Lending Protocol are currently under vote. In January, we released version 3.1.0, the reference server implementation of rippled. $XRP The Ledger Protocol, which includes a single asset vault and lending protocol, has been released.
However, according to XRPScan, voting on the lending protocol appeared to be moving steadily forward, with only 17.14% achieving consensus. This is 62.86% away from the 80% threshold required for a fix to enter the activation stage.
of $XRP Ledger adjustment systems use a consensus process to approve changes that affect the processing of transactions on the books. $XRP ledger. For an amendment to pass, it must receive at least 80% support within two weeks.
For lending protocols, a minimum of 62.86% validator support is required to achieve majority.
What comes next?
In addition to amendments to the lending protocols, the XLS-65 specification introduces that a single asset vault is now monitored. Single Asset Custodian is slowly gaining support and currently has a consensus of 22.85%.
A serious bug was recently discovered in the proposed XRPL batch fix. This may explain the seemingly slow, if unhurried, response of the vote as other amendments are tested.
In light of batch fix bugs, Ripple has indicated that it is raising the bar for fix security.
JA Akinyele, head of engineering at RippleX, said Ripple is working on formal validation of high-risk components on its ledger in the long term.
This means proving the safety of critical components, modeling corrective behavior before activation, standardizing validation requirements for consensus-critical code, and integrating formal methods into the XRPL SDLC (from XLS specification to code to testing).
The goal is to ensure end-to-end that XRPL modification specifications and code are not only functionally correct, but also maintain the security and safety properties defined in the ledger.
