Bitcoin anchoring
Every Sequentia block names a Bitcoin block. If Bitcoin ever drops that block, Sequentia drops every block that named it.
That one rule is why Sequentia is called a Bitcoin sidechain even though no bitcoin is ever locked, pegged or wrapped to make it work. The two chains are tied by reference, not by a deposit.
What the rule says
Each new Sequentia block carries, inside its own header, the hash and height of a Bitcoin block. A block can name the same Bitcoin block as its parent did, or a later one, never an earlier one. Since Sequentia produces a block a minute and Bitcoin one every ten, about ten Sequentia blocks in a row point at the same Bitcoin block.
When Bitcoin reorganises, which happens now and then at its tip, every Sequentia node sees it and discards the Sequentia blocks that pointed at the orphaned Bitcoin block. Their transactions go back to the waiting pool and are included again.
As long as Bitcoin does not reorganise a referenced block, no Sequentia reorganisation is possible. Sequentia’s history is exactly as stable as Bitcoin’s, and never less.
Whitepaper 5.1The anchoring rule as the whitepaper states it
Any new Sequentia block includes a reference to the hash of the header of a Bitcoin block. If the Sequentia block X references the Bitcoin block Y, the block X+1 necessarily references the hash of a Bitcoin block at a height higher or equal to Y. When Bitcoin chain reorganisations happen, Sequentia nodes discard all Sequentia blocks referencing orphaned Bitcoin blocks.
The two anchor fields (Bitcoin height and header hash) sit in the part of the Sequentia header that is hashed and signed, so a block’s anchor cannot be changed without invalidating the producer’s signature.
Whitepaper 5.3What a node checks on every block
- The header contains a Bitcoin block hash.
- The anchor height does not decrease along the chain, and if it is unchanged from the parent’s, the hash is unchanged too.
- The referenced Bitcoin block exists, sits at the claimed height, and is on the Bitcoin node’s best chain. This is the check that needs a live Bitcoin node; it is skipped when a block repeats its parent’s already-validated anchor.
Alongside this, a background task (the anchor watcher) asks the Bitcoin node for its best chain every few seconds: 5 by default, 15 on the testnet. When an anchor is no longer on that chain, the watcher invalidates the lowest affected Sequentia block and its descendants.
This is a consensus invalidation and not a local preference. Every node following the same Bitcoin chain reaches the same verdict, because Bitcoin’s best chain is the shared oracle.
The cost does not grow with the chain. A Bitcoin block that has been checked stays valid until Bitcoin reorganises, and many Sequentia blocks share one anchor, so with no reorganisation each poll costs a single request, whether the chain is a day or ten years old (section 5.4).
Specification: 03-bitcoin-anchoring.md.
What anchoring buys
Four things, each of which a stand-alone chain cannot get at any price.
1. A chain that cannot get stuck
A committee-based chain that fails to gather its quorum has no way, from the inside, to tell absent signers from slow messages, so it waits. This is why chains like Algorand and Liquid halt when a third of their signers are missing.
Sequentia has a clock outside itself. Bitcoin’s progress is an unforgeable measure of time passing, and every block already commits to it. If Bitcoin has moved on and Sequentia has not, the chain knows it is stalled and is allowed to continue with fewer signatures. See Never stuck.
2. Trades that span both chains
Normally, a trade with one leg on each of two chains has to wait a long time on both, because either chain might reorganise on its own and undo one leg while the other stands. An exchange, a bridge or a lender accepting both has to run two unrelated risk models.
With anchoring, the two chains reorganise together. “Three Bitcoin confirmations” becomes a single policy that covers both the bitcoin leg and the Sequentia leg, and a contract on Sequentia can count time in Bitcoin blocks. This is what lets real bitcoin, sitting on Bitcoin, be traded against assets on Sequentia without wrapping it. See Swap BTC for any asset.
In developmentThe one case anchoring does not close by itself, and the fix on its way
Anchoring guarantees that if the bitcoin payment is reorganised out, the Sequentia side is reorganised out with it. It does not, alone, guarantee what happens next. After such a reorganisation the Sequentia transaction returns to the waiting pool and is mined again, while a dishonest buyer could spend the same bitcoin elsewhere instead of letting the payment be mined again.
The fix removes the gap at the level of consensus. A Sequentia output can be locked so that it opens only for a spender who proves that a specific Bitcoin payment (this script, at least this amount) is in Bitcoin’s chain, and every node checks that proof against the chain’s own anchors. Then:
- the bitcoin side of a swap is an ordinary payment: no hash lock, no secret, nothing a Bitcoin wallet has to support;
- the claim on Sequentia is valid only in a block whose anchors contain the payment, so if the payment leaves Bitcoin’s history, the claim leaves Sequentia’s with it and can never be mined again;
- the seller has a refund path if the payment never arrives.
It is implemented as three tapscript opcodes, OP_INSPECTBTCPAYMENT, OP_INSPECTBTCTX and OP_CHECKANCHORHEIGHTVERIFY, together with a signing rule for the committee. Status: written and tested on a development branch, not yet merged or activated on the testnet; the wallets and SeqDEX still use hashed-timelock swaps today.
Specification: bitcoin-payment-proof.md on the feature/bitcoin-payment-proof branch.
3. Randomness nobody can bias
Each block’s producer is chosen by a lottery, and a lottery needs a seed. If the seed came from the previous Sequentia block, its producer could shuffle transactions or nudge a timestamp until the next draw favoured it.
The seed comes from the parent block’s Bitcoin anchor instead. A producer can grind a Sequentia block hash; it cannot grind Bitcoin’s proof of work.
4. Protection against rewritten history
Proof-of-stake chains share a weakness: people who used to hold stake can sell their old keys, and whoever buys enough of them can sign an alternative history. Sequentia writes checkpoints into Bitcoin and keeps a departing staker’s coins locked until a checkpoint has covered everything their keys could have signed. See Checkpoints.
Staying close to Bitcoin’s tip
Anchoring is only useful for trading if Sequentia follows Bitcoin closely: a trade waiting for a Bitcoin block needs Sequentia to reference that block soon after it appears.
Left alone, producers would prefer the opposite. An older Bitcoin block is less likely to be reorganised, so pointing at it protects their fees. Sequentia corrects the incentive in how blocks are chosen: when the committee has several candidate blocks for the same height, it backs the one anchored to the most recent Bitcoin block.
Whitepaper 7.2Why the freshest anchor wins only before a block is certified
The preference applies while the committee is choosing which proposal to sign. It never reorders a block that is already certified: the Bitcoin anchor is deliberately not part of the fork-choice comparison.
An early design let every new Bitcoin block trigger a new round and replace the latest Sequentia block. That gives the right incentive but orphans Sequentia blocks at every Bitcoin block, which defeats the purpose of immediate finality.
A proposal cannot gain rank by claiming an anchor nobody has seen. Each committee member counts an anchor only up to the Bitcoin height it knows itself, and checks the claim before signing.
Whitepaper 7.4When Bitcoin itself is forked at the tip
If the Bitcoin node knows of rival branches near the tip, the tip block may be the one that loses. A producer therefore anchors to the last height on which every live branch still agrees. This trades a little latency for stability, and it is a producer policy rather than a consensus rule, so operators can set it differently without splitting the network.
There is one exception. If the parent block is already anchored to one of the competing branches, the producer keeps following that branch for as long as it remains Bitcoin’s best chain: the chain is already committed, and holding back would only freeze the anchor. A frozen anchor also disables the rule that lets the chain continue without a quorum.
This exception was added after an incident on the public testnet on 1 October 2026, when a server failure took many committee nodes offline during a long-lived fork of Bitcoin testnet4 and the remaining nodes could neither form a quorum nor escape the stall.
What it asks of a node
A Sequentia full node needs a Bitcoin node next to it, ideally its own. The connection is not optional: a node that stops checking anchors can no longer notice that its chain is built on an orphaned Bitcoin block. A node that cannot reach Bitcoin refuses to start, or asks the user whether to start anyway and shows a warning for the whole session.
See Run a node.
Read further
- Whitepaper, Principle 5 (Bitcoin anchoring) and Principle 7 (cross-chain consistency).
03-bitcoin-anchoring.md: the anchor fields, the validation rules and the watcher.anchor-reorg-of-reorg-recovery-design.md: what happens when Bitcoin reorganises twice in a row.