Skip to content

Status and roadmap

Simplifies the whitepaper, section v

This page lists what exists, what is being built and what is planned. An item appears under “in development” only if it has a public branch or a public specification.

Where things stand

Live A public testnet, producing blocks continuously since its re-genesis on 5 July 2026, anchored to Bitcoin testnet4. Every consensus rule in the whitepaper is running on it.

Live A full set of applications: wallets for browser, phone and desktop, an exchange, an explorer, a faucet, staking pools, bridges and more. See What is live today.

Not yet Mainnet. There is no Sequentia mainnet. Testnet coins and assets have no value, and the testnet can be reset.

Whether it is all working right now: the status page.

How we got here

When What
July 2022 First edition of the Sequentia paper: the design as a proposal.
2022 Development starts, with a small team funded by angel investors.
June 2024 Second edition of the paper.
5 July 2026 Re-genesis of the public testnet, on Bitcoin testnet4, with the public fixed-size committee of up to 250 members.
17 July 2026 Testnet incident: nodes final on different branches after a burst of Bitcoin testnet blocks. Result: the escape rule now requires elapsed Bitcoin time, and the reconciliation rule was added.
Summer 2026 Coordinated upgrades at announced heights, among them the sixty-second block spacing as a consensus rule and supervised assets (active from block 94,600).
September 2026 The Liquid reserve incident. The same inherited defect is fixed in Sequentia the same week; no peg, so no funds were at risk.
1 October 2026 Testnet incident: a server failure during a long Bitcoin testnet fork halts the chain. Result: producers keep following a Bitcoin branch the chain is already committed to.
October 2026 Revised edition of the whitepaper, describing the protocol as built. Sequentia at the Plan B Forum in Lugano.
November 2026 Node releases in the 25.2 series.

The most useful lesson of the testnet so far is in the whitepaper’s own words: a consensus change is easy to write and a coordinated cutover is not. Every rule that needed a hard fork has been through at least one coordinated activation, at an agreed height, with every node upgraded in one window.

In development

Swaps settled by proof of a Bitcoin payment

Coming

Three new opcodes let a Sequentia output open only for a spender who proves that a specific Bitcoin payment is in Bitcoin’s chain. This makes the bitcoin side of a swap an ordinary payment, and closes at consensus level the case of a buyer who double-spends after a Bitcoin reorganisation.

  • State: implemented and tested on a development branch of the node. Not merged. It also needs a signing rule for the committee.
  • Then: activation on the testnet at an announced height, followed by the wallets and SeqDEX moving from hashed-timelock swaps to the new form.
  • Read: Swaps and SeqDEX, and the specification.

Hardening

Continuous work on the node’s consensus and production code, visible in the pull requests of the node repository. Security review is described in 07-security-and-audit.md.

Moving experimental pieces to live

Lightning swaps in the wallets depend on a hosted demo backend today. Lending, the launchpad and network-enforced regulated assets are working but young. See the labels in What is live today.

Planned

The wallet on Bitcoin mainnet

The Bitcoin side of the wallet, Ark with Lightning, runs on Bitcoin testnet4 today. Its launch on Bitcoin mainnet is planned for 2027.

Sequentia mainnet

No date is announced. What launch involves is already specified:

  • a new genesis block with a fresh founder key and the distribution of the 400,000,000 SEQ;
  • no change to any consensus rule: the committee, the minimum stake, the block weight, anchoring and the rest are already at their real values and fixed in the code;
  • payment of the balances earned on Emissio to the mainnet addresses testers registered.

See 06-tokenomics-and-launch.md.

Covenants on Bitcoin

Not ours to ship, but worth watching. Proposals such as BIP119 (CTV), TXHASH and BIP348 (CSFS) would let Ark on Bitcoin work the way Arca already works on Sequentia.

How upgrades reach the testnet

  1. A change is developed in the open and merged.
  2. If it changes consensus, it is given an activation height.
  3. A release is published and announced, and every node operator upgrades before that height. A node that does not upgrade forks off.

Releases are tagged in the node repository. If you run a node, follow the community channels for upgrade announcements.

Forward-looking statements

Everything under “in development” and “planned” describes intentions, not commitments. See the disclaimer.