Sequentia vs the rest
Built on Liquid’s code. No peg, no federation, no gas coin.
At a glance
| Fee paid in | Bitcoin on the chain | Who produces blocks | Finality | Tie to Bitcoin | |
|---|---|---|---|---|---|
| Ethereum, Tron, Solana | The chain’s own coin | Wrapped, held by a custodian | Stakers of the chain’s coin | Varies | None |
| Liquid | L-BTC | Pegged, held by a federation | A fixed federation | Final after two blocks | Federated peg |
| Rootstock | rBTC | Pegged | Bitcoin miners, by merged mining | Probabilistic | Merged mining, peg |
| Rollups | The base chain’s coin | Wrapped | Usually a single sequencer | Inherited from the base chain | None for Bitcoin |
| Assets on Bitcoin (Taproot Assets, RGB) | BTC | Real | Bitcoin miners | Bitcoin’s | Uses Bitcoin’s blockspace |
| Sequentia | Any asset | Real BTC stays on Bitcoin | Anyone who stakes | About 10 seconds | Every block anchored |
Versus Liquid
Sequentia is the closest relative of Liquid. Both run on Elements, the Bitcoin Core derivative developed by Blockstream, and share its UTXO model, Bitcoin Script, confidential transactions and asset issuance. The differences are the point.
- No peg, no L-BTC. Liquid needs real bitcoin locked with its federation, and fees are paid only in the pegged coin. Sequentia inherits that machinery and leaves it switched off. Bitcoin stays on Bitcoin.
- No federation. Liquid’s blocks are signed by a fixed set of functionaries chosen off-chain. Sequentia’s are produced by whoever stakes, and paid in whatever fees they accept.
- Anchoring. Sequentia’s history is bound to Bitcoin’s block by block, which is what allows trading against real bitcoin.
- Liveness. Liquid halts if a third of its functionaries are missing. Sequentia reads Bitcoin’s progress to know when it is stalled and keeps going.
- Bitcoin’s address format, public amounts by default. Liquid hides amounts by default behind its own address format. Sequentia uses Bitcoin’s addresses, and confidentiality is opt-in.
- Compliance by consensus. Supervised assets need no co-signing intermediary.
Go deeperWhat the September 2026 incident showed
On 6 September 2026 a defect in Liquid’s software let an attacker create roughly 4,000 L-BTC that no bitcoin backed, redeem them through the ordinary peg-out, and take about 4,000 real BTC out of a reserve of roughly 4,200. The attackers returned 3,400 and kept some 598, and peg-outs were frozen for weeks.
Sequentia had the identical defect, because it shares the code, and corrected it in the same week. The comparison is instructive precisely because the defect is not what distinguishes the two systems. Sequentia asks nobody to hand their bitcoin to a federation, so there was no reserve to drain: had the bug been exploited there, nobody would have lost a bitcoin.
Source: whitepaper, section i.
Versus Ethereum, Tron and other coin-first chains
These chains host most of today’s stablecoins and tokenised assets. They share three traits Sequentia was designed to remove.
- A mandatory coin. Fees are accepted in the chain’s own coin only. See The end of gas tokens.
- No bitcoin. Trading against bitcoin means trading against a custodian’s token.
- Accounts and unbounded contracts. Account models expose a user’s whole balance and history from one address, and when the chain gets busy, automated trading saturates it and invites front-running.
They also create new coins to pay their validators. Sequentia creates none.
Versus rollups
A rollup executes transactions off a base chain and posts the data back onto it. For a chain whose bottleneck is execution, it is the right answer. For Sequentia’s purpose it is not:
- ordering is normally done by a single sequencer, a centralisation at least as strong as a federation;
- the security it inherits is the base chain’s data availability and settlement, which here would have to be Bitcoin, and Bitcoin offers neither to a rollup;
- the fee is paid in the base chain’s coin, which brings the gas token straight back, and a rollup on Bitcoin would also have to post its data into Bitcoin blockspace.
Versus assets issued on Bitcoin itself
Taproot Assets and RGB put assets directly on Bitcoin. That keeps the bitcoin real, but every issuance and every settlement uses Bitcoin’s own scarce blockspace, and assets without deep liquidity cannot be traded over payment channels. See Finance on Bitcoin.
Versus merged mining and proof of burn
Merged-mined sidechains, such as Rootstock, give Bitcoin’s mining pools power over a chain in which they hold no significant stake, and they still need a pegged bitcoin to pay fees.
Proof-of-burn and proof-of-transfer chains, such as Stacks, ask users to give up bitcoin for influence over a chain that may not succeed, and in practice fall back on their own token for governance.
Whitepaper iiiThe full survey: nine families of design
The whitepaper compares Sequentia against nine architectures and explains the trade-off of each:
- Proof of authority (BNB Smart Chain): a fixed set of trusted validators; no censorship resistance.
- New proof of work: unsafe at birth, because renting enough hashrate to attack a young chain is cheap.
- Merged mining (Rootstock, Namecoin): miners govern a chain they have no stake in.
- Strong federation (Liquid): maximum persistence, but it halts if a third of signers vanish, and membership is closed.
- Proof of stake with immediate finality (Tendermint, Algorand): open membership, same stall risk, and stakers hold absolute power over the rules.
- Proof of stake with probabilistic finality (Cardano): stays live, but forking is costless, so blocks are orphaned.
- Proof of stake with finality added afterwards (Polkadot): a hybrid that can split isolated nodes permanently, and lets stakers upgrade the rules on-chain without the users.
- Proof of burn or transfer (Stacks, Spacechain): hard to bootstrap; drifts back to a governance token.
- Rollups: a single sequencer, and the base chain’s coin for fees.
Sequentia takes immediate finality from the fifth family, removes its stall risk by using Bitcoin as an outside clock, and removes the stakers’ power over the rules by keeping validation on every full node. See the lightpaper.