Not a network amendmentTier BUpcoming standardsSpec: Draft
Firewall XLS-86
A draft for an outgoing destination allowlist, counterparty approval, a backup account, and an account-wide fee limit. This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.
Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder
- Network status
- Not a network amendment
- XLS
- XLS-86
- Spec status
- Draft
- Spec revision
- Sep 19, 2025
What does this XLS propose?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
Technical details: transactions, fields, codes and invariants
Transactions
- FirewallSet
- FirewallDelete
- WithdrawPreauth
- all outgoing transactions subject to MaxFee checks
Ledger objects
- Firewall (LedgerEntryType 0x0085)
- WithdrawPreauth (LedgerEntryType 0x0856)
Fields and flags
- FirewallID / Counterparty / Backup
- CounterpartySignature
- MaxFee
- Authorize / Unauthorize
- Firewall key space 0x0046 / WithdrawPreauth key space 0x0047
Result codes
- tefFIREWALL_BLOCK
- temDISABLED / temINVALID_FLAG / temMALFORMED
- temBAD_SIGNATURE / temINVALID_ACCOUNT_ID / temCANNOT_PREAUTH_SELF
- tecDUPLICATE / tecNO_DST / tecNO_TARGET / tecNO_ENTRY
- tecNO_PERMISSION / tecINSUFFICIENT_RESERVE / tecDIR_FULL
How does this proposal relate to others?
Every direct relationship has a type, an explanation and a primary source.
No direct family relationship supported by reliable evidence is recorded for this proposal. The page deliberately avoids showing an assumed connection.
What happens next for this proposal?
Where does it sit within its amendment family?
Firewall has no amendment family with other members on this site, so there is no progression to show here.