Wietse Wind, the top developer building the XRP Ledger (XRPL), has raised a debate regarding modifications to the protocol. Developers argued that audits alone are not enough.
XRPL developers ask for improved fix testing
Vice style emphasized Via X’s post that XRPL fixes need better testing. Essentially, developers are urging XRPL validators to stop treating protocol fixes as just updates.
In particular, amendments are new features or suggestions for the XRP Ledger, such as adding or improving transaction types. Publication requires at least 80% approval from trusted validators via voting. Once activated, it applies permanently to the entire network.
In his post, Wietse Wind pointed out three common but insufficient testing methods for testing XRPL amendments. Developers said that audits, hackathons, and development tests are not enough to determine the safety of XRPL modifications.
In case anyone is wondering about my rant* about XRPL fixes needing better testing…
No, hackathons are not enough
No, auditing alone is not enough
No, developer testing alone is not enoughI combined them all and repeated them several times.
There is no “Yolo vote”. No “I believe it’s okay, because…” https://t.co/cvhSLyYMxE
— White Winds – à She Xaman® + XRPL + Xhau (@VietsWind) November 3, 2025
XRPL developers say they “combined all of that and did several iterations.” This means audits, hackathons, and development testing are all needed, he sternly reiterated.
He went on to warn validators against voting “yes” on an amendment just because it’s cool or has support from community members.
Wind’s statement aims to prioritize the security of the XRP Ledger. Importantly, one bad fix can break the network, enable exploits, or lock up funds.
Check out the latest XRPL fixes
Meanwhile, Wietse Wind recently expressed excitement about the upcoming XRP Ledger feature, Batch (XLS-56). This feature allows you to bundle multiple transactions into one batch and process them all together.
However, Wind pointed out that: This may occur with batch functions assignment. Lack of understanding can lead to a setback in support.
In contrast, Uphold executives praised the new amendmenta multi-purpose token (MPT) standard to solve regulatory compliance issues.
To emphasize, the new token standard will allow financial institutions such as banks and asset managers to issue fungible tokens. As a result, banks will be able to issue stablecoins, bonds, or tokenized real-world assets directly on XRPL.
Additionally, Vet, a popular XRPL validator, claimed: Voted a veto on the token escrow amendment bill. He argued that it would be wiser to wait until token escrow is fixed to properly support multi-purpose tokens.
