The current discussions around XRP Ledger’s (XRPL) future have been reignited by insights from J. Ayo Akinyele, Ripple 
$1 X’s Head of Engineering, and David Schwartz, who is preparing to step down from his role as CTO. While Akinyele sees potential in a native staking model amid increasing institutional use of XRP, Schwartz acknowledges its technical allure but questions its near-term feasibility.
XRP Ledger’s Staking Dispute Surfaces
Akinyele emphasizes that XRP’s function extends beyond value transfer. XRP is expanding into areas like tokenization, real-time payments, DATs, and even DeFi with the first approved spot XRP ETF in the U.S. This expansion necessitates the consideration of new incentive models and network participation strategies. To implement native staking on XRPL, Akinyele outlines the need for a sustainable reward source and a fair distribution mechanism.
Currently, the system operates on a model where transaction fees are burned, and validators’ reliability is performance-based. Akinyele suggests that should staking be integrated, part of these fees might be redirected to a rewards pool. He stresses the importance of carefully designing the distribution of incentives and the impact on governance.
Additionally, Akinyele points out that ecosystem projects like Flare, Doppler Finance, Axelar, and MoreMarkets are already experimenting with staking-like mechanisms, indicating that the conceptual groundwork is underway.
Technical Insights from David Schwartz
In a statement on his social media account, Schwartz mentions the evolution of his thoughts on governance and consensus models, asserting that discussing new designs suited to today’s DeFi ecosystem is natural. He urges a reconsideration of the model developed in 2012 to align with the current smart contract focus.
Schwartz shares two technical scenarios discussed within the community. The first features a two-tier consensus system where a small stake-based internal validator group progresses the ledger, while the external layer handles fees, updates, and oversight. The second scenario maintains the existing model with zero-knowledge proofs funded by transaction fees to validate smart contract executions. This approach might allow nodes to perform verification without directly executing contracts.
However, Schwartz emphasizes that while both approaches are technically captivating, they are unrealistic in the short term. The focus is on raising awareness about which values should be preserved and which new capabilities might be integrated harmoniously into XRPL’s future.
