- Ripple CTO warns proposed XRPL transaction ordering could increase risks.
- Validators rejected timestamp ordering because network propagation differs between nodes.
- Sequencing flags may prioritize transactions but expose users to manipulation.
Ripple CTO emeritus David Schwartz has warned that a proposed XRP Ledger transaction ordering method could create new security risks. According to comments shared on X, Schwartz said one suggested approach may unintentionally make front-running and sandwich attacks easier for some users.
The discussion follows Schwartz’s recently proposed transaction reservation scheme. That proposal seeks to reserve transaction slots before they become publicly visible. As a result, transactions could execute before later submissions gain an opportunity to interfere with them.
During the conversation, an X user suggested assigning timestamps down to the second. Under that idea, earlier transactions would automatically receive priority during processing. The suggestion aimed to simplify transaction ordering across the XRP Ledger network.
However, Ripple software engineer Mayukha Vadari explained why that solution would not work. According to comments shared on X, validator nodes receive transactions at different times. Transactions travel through a distributed peer-to-peer network. Therefore, timestamps cannot guarantee identical ordering across every validator.
Also Read: BlackRock Bitcoin ETF Sees $300M Outflows as Institutions Rotate Capital in June
Consensus ordering comes with trade-offs
According to Schwartz, the closest practical alternative involves consensus-based transaction ordering. Under that model, validators would vote on transaction order during the consensus process.
However, Schwartz explained that the method carries significant drawbacks. Validators would need to agree on more information during every consensus round. Consequently, the additional workload would slow the network’s consensus process and increase complexity.
Schwartz also outlined another possible option. Users could pay an additional fee to attach a sequencing flag to selected transactions. Those flagged transactions would receive relay priority within the same ledger before standard transactions.
Security concerns remain a major obstacle
Despite outlining the proposal, Schwartz said he does not support implementing the sequencing flag. According to his comments on X, the feature could make front-running and sandwich attacks easier against transactions without the flag.
Attackers could prioritize flagged transactions while ordinary users avoid paying the additional fee. Consequently, the proposed solution could weaken fairness instead of strengthening network protection.
In conclusion, the discussion shows Ripple developers continue evaluating improvements to XRP Ledger transaction processing. Schwartz believes future changes should strengthen security without slowing consensus or introducing new attack opportunities.
Also Read: June Crypto Hacks Reach $75.9M as Humanity Protocol Accounts for Biggest Security Breach
