Eltoo (LN-Symmetry)

Eltoo, also called LN-Symmetry, is a proposed replacement for the Lightning Network's channel-update mechanism in which any later channel state can directly override any earlier one. Today's channels rely on a penalty system: if a peer broadcasts an outdated state, the counterparty can claim the entire channel balance as punishment. Eltoo removes the need for that punishment, making channels simpler and far safer to back up and recover — but it is not yet possible on Bitcoin, because it depends on a consensus change that has not been activated.

From penalties to simple replacement

Under eltoo, every state is numbered, and a newer state transaction can spend and supersede an older one regardless of which stale state was published. Broadcasting an old state is therefore harmless beyond wasting a little fee, because the honest peer simply attaches the latest state on top and settles from there. Nodes only need to store the most recent state rather than the full history of revocation secrets, which is a large win for storage-constrained devices and for the general safety of backups: a node restored from an old backup under eltoo cannot accidentally destroy itself the way the penalty model punishes any mistaken rebroadcast today.

The missing Bitcoin upgrade

Eltoo depends on a new signature-hashing mode, SIGHASH_ANYPREVOUT, defined in BIP 118. This lets a signature remain valid even if the exact transaction it spends changes — a capability eltoo calls rebinding, and it is precisely what allows a later state to bind onto any earlier one. As of 2026, SIGHASH_ANYPREVOUT has not been activated on Bitcoin, so eltoo remains a proposal rather than a deployed feature. It is worth stressing that this is a genuine consensus prerequisite: no amount of wallet engineering can ship eltoo until the base layer gains the sighash mode, which itself would build on the Taproot upgrade that is already live today.

What it would unlock beyond simpler channels

The penalty-free design does more than tidy up two-party channels. It would make multiparty constructions such as channel factories considerably easier, because participants no longer have to police one another with punishment transactions, and coordinating updates among many peers stops being a minefield of mutually assured destruction. That in turn matters for scaling: factories let a group share the cost of a single on-chain transaction while opening and rebalancing many channels among themselves off-chain. For anyone thinking about how Lightning serves millions of self-custodial users without a proportional flood of on-chain footprint, eltoo's symmetry is one of the cleaner paths, which is a large part of why the proposal keeps drawing attention despite the missing base-layer piece. Symmetry also simplifies the mental model for developers, since one shared state layout replaces the asymmetric pair of commitment transactions that today's channels maintain per side, cutting down the surface area where subtle bugs can hide in wallet implementations.

Why sovereign operators are watching it

Eltoo reduces the urgency of always-online monitoring by services like a watchtower, since an honest node that comes back online late can still respond with its latest state instead of losing everything to a penalty window — though watchtowers and anchor outputs would still help ensure that state confirms under fee pressure. For the sovereign operator running channels on modest, sometimes-offline hardware, that shift from adversarial punishment to simple replacement is exactly the kind of robustness that makes self-hosting Lightning less nerve-wracking. Until BIP 118 activates, though, it stays firmly in the column of promising future upgrades, and every payment channel in operation today still uses the penalty model it aims to retire. That gap between a clean design and a live feature is itself instructive: it shows how much of Lightning's future robustness is gated on deliberate, conservative changes to Bitcoin's base layer, and why sovereign operators track base-layer proposals as closely as they track their own node software.