Ark
Ark is a transaction-batching protocol for Bitcoin with VTXOs and an ASP — self-custody, batching, and a comparison with Lightning and Liquid.
Protocol paper (PDF): Ark — protocol specification — Ark Labs.
What is Ark?
Ark is a transaction-batching protocol for Bitcoin, developed by Ark Labs. The protocol makes it possible to carry out off-chain transactions while users retain full self-custody of their funds. At the core of Ark are Virtual UTXOs (VTXOs) — off-chain representations of bitcoin UTXOs — coordinated by an operator called an Ark Service Provider (ASP).
The ASP aggregates users' off-chain activity and bundles it into periodic on-chain commitment transactions. Each commitment transaction contains one or more batches that specify a tree of VTXOs (a Virtual Transaction Tree, VTXT). The result is a system with a minimal on-chain footprint: no matter how many off-chain transactions take place, the on-chain cost is O(1) per round.
Users can leave Ark at any time and withdraw their funds on-chain — either cooperatively with the operator (one on-chain transaction) or unilaterally by broadcasting the relevant virtual transactions in the tree (O(log t) transactions, where t is the number of VTXOs in the batch).
How Ark works
Boarding. A user creates a boarding transaction that locks funds in an output which can be spent either by the user and the operator together, or by the user alone after a timelock. The operator includes this output in the next commitment transaction and gives the user a VTXO.
Transactions. Ark transactions work like Bitcoin transactions, but off-chain. Alice can send a VTXO to Bob by creating an Ark transaction that spends her VTXO and creates a new one for Bob. The operator co-signs the transaction. Bob then swaps his new VTXO for a confirmed VTXO in a new on-chain batch.
Batch swap. The atomicity of a batch swap is ensured via connectors — anchor outputs that bind forfeit transactions to commitment transactions via SIGHASH_ALL. Bob hands over his old VTXO to the operator (via a forfeit transaction), and the operator gives Bob a fresh VTXO in a new batch. Both sides happen atomically: either both complete, or neither does.
Batch expiry. Each batch has an expiry time (Te). After Te, the operator can reclaim the entire batch via a sweep path. This means the user must come online and renew their VTXOs before Te — otherwise the user loses their funds. This is necessary so the operator can free up its capital.
Ark compared with the Lightning Network
The Lightning Network, described by Poon and Dryja (2016, PDF), is a network of bilateral payment channels. Two parties lock funds in a 2-of-2 multisig Funding Transaction and create Commitment Transactions off-chain that represent the current balance. Payments to third parties are sent through the network via Hashed Timelock Contracts (HTLCs) with decreasing timelocks.
Architecture
| Lightning | Ark | |
|---|---|---|
| Base structure | Bilateral channels between two parties | Hub-and-spoke with a central operator (ASP) |
| Off-chain unit | Channel balance (Commitment Transaction) | VTXO (Virtual UTXO) |
| Network | Peer-to-peer with routing | Direct coordination with the operator |
| On-chain footprint | Channel open + channel close (minimum 2 transactions) | O(1) per batch regardless of the number of transactions |
Deterring the use of old states
In Lightning, the use of old Commitment Transactions is prevented via Breach Remedy Transactions. Old Commitment Transactions are still valid Bitcoin transactions, but there's an economic penalty mechanism that makes broadcasting them financial suicide. When the channel balance is updated, the parties exchange revocation keys. If a party then broadcasts an old Commitment Transaction, the counterparty can use their Breach Remedy Transaction to take all the funds in the channel as a penalty.
In Ark, the transition happens via forfeit transactions and batch expiry. When a user swaps a VTXO, they sign a forfeit transaction that gives the operator the right to the old VTXO, conditional on the new commitment transaction being on-chain. There's no penalty mechanism in the Lightning sense — atomicity is ensured by connectors.
Onboarding and receiving
In Lightning, receiving payments requires an existing channel with inbound liquidity. Opening a channel costs an on-chain transaction, and both parties must coordinate. This is one of Lightning's best-known user barriers.
In Ark, the recipient needs no prior setup. A VTXO can be created for anyone via an Ark transaction. The recipient then swaps it for a confirmed VTXO. Onboarding to Ark is significantly simpler.
Monitoring
Lightning requires constant monitoring of the blockchain (or delegation to a watchtower) to protect against cheating. If the counterparty broadcasts an old Commitment Transaction and you don't react within the penalty period, funds can be lost.
Ark only requires periodic online presence (with period To < Te). The user doesn't need to monitor for cheating, but must renew their VTXOs before batch expiry. The consequence of missing the deadline is serious, though: the funds go to the operator.
Expiry
Lightning channels have no expiry date. A channel can exist for years, as long as both parties are cooperative.
Ark VTXOs always have an expiry date (batch expiry Te). The user must actively renew their VTXOs before this deadline. This is a fundamental difference that's often overlooked in the marketing of Ark-based wallets.
Strengths and weaknesses
Lightning's strength is multi-hop routing — the ability to pay anyone in the network via intermediaries, without trusting a central party. Lightning's weakness is its complexity: liquidity management, channel openings, the need for inbound capacity, and the requirement for constant monitoring.
Ark's strength is simple onboarding and ease of use — no channels, no liquidity management, a simple self-custody model. Ark's weakness is its dependence on a central operator, the requirement to periodically renew VTXOs, and the operator's capital requirements.
Ark compared with Liquid
Liquid is a sidechain developed by Blockstream. It's a separate blockchain network with its own consensus mechanism, connected to Bitcoin via a two-way peg administered by a federation of functionaries.
Custody model
Liquid uses a federation of about 15 functionaries who hold the pegged bitcoin in a multisig. Users trust that a majority of the federation acts honestly. If the federation colludes to commit fraud, they can steal the funds. Users have no option for unilateral exit — they depend on the federation's cooperation to move funds back to Bitcoin.
Ark gives users a guarantee of unilateral exit. Every VTXO can always be broadcast on-chain via the virtual transaction tree. The ASP can censor or refuse to cooperate, but can never steal funds. It's a fundamentally stronger self-custody model.
On-chain vs. sidechain
Liquid is a separate blockchain with its own blocks, its own consensus, and its own transactions. L-BTC (Liquid Bitcoin) is a separate token that represents pegged bitcoin. Transactions on Liquid don't touch the Bitcoin blockchain at all (apart from peg-in/peg-out).
Ark operates directly on top of Bitcoin. VTXOs are genuine Bitcoin transactions that are simply held off-chain. Commitment transactions are Bitcoin transactions. There's no separate blockchain, no separate token, and no separate consensus mechanism.
Trust
| Liquid | Ark | |
|---|---|---|
| Trust model | Federation (about 15 functionaries) | Single operator (ASP), but non-custodial |
| Unilateral exit | No — requires the federation's cooperation | Yes — always possible via VTXT |
| Can the operator/federation steal? | Yes, through collusion among a majority | No — can only censor, not steal |
| Separate blockchain | Yes | No — uses Bitcoin directly |
Functionality
Liquid supports Confidential Transactions (hidden amounts), asset issuance (tokens), and more advanced scripting than Bitcoin. It's designed for traders, exchanges, and institutional users who need fast settlement with confidentiality.
Ark is designed as a scaling protocol for payments, with a focus on simple onboarding and interoperability with Lightning. Ark doesn't support confidentiality features like Confidential Transactions, but inherits bitcoin scripting capabilities for VTXOs.
Interoperability: how the three work together
The three protocols aren't competitors but complementary layers in the Bitcoin ecosystem:
Bitcoin L1 is the settlement layer — the secure, decentralized foundation. All three protocols ultimately settle to L1.
Lightning is the routing layer — optimized for fast payments across a large network via HTLCs and multi-hop channels. Lightning's network effect (businesses, wallets, exchanges) is its biggest strength.
Ark is the onboarding and balance layer — optimized for a simple user experience without channel management. Ark can work together with Lightning via swap services like Boltz, which convert between VTXOs and Lightning payments.
Liquid is the institutional settlement layer — optimized for traders and exchanges that need fast, confidential settlement with Confidential Transactions.
In practice, a user can hold their balance in Ark (simple self-custody, no channel management), pay via Lightning (universal compatibility with businesses), and use Liquid for larger trades with confidentiality. Wallets like BlueWallet integrate Ark under the hood while the user sees standard Lightning invoices (lnbc) — the compatibility layer stays the same, but the self-custody model improves.
Important caveats
Ark is still early. Arkade launched as a public beta in late 2025. The protocol is under active development, and there are known limitations: the operator's capital requirements, the risk of VTXOs expiring, and the centralization around a single ASP. Future work includes multiple operators, better pre-confirmation mechanisms, and solutions for mass-exit scenarios.
VTXO expiry is a real risk. Users who hold Ark balances need to understand that their VTXOs expire. Wallets should communicate this clearly and preferably handle renewal automatically. Passive long-term storage is not Ark's purpose — for that, you should use on-chain cold storage.
Naming matters. Calling an Ark-based wallet a "Lightning wallet" is technically imprecise and can create false expectations for the user — especially around the expiry of funds.