Statechain

A statechain is an off-chain protocol that lets the ownership of an entire Bitcoin UTXO move between people without an on-chain transaction. Instead of changing the coin on the blockchain, the parties change who controls the key that can spend it. This enables instant, low-cost transfers of specific coins — the UTXO itself never moves — with an on-chain transaction needed only when an owner finally withdraws to full self-custody.

The statechain entity

The protocol is coordinated by a statechain entity (SE) that co-signs alongside the current owner using a shared-key scheme: the spending key is split between the SE and the owner, so neither the SE nor any single party ever holds the complete private key. When ownership is transferred, the SE and the participants run a key-update protocol so that the new owner's share plus the SE's share can produce valid signatures, while the previous owner's share becomes useless. The elegant part is that the on-chain key never changes — the blockchain sees nothing at all. The Mercury Layer implementation refines this with blinded signing, so the SE cannot even see which coin it is helping to transfer or what the signatures it co-creates look like, meaningfully improving privacy over the original design.

The trust model, honestly stated

Statechains are trust-minimized, not trustless, and the distinction deserves plain language. The security promise depends on the SE actually deleting its old key-share material after each transfer: an SE that secretly retained every historical share could collude with a past owner to sign a spend. To bound the damage of SE failure or misbehavior, every owner holds a pre-signed, timelocked backup transaction — a unilateral exit path that sends the coin to a key only they control after the timelock matures, with each transfer's backup arranged to take precedence over earlier owners'. So the worst realistic outcomes are degraded: an unresponsive SE costs you a wait, not your coin; a dishonest SE requires collusion with a specific prior owner to hurt you. That is a very different — and for some uses, acceptable — trade-off from custodial holding.

The coin's lifecycle makes the model concrete. An owner deposits by sending a UTXO to the shared key, receiving the first backup transaction in exchange; the coin then changes hands any number of times through key updates, each transfer taking seconds and costing effectively nothing; and the story ends either with a cooperative on-chain withdrawal co-signed by the SE, or — if the SE has vanished — with the current owner broadcasting their timelocked backup and waiting out the lock. Statechain entities typically sustain themselves on small deposit or transfer fees. The whole arrangement is auditable from the outside: every promise reduces to transactions you can inspect and a timelock you can count down on your own node.

Statechains among the layers

Each off-chain system carves the design space differently. Lightning excels at streaming arbitrary amounts but requires channels, liquidity management, and online monitoring. Ark batches users through an operator with periodic on-chain rounds. Statechains transfer whole UTXOs only — you cannot send part of a coin, which suits them to moving standardized denominations, transferring a Lightning channel wholesale, or passing around a specific coin like a bearer instrument. Their virtues are immediacy, negligible cost, no liquidity constraints, and no consensus changes: statechains work on Bitcoin today, no soft fork required.

Why a sovereign Bitcoiner should care

Statechains matter as an existence proof: Bitcoin's base layer can support instant off-chain transfer of real coins with a small, auditable trust assumption and a unilateral exit. That exit path is the philosophical core — the same property D-Central looks for in every layer of the stack, from firmware you can reflash to coins you can always sweep back to keys you alone hold via self-custody. D-Central documents statechains neutrally as one of several second-layer approaches to scaling Bitcoin custody and transfer; for protocol specifics and current status, consult the Mercury Layer documentation directly.