Ark Protocol

Definition: The Ark protocol is a Bitcoin Layer 2 design for making off-chain payments using virtual transaction outputs (VTXOs). An Ark server or Ark service provider coordinates users and batches Bitcoin settlement, while each VTXO is backed by a package of transactions that can provide an on-chain exit path. Ark is a protocol design, not a separate cryptocurrency or a single network; implementations can make different choices about coordination, payment flows, expiry, and recovery.12

TypeBitcoin Layer 2 protocol design for off-chain payments
Core unitVirtual transaction output (VTXO), backed by Bitcoin transactions and spending conditions2
CoordinatorAn Ark server or service provider coordinates batches and payments; roles vary by implementation3
SettlementGroups of VTXOs are anchored through Bitcoin transactions; a unilateral exit may require multiple transactions and a timelock25
Example implementationSecond announced Bark mainnet availability on June 9, 2026; this describes Bark, not every Ark implementation6
DirectoryBitcoin Directory

How Ark and VTXOs work

A VTXO is an off-chain Bitcoin output controlled by a user through transaction data and signatures. It is “virtual” because it has not necessarily been broadcast as a confirmed, individual output on Bitcoin’s base chain. The user holds the transaction path that can eventually create an on-chain output, subject to its script conditions, timelocks, and the implementation’s rules. The construction is intended to let many users share the cost of a larger on-chain output rather than publish a separate Bitcoin transaction for each off-chain transfer.25

An Ark server coordinates the protocol but is not simply a blockchain validator. In the reference design, a user can cooperate with the server for normal activity or use a unilateral transaction path to exit to Bitcoin if cooperation fails. That exit is not always immediate: spending conditions can impose a delay, and an exit may involve broadcasting a chain of transactions and paying Bitcoin network fees. Users therefore need to keep the relevant wallet data and understand the recovery procedure for the particular implementation they use.2

Rounds, batches, and payments

In a round-based design, the server periodically organizes users’ VTXOs into a batch. Participants exchange older VTXOs for new ones, and the server publishes a Bitcoin transaction that anchors the batch. Connector outputs can link each participant’s forfeiture transaction to the batch transaction, so a user does not give up an input VTXO unless the corresponding new batch is confirmed. Rounds can spread the on-chain cost across many users, but they need coordination and on-chain block space; delays or congestion can affect when a refresh completes.3

Some Ark designs also support out-of-round (OOR), sometimes called “arkoor,” transfers. These can move a VTXO between users without waiting for the next on-chain round. In the reference design, the server co-signs part of the transfer. That makes the payment faster, but it adds a trust assumption: the receiver depends on the server and prior sender not colluding to create a conflicting spend. A receiver can reduce this exposure by refreshing the VTXO into a confirmed batch, when supported, before relying on it as a longer-term balance.4

Ark compared with Lightning

Ark and the Lightning Network both move Bitcoin activity off-chain, but they organize payments differently. Lightning uses payment channels connected into a routing network. Ark uses a server-coordinated model with shared transaction outputs and VTXOs. Ark may reduce some channel setup and inbound-liquidity work for users, while relying more directly on a service provider for coordination and, in some payment flows, liquidity. The operator still has to fund or arrange the on-chain batch, and availability, fees, and liquidity depend on the implementation and its service model.13

Security and limitations

“Self-custodial” describes an important design goal of Ark, but it does not mean every payment is free from trust or operational assumptions. A user’s ability to exit depends on having the correct transaction data and keys, acting before relevant deadlines, paying on-chain fees, and having an implementation whose contracts work as intended. The server may refuse service, pause rounds, or be unavailable. Some VTXOs can expire or need periodic refresh; timing and recovery conditions are implementation-specific, so users should check them rather than assume one universal Ark expiry period.25

Ark also does not remove Bitcoin’s block-space limits. Batches need on-chain confirmation, and a mass exit could require many users to compete for block space at once. An implementation’s operator, wallet, fee policy, liquidity, data availability, and emergency-exit design all affect the practical security and user experience. Review the specific software and service before depositing funds; the general protocol label alone does not tell users which guarantees a particular wallet or server provides.36

History

  • May 22, 2023: Bitcoin developer Burak Keceli introduced the design to the bitcoin-dev mailing list under the name Ark, describing it as an alternative second-layer approach for off-chain Bitcoin payments.1
  • June 9, 2026: Second announced that Bark, its implementation of Ark, was available on Bitcoin mainnet. This is a milestone for that implementation, not a statement that every project using the Ark design is live on mainnet.6

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Keceli, Burak. “Ark: An Alternative Privacy-preserving Second Layer Solution.” Bitcoin-Dev mailing list, May 22, 2023. Original proposal.
  2. Ark Protocol. “VTXOs.” Accessed November 10, 2026. VTXO design and expiry.
  3. Ark Protocol. “Connectors.” Accessed November 10, 2026. Rounds, batches, and connectors.
  4. Ark Protocol. “Out-of-Round Payments.” Accessed November 10, 2026. OOR payment model and trust assumptions.
  5. Argentieri, Marco, Zeta Avarikioti, Andrew Camilleri, Pim Keer, and Matteo Maffei. “Ark: A UTXO-based Transaction Batching Protocol.” Accessed November 10, 2026. Technical paper.
  6. Second. “Bark Now on Bitcoin Mainnet.” June 9, 2026. Implementation launch announcement.