Ark

The awkward part of Lightning is that you cannot be paid until somebody has already locked money on your side of a channel. Ark removes that step: a service provider funds one big on-chain output per round and slices it into virtual outputs for everyone taking part. Those slices carry a deadline, typically four weeks, and a slice you forget about reverts to the provider.

How it works

Ark works in rounds, and a round is one on-chain transaction shared by many people.

Burak proposed the design in May 2023. A provider gathers the requests waiting at that moment, publishes a single transaction, and makes its output the root of a tree of pre-signed transactions. Each leaf of that tree is a virtual output, a VTXO, belonging to one participant. Dozens of balances therefore occupy one on-chain output, which is where the cost saving comes from.

Paying somebody means invalidating your leaf and having theirs created. You hand the provider a signature that forfeits your VTXO, and in the next round the recipient receives a fresh one. You never negotiate capacity with anybody, and the recipient does not need a prior relationship with you or with the provider.

The escape hatch is unilateral exit. Because every transaction in the tree is already signed, you can broadcast the path from the root down to your own leaf and land the coin on chain without the provider's help. It works, and it is not cheap: you pay for several transactions instead of one, which is the honest price of sharing an output with strangers.

Expiry is the part people underestimate. A VTXO lives for a set window, commonly 28 days, and before it lapses you have to refresh it by joining another round. Miss the window and the timelock on the shared output lets the provider sweep what is left. The provider is also fronting real bitcoin in every round and only recovers it when those outputs expire, so the fee you pay is rent on that capital rather than a routing charge.

Covenants would make this cheaper. The version running on bitcoin today, covenantless Ark, replaces a missing covenant opcode by having every participant in a round sign the tree, which works but demands that everyone be online and cooperative at round time. An opcode such as OP_CHECKTEMPLATEVERIFY would let the tree be built without that ceremony.

Where you see it

Ark lives in test networks, early mainnet services, and wallets aimed at people who want Lightning-style payments without running channel software.

What it is genuinely good at is onboarding. A new user can receive their first payment immediately, with no channel to open, no inbound capacity to buy and no node to keep online, which removes the single most common reason people give up on Lightning.

The rule to take away is about time, not trust. The provider cannot take a VTXO you are watching, because the pre-signed exit path is yours. It can refuse to serve you, and it does end up with the coins of anyone who lets a deadline pass. Treat an Ark balance the way you would treat a transit card: convenient, topped up on purpose, and not where your savings live. Money you intend to keep belongs in a wallet whose only requirement is that you protect the seed phrase.

Ark vs Lightning Network

Ark and Lightning both move bitcoin off chain with timelocks, and they solve liquidity from opposite ends. On Lightning, receiving needs inbound capacity that somebody committed to your channel in advance, and once it is there the balance stays yours indefinitely. In Ark, receiving needs nothing arranged beforehand, and the provider recycles its capital every round, but your balance carries a clock. Put simply: Lightning makes you solve liquidity once and then leaves you alone, while Ark makes liquidity somebody else's problem and hands you a renewal date.