Ark: Arca
Arca is an Ark protocol for Sequentia. It does for every asset on Sequentia what Ark does for bitcoin: payments that are instant and off-chain, with no channels and no liquidity to manage, while each user keeps a coin they can take to the chain on their own.
It is a fork of Bark, the Ark implementation by Second, rebuilt on Sequentia’s covenants.
- Code: arca
- Desktop app: arca-client
The idea
An operator commits many users’ balances to one on-chain output, called a batch. Inside the batch is a tree of transactions, and each user holds one leaf of it.
- Paying and receiving happens off-chain, between leaves, with the operator’s co-signature. It is instant.
- Leaving needs nobody. A user publishes the path from the batch to their leaf and claims it after a delay. The operator cannot stop this.
- One asset per batch. Every asset issued on Sequentia can have batches of its own.
So the operator provides speed and convenience. It never holds the keys to a user’s coin.
What covenants change
On Bitcoin today, the tree inside a batch is held together by transactions that participants sign in advance. On Sequentia the tree is a covenant tree: each output’s script pins what its children must be, and the chain itself enforces it.
| Ark on Bitcoin today | Arca on Sequentia | |
|---|---|---|
| What holds the tree together | Pre-signed transactions | Covenants checked by consensus |
| Assets | Bitcoin | Any Sequentia asset, one per batch |
| Leaf scripts | Bitcoin Script | Tapscript with introspection, and Simplicity |
Covenants have been in production on Elements chains for years. This is also the practical argument for adding them to Bitcoin (proposals such as BIP119 CTV, TXHASH and BIP348 CSFS): Ark already works well there, and the same design would bring it to the state of the art.
The life of a coin
- Board. A user moves an on-chain coin into the operator’s next batch and receives a leaf.
- Pay and receive. Leaves change hands off-chain, instantly.
- Refresh. A batch expires 28 days after it was made. Before then, each leaf is moved into a new batch. The holder submits this once, naming the leaves given up and the leaves wanted, and the operator carries it out in a later round without the holder being online. A refresh is free in the last days before its deadline.
- Offboard or exit. A user leaves with the operator’s cooperation, cheaply, or without it, by publishing their path.
Go deeperWhat happens to a holder who disappears
A holder who stays away does not lose the coin when the batch is swept. Once the batch is released, the operator, and every watchtower the holder’s wallet deposited the coin with, bring it on-chain under the holder’s own key, and the wallet boards it again when it returns.
A coin a sweep takes all the same is not the operator’s to keep: its server owes it back, less a late-refresh fee, and repays it as a new leaf once the holder’s wallet claims it.
When a holder gives up an old leaf for a new one, it hands over a forfeit of the old leaf bound to the new round. The forfeit is void if that round leaves the chain, so a Bitcoin-anchor reorganisation cannot be used to take both.
Details: the arca README.
Go deeperFinality of an off-chain coin
A coin resting on a round is as final as that round. While the round’s block is out of the chain, the coin is worth nothing, and it is good again if the round returns. Since a Sequentia block is displaced only by a reorganisation of its Bitcoin anchor, this is the same guarantee as an on-chain payment: see Final in seconds.
The operator’s server watches the chain and rebroadcasts everything it has published after any rollback.
In the wallets
In the web wallet’s user mode, you do not see any of this. The wallet holds its Sequentia assets in an operator’s tree by itself and shows one balance per asset. A payment to another wallet’s receive code arrives in seconds.
Developer mode shows the leaves, the balance per route, boarding, and an exit drill.
Bitcoin is handled the same way on a Bitcoin ark, with Bark: see Instant bitcoin.
The Arca client
A desktop app for Linux and Windows. With it you join an operator and use it as a dual-chain wallet: every Sequentia asset as Arca coins and on-chain coins, and bitcoin on a Bitcoin ark. On Linux you can also run an operator with it.
It bundles the arca command-line client and, for bitcoin, Bark’s own client and daemon. Everything the wallet does, every check and every signature, is done by those clients; the app shows what they say.
Operators publish a signed record in the asset registry, which is how wallets find them.
Arca or Lightning?
Both are instant. Lightning needs channels funded on both sides, so it suits heavily traded assets and reaching the wider Lightning network. Arca needs no channels, so it works for any asset from the first payment. The wallets use both and choose for you. See Lightning: SeqLN.