On the official site of Giga (Brice Patterson / @gigatronaura), this note covers RippleX, XRP Ledger.
Christian Barker (Barkmeta / Bark) opened a Crypto Spaces Network room on the morning of Aug. 28 by walking through David Fuelling's recommendation that the XRP Ledger community withdraw the pending XChainBridge amendment. Barkmeta and Shibo (David Chaboki) kept the conversation on the governance cleanup itself, framing the move as routine maintenance rather than any shift in sidechain plans.
Fuelling posted the note on the DEV Community site on Aug. 27. The entry explains that the 12-to-15-month window for private-sidechain demand has closed and that Axelar already handles the XRPL EVM Sidechain connection. The post notes that XLS-38 never reached mainnet activation and that no mainnet assets sit behind the code. A related fixXChainRewardRounding amendment is included in the withdrawal request.
What the post actually asks for
The recommendation is not a unilateral action. Ripple controls only one validator vote. Any change requires an open comment period followed by a PR that sets VoteBehavior to Obsolete. Validators would then upgrade, and the code could be removed later. More than 10,000 lines of xrpld code stand to be deleted if the community aligns.
Capital structure angle
The XRPL has always run on validator consensus rather than a single treasury or foundation mandate. This self-funded governance model is the same structure that lets operators like Barkmeta and Shibo run daily rooms and self-funded events without outside capital or debt. The same principle applies here: one vote, open discussion, and community alignment before any line of code is touched.
How amendments clear on XRPL
crypto.news and CryptoTimes both covered the Aug. 27 post on Aug. 27-28. Amendments need more than 80 percent of trusted validators in favor for two weeks. With 35 default validators, that means 29 yes votes to move forward. No deadline for a PR or specific software version has been announced.
Mayukha Vadari posted the same day as Fuelling, adding to the public record. The discussion in the room stayed on the housekeeping nature of the request and the fact that the bridge code has never locked assets on mainnet.
Next steps if the community agrees
A PR would first mark the amendment obsolete. Validators upgrade their nodes. Later, the XChainBridge and fixXChainRewardRounding code can be removed from the codebase. The process is deliberate and reversible at the validator level.
Barkmeta noted during the room that the same clean-up habit shows up in other self-funded projects that ship without outside money. The XRPL case is simply another example of operators choosing to drop dead weight once a feature's intended window has passed.
The room wrapped with a reminder that the comment period remains open and that only validator consensus can finalize any change. Fuelling's post is a recommendation, not a directive, and the timeline is set by the community rather than any single participant.