Two answers to the same problem
Ark and Spark both let you pay in bitcoin instantly without a blockchain transaction for each payment, and without opening Lightning channels of your own. Both give you a way to take your bitcoin back to the blockchain without anyone's permission. Both rely on an operator while things are running normally.
They differ in what you hold, whom you trust and when, and what you have to keep doing to stay safe. This page puts those differences side by side. It is a summary of the two full guides, Ark and Spark, and it adds nothing they do not say. Read the full guide before you put money in either.
Side by side
| Ark | Spark | |
|---|---|---|
| What you hold | A VTXO: a claim with a path of signed transactions back to a Bitcoin output. | A leaf: an amount at the end of a tree of signed, unbroadcast transactions, locked to a key shared between you and the operators. |
| Who runs it | One operator per service. Ark is a family: Second's Bark and Arkade are separate implementations with different rules. | A group of operators. In October 2026 the published set was Lightspark, Flashnet and Breez, with any two able to sign together. |
| How a payment moves | The operator coordinates it off-chain. Claims are later renewed together in a round that settles on the blockchain. | The operators change their part of the shared key so that the receiver's part completes it. Nothing touches the blockchain. |
| The extra trust when you receive | Until you complete a standard refresh, you rely on the operator and earlier senders not working together to spend the same claim twice. | You rely on enough operators deleting their old key shares. If they kept them, they and a previous owner could sign your leaf away. |
| Can that trust be removed? | Yes, for that payment: a completed refresh puts your claim in a new confirmed tree. | No. Spark's own comparison says the operators cannot prove the deletion happened. |
| What you must keep doing | Refresh before your claim's expiry, and keep the off-chain records your exit needs. | Have your wallet, or a watchtower acting for you, online to answer if a previous owner broadcasts an old exit. |
| Leaving without the operator | Broadcast your branch of the tree, wait for a timelock, then claim. | Broadcast the pre-signed exit from the root of the tree to your leaf, wait for a timelock, then claim. |
| What leaving costs | Several Bitcoin transactions' worth of fees. A small claim can cost more to recover than it holds. | Several Bitcoin transactions' worth of fees. A small leaf can cost more to exit than it holds. |
The difference that matters most
Both systems ask you to trust someone at the moment you are paid. What happens to that trust afterwards is different.
In Ark, the trust has an end. A payment you have just received depends on the operator and the earlier senders behaving. Once you complete a standard refresh, your claim sits in a new tree confirmed on the blockchain, and that dependence is gone for that payment. The cost is a deadline: a claim has a lifetime, and you have to refresh or exit before it runs out.
In Spark, the trust does not end. Every transfer depends on the operators deleting old key material inside their own systems, where nobody outside can check. I have seen no report of an operator failing to do it. The design simply gives you no way to verify it, for any payment, at any point.
Neither is the same as holding bitcoin on the blockchain under a key only you hold. There, nobody else's key or cooperation is involved at all.
The exit is a last resort in both
An exit you can make alone is what separates these systems from a custodial app. It is still slow and it costs fees, in both.
- You need the right data. An Ark exit needs the stored transaction records for your branch. Check what your Spark wallet needs beyond its recovery words.
- You need fees, and sometimes separate on-chain bitcoin to pay them.
- You need time. Both end with a timelock before the final claim.
- You need a wallet that lets you do it. When I checked in October 2026, Spark's own exit instructions were marked beta and ran from the command line.
If the amount you hold is smaller than an exit would cost, the exit protects you in theory only.
How to choose
- Start from the wallet, not the protocol. You will meet either one through an app. Find out which implementation it uses, who the operator or operators are, and whether the app lets you exit by yourself.
- Ask what you must remember to do. Ark asks you to refresh in time. Spark asks you to stay watchful, or to rely on a watchtower.
- Ask what you cannot check. In Spark it is key deletion on every transfer. In Ark it is the period before a refresh completes, and the details differ between implementations.
- Keep the amounts small. Treat both as a spending balance. Savings belong in an on-chain wallet whose keys only you hold.
If you already use Lightning happily, you do not need either. They are worth learning about because wallets are starting to build on them, and the app in your hand may already be using one.
Sources & further reading
Researched 15 November 2026. Software and services change: check the current documents before you act.
- Ark: VTXOs ↗
- Second: payments ↗
- Second: rounds ↗
- Second: VTXO lifetime ↗
- Second: emergency exits ↗
- Arkade: security and trust ↗
- Spark: core concepts ↗
- Spark: transfers ↗
- Spark: trust model ↗
- Spark: sovereignty and exits ↗
- Spark: unilateral exit ↗
- Spark: comparison with Ark ↗
Ark → · Spark → · Lightning → · Choose the Lightning setup you can maintain →
