Overview
- RippleX said on June 8 that it is working with Common Prefix to apply formal verification to the Single Asset Vault (XLS-65) and the Lending Protocol (XLS-66) before any Mainnet activation.
- The teams build abstract, machine-checkable models and use those models to run oracles that compare outputs with the xrpld C++ implementation so discrepancies are flagged automatically.
- Modeling has already exposed edge cases that conventional unit and integration tests missed, especially around numerical precision and sequential accounting that can compound across transactions.
- Although amendment support for XLS-65 and XLS-66 was added in XRPL v3.1.x, the features cannot go live without the required validator approval and the network is preparing an xrpld v3.2.0 release targeted for mid-June.
- The move responds to past risks such as a flagged Batch-transaction flaw and aims to raise confidence in protocol-level DeFi, but formal proofs only guarantee the properties encoded in a model and do not rule out all possible vulnerabilities.