The XLS-86 Firewall is an XRP Ledger amendment that lets account owners set time-based and value-limited controls plus a whitelist to block unauthorized outgoing transactions. It reduces losses from private-key compromise and requires validator consensus to activate on the XRP Ledger.
-
XLS-86 Firewall adds time/value limits and whitelists to outgoing transactions on the XRP Ledger.
-
Amendments like XLS-86 require >80% validator support for two weeks to pass into rippled releases.
-
Discussion began November 2024; Vet (a dUNL validator) confirmed development and potential rollout steps.
XLS-86 Firewall: XRP Ledger amendment adding time/value limits and whitelists to protect accounts — track validator voting and update wallets when approved.
What is the XLS-86 Firewall?
XLS-86 Firewall is an XRP Ledger amendment proposal that introduces configurable, time-based and value-limited safeguards on outgoing transactions. It lets account owners define limits and a whitelist so that, even if a private key is compromised, attackers cannot immediately drain funds.
How does the XRP Ledger firewall work?
The firewall works by enforcing transaction constraints at the ledger level. Account owners can set daily or per-transaction caps and designate trusted accounts that bypass the firewall. If an unauthorized transaction exceeds set limits, the ledger rejects it until the owner intervenes.
In plain terms, the firewall creates a delay and threshold-based safety net around outgoing payments and token transfers, which complements multisig protections and wallet-level security.
More on firewall amendment
“Firewall” is a security feature that allows account owners to configure time-based, value-limited safeguards on outgoing transactions. This ensures that, even if a private key is compromised, an attacker cannot immediately drain the account, giving the owner time to secure their assets.
The feature includes a whitelist mechanism to allow only trusted accounts to bypass the firewall. That makes the feature useful for retail users and small enterprises and enhances multisig protection by adding an additional ledger-level control.
Discussions on the firewall amendment began in November 2024. Vet, a dUNL validator on the XRPL, publicly indicated development progress and framed the change as a potential endgame for common scam vectors targeting outgoing transfers.
What’s next?
The XRP Ledger amendment process requires validators to upgrade rippled and vote. If an amendment gains more than 80% support for two consecutive weeks, it becomes enabled in subsequent ledger versions.
The next rippled release is expected to bundle XLS-86 code if consensus thresholds are met. Network participants should watch validator voting tallies and rippled release notes for exact activation dates.
Operationally, wallets and custodial services will need to integrate firewall settings into their user interfaces to give account owners practical control once the amendment is activated.
Frequently Asked Questions
Will XLS-86 prevent all scams?
XLS-86 reduces risk from unauthorized outgoing transactions by enforcing limits and whitelists, but it does not replace strong key management or multisig. It is an additional ledger-level control that mitigates common drain scenarios.
How do validators approve amendments on the XRP Ledger?
Validators vote by running updated rippled software and signaling support. An amendment passes when >80% of validator voting weight supports it for two weeks; the code then takes effect in future ledgers.
Key Takeaways
- XLS-86 strengthens account security: Adds ledger-level time/value limits and whitelists to outgoing transactions.
- Activation requires validator consensus: Amendments need >80% support for two weeks to be enabled.
- Prepare wallets and users: Monitor votes, update rippled/wallet software, and configure firewall settings when available.
Conclusion
The XLS-86 Firewall is a significant XRP Ledger amendment aimed at reducing losses from private-key compromises by enforcing time-based, value-limited outgoing controls and a whitelist mechanism. COINOTAG will continue to follow validator voting and rippled releases as the amendment progresses; users and wallet providers should prepare to adopt the new settings when activated.
