Senior Ripple Engineer has it It was cleared air As I've been talking about rusting and rewriting the XRP ledger (XRPL) recently trigger Concerns among XRP holders.
In particular, these concerns I picked it up After Ripple's Chief Technology Officer, David Schwartzdiscussed ideas during the developers Boot camp. For context, the original XRPL architects, including Schwartz, have a great advantage when writing networks using C++ and pivoting to rust.
After community figure Eri highlighted this lead in a recent post, certain members of the community questioned whether such changes could affect XRP holdings or destroy the XRPL network.
According to her, the rewrite only includes the language used to build the protocol, and data stored on the blockchain or how network It works. she stress That user will continue to retain XRP and the developer will continue to building In XRPL, always do the same I have it.
Cali I explained it The process defines how the system currently functions, Ripples Individual modules. From there, developers can gradually rewrite each part of the rust, but the transaction engine could remain in C++.
Why use rust?
In particular, she addressed this issue. rear Schwartz remarks With XRPL Core Dev Boot camp. Someone from XRPL Commons, a nonprofit organization that supports XRPL Growth asks Schwartz why Ripple didn't move forward by rewriting the rusty XRPL now.
For beginners, rust is known for its speed and reliability. that I'll give it Developers have low-level control over memory while preventing common bugs that plague older languages Like C and C++.
This makes Rust highly compatible with blockchain software. Especially like a blockchain Solana, suiand the polka dots run with rust. Rewriting core XRPL software with Rust helps improve security, speed and ease of infrastructure maintenance.
Ripple CTO has confirmed Ripple that is already considering ideas
In response to the question, Schwartz said Ripple was already considering a shift. He confirmed his role in those discussions. Schwartz explained that Ripple wants to break down the architecture of XRPL into smaller, more manageable parts, especially transaction engines, so it can ultimately run inside a VM.
Especially this setup It allows you to recreate it Part of systems in other languages, such as rust Rewrite everything at once.
The big challenges of payment engines
However, Schwartz pointed out that one major challenge lies in the payment engine. He said that part of the work relies on mathematics that don't always produce the same results when executed on different orders, making accurate replicating in another language difficult.
For example, floating point calculations It may lead to Small differences depending on the order of addition and subtraction.
He explained that it is important to make XRPL more modular and flexible. “You can imagine a situation where a transaction engine is kind of compartmentalized and running on a VM. I want to make my code more modular.”
Schwartz also revealed that Ripples I have it It's begun Review of proposals from interested external companies help This work. He said the team is deciding what to do first and how to move forward. He also added that he would like to create formal specifications for each part of the system, making it easier to create alternative versions where everything behaves the same.
Despite the complexity, Schwartz believes there is some advantage from moving the idea forward. “So, yeah, me absolutely I think that's a good thing. It's not easy at all. ”
