Bitcoin payments without a channel for everyone
Ark is a family of Bitcoin payment protocols. Users hold virtual transaction outputs, or VTXOs, backed by Bitcoin transactions that can be brought on-chain. An operator coordinates fast off-chain activity and shared settlement. There is no separate Ark currency to buy, and ordinary Ark payments do not require every user to open and manage their own Lightning channel.
Think of a VTXO as a claim with a transaction path back to an ordinary Bitcoin output. It is more than a number in an app, but it is not yet the same thing as a confirmed output controlled by a simple wallet key. The claim has conditions, supporting transaction data and a lifetime. Those details are the point of this guide.
Ark is most interesting for spending balances and frequent small payments. It does not make on-chain fees disappear, guarantee anonymity or turn an intermittently connected wallet into unattended long-term storage. The right question is not only “how fast is the payment?” but “what must remain true for me to recover it?”
Follow the payment, then test the exit
Start with a fictional confirmed boarding transaction. Split a payment, refresh the recipient’s claim, then turn the operator off. Follow only your branch back to Bitcoin. Raise the fee rate or remove the exit records to see why an exit path and an immediately usable balance are different things.
This is a teaching model of a standard, non-delegated refresh. Its 40-block lifetime, four-block exit delay and transaction sizes are invented. Payment amounts exclude cooperative service fees. It does not simulate conflicting spends, signatures, mempool acceptance or real confirmation times.
A path anchored in Bitcoin
Confirm the fictional boarding transaction supporting 100,000 sats. Ordinary service fees are excluded.
Not yet boarded
Expiry height: -
Start with boarding, then follow the recipient through Pay and Refresh.
Check your understanding
Does receiving an Ark payment always restart its expiry?
Conceptual standard-refresh model, not a wallet emulator. Invented: 40-block lifetime, four-block delay, 600 vB of branch/fee-bump transactions and a 150 vB claim. Actual values differ. No real funds or network calls.
A VTXO links to confirmed Bitcoin funding. Payments can add trust assumptions; standard refreshes renew claims. Independent exits need records, fees and timely confirmations, then a delayed claim.
What you actually hold
A confirmed shared commitment anchors a tree of transactions. Leaves represent individual users’ claims. Most of that tree stays unpublished during normal use. An exit publishes the necessary path rather than forcing every leaf on-chain. Shared ancestors can help later exiters, but broad simultaneous exits still compete for Bitcoin block space.
Current implementations use presigned transactions and signing protocols to constrain what can happen next. Designs using proposed covenant opcodes are a different branch of development; do not treat a proposed Bitcoin upgrade as a requirement already deployed. A valid claim also depends on which transactions were signed, which state was forfeited and which backing output remains unspent.
Fast payment is not the same as settlement
In Second’s Bark design, out-of-round payments create spend VTXOs. Until a receiver completes a standard refresh, the receiver relies on the operator and relevant prior senders not colluding to produce conflicting spends. Longer chains can add counterparties and exit transactions. A visible balance is not proof that this extra assumption has disappeared.
A completed standard refresh exchanges the old claim for a claim in a new confirmed tree. It improves the received payment’s security model and extends its lifetime. Merely requesting a refresh, watching a spinner or seeing a transaction in a mempool is not the same as completing that transition. Second’s delegated refresh path has a different trust model; do not silently substitute it for the standard process shown here.
Second: payments ↗ · Second: rounds ↗
Refresh before the deadline
An expiry is a point at which the operator’s reclaim path becomes available. It is not a promise that coins vanish at that instant, nor is it a safe period to begin planning. Refreshing needs cooperation; exiting needs time, data, fees and confirmations. Leave room for an outage or fee spike.
Second documents cooperative recovery options after expiry, but those require the server. They are not a replacement for timely independent recovery. An Ark payment can inherit the original expiry rather than restart the clock. In this model, once the final exit leaf confirms before expiry it no longer expires, although a separate relative delay still applies before the final claim.
Two different ways back to Bitcoin
Cooperative offboarding asks the operator to help move the balance on-chain. A unilateral exit instead uses the stored transaction chain without its cooperation. Broadcast and confirm the required ancestors, reach the exit output, wait for its relative timelock, then claim to your own on-chain address. The final claim is a distinct step; an “exit started” message is not completion.
Each necessary transaction consumes block space. The cost depends on tree depth, extra off-chain spends, already confirmed ancestors and current fees. Some workflows need separately available on-chain bitcoin to fee-bump the exit chain. A small claim can cost more to recover than it contains. Our fee panel deliberately shows an external fee reserve separately from the VTXO balance.
What gets easier, and what you take on
Benefits: fast cooperative payments, shared settlement costs and less individual channel management. Lightning interoperability can be offered through a gateway or swap flow, but Ark itself is not Lightning and an Ark address is not an ordinary Bitcoin address.
Costs: operator availability and liquidity, refresh management, off-chain data backups, extra assumptions for unsettled payments and potentially expensive exits. The operator and counterparties may learn payment information; privacy depends on the actual protocol, wallet and deployment. Neither batching nor the word “self-custodial” proves anonymity or effortless recovery.
An ordinary on-chain payment gives the receiver a confirmed output after inclusion in a block. Lightning uses channels and channel-specific liquidity. Ark shares on-chain commitments through an operator and introduces refresh and exit responsibilities. None is simply a faster version of the others: compare the counterparty assumptions, data you must retain and how you get back on-chain.
Ark is a family, not one identical service
Bark/Second and Arkade share the broad idea but differ in payment construction, settlement, delegated operations, fees and software. Arkade’s current security documentation also describes an operator signer using a trusted execution environment. Its Arkade Script conditions can be checked by that operator rather than directly by Bitcoin; that is distinct from the Bitcoin-enforced exit path.
Do not carry a lifetime, fee quote, recovery instruction or security claim from one implementation into another. Compare the exact wallet version, operator parameters and current documentation. This guide describes shared concepts and names implementation-specific claims. The simulation is not an Arkade or Bark wallet emulator.
A sensible first experiment
Choose an implementation and follow its official test-network walkthrough. Confirm that the wallet, operator and chain-data source use the same network. Receive test coins, inspect the VTXO status and expiry, send to a second test wallet, refresh and try cooperative offboarding. Then rehearse an exit and final claim in the supported test environment.
Before using a spending balance, establish how the wallet refreshes when your phone sleeps, which fees it charges and how it alerts you to approaching expiry. Record the supported recovery process. Treat software and service limits as changeable settings, not timeless properties of Ark. The official Bark signet guide and Arkade wallet documentation are linked below.
Bark: signet walkthrough ↗ · Arkade: wallet setup ↗
Back up the claim, not just the keys
A seed may recreate keys without recreating all off-chain transaction data. Second documents seed-only recovery through its server mailbox, while independent full restoration needs an up-to-date wallet database backup. Its documentation distinguishes restoring a balance from restoring payment history and an exit already in progress.
Find out what your chosen wallet exports, how often it updates and where an encrypted copy survives device loss. Rehearse recovery while the operator is unavailable. Keep the transaction records and keys confidential. Do not paste a real seed, wallet database or exit package into an educational website.
Before relying on Ark, be able to answer: what kind of VTXO do I hold, when does it expire, who must cooperate, what data do I possess, and how will I pay for the exit? If any answer is unclear, stay with test funds until it is clear.
Sources & further reading
Researched 14 November 2026. Implementation details can change.
