Rovereto, Tuesday 17 November 2026 · Year XIII, n. 321 itende
Bitcoin Valley
ContentsClose

Dispatches from the valley where you pay in bitcoin.

The software · For people who take things apart

Spark, and what we're keeping an eye on

A wallet that takes payments even with the phone switched off, without anyone holding the words for you. Spark comes close. Here's how it works, and who we rely on to make it work.

What it is

Spark is a protocol built on top of Bitcoin by Lightspark, an American company. It was unveiled in alpha in autumn 2024,1 and the beta has been on the real network since 29 April 2025.2 The documentation still calls it beta, and “very experimental”.3

The idea is called a statechain, and Ruben Somsen proposed it in 2018 at Scaling Bitcoin in Tokyo: you hand over the right to a coin already written in the ledger, without writing a new transaction every time it changes hands.4

Spark takes it further: it splits the coin into pieces, so you can pay any amount, and instead of a single custodian of the second key it uses a group of operators.5

You

One key sits in your wallet. Without you, the operators can't spend.

The operators

The other key is split among a few operators, the Spark Operators, and none of them holds it whole. There are three founding operators: Lightspark, Flashnet and Breez.3

To spend, you need both. You need your signature and those of a share of the operators, merged into a single signature with a method called FROST.6 Without them, you can't spend quickly either.

Who we rely on. When the coin passes from you to someone else, the operators change their part of the key and delete the old one. As long as at least one of them really does it, at the moment of the handover, whoever held the coin before can no longer take it back.7 You can't see this from outside: this is the trust worth knowing about, and one honest operator is enough.

If the operators disappear, the way out. The wallet keeps pre-signed transactions to one side that bring the coin back onto the ledger. If the operators disappear or refuse, you broadcast them and the sats are yours again, after a wait. You need a coin of your own on-chain to pay the fees, and for small amounts the exit costs more than it's worth.8

And Lightning. Spark and Lightning are different networks. Swapping between them is the job of a provider, the Spark Service Provider. The one wallets use today belongs to Lightspark, and its code isn't public.9

Why we chose it

The Valley's rule is always the same: the recovery phrase stays only with whoever takes the payment, and there are no keys on the server that can spend. The software is built that way.

At the till, that rule is a tough one. Whoever takes the payment has to be reachable even when their phone is off, and that's usually where someone steps in to hold the money for them. Of the ones we've tried, Spark is the closest road to the rule. On 1 November 2026, with Spark SDK 0.14.0 on Lightspark's test network, we saw that:10

  • the till uses a throwaway wallet, and all it knows about the owner is their public key;
  • it took a payment with the owner's phone switched off, for thirty seconds or so, and when the phone came back on the sats were theirs;
  • the owner gets the takings back starting from nothing but the recovery phrase.

We also saw two limits. The payment showed up in the balance after about 30 seconds, and not all of it could be spent straight away. And in that test the payer was another Spark wallet; we tried paying from an ordinary Lightning wallet later, with Blink.

And the world moves fast: further down are the other roads we're following.

Where the till comes in

Today the site's till reads the shop's Lightning address and asks its provider whether the invoice has been paid. How it works is in lesson 5. Any Lightning address will do: for a small shop the easiest is a wallet on Spark, which receives payments with the phone switched off, with no channels or liquidity to look after.

Blink, the first wallet we tested the till with, has also offered self-custodial accounts built on Spark since June 2026. The recovery phrase stays on the user's phone, and the name@blink.sv address stays the same.9 The exit on-chain exists in the protocol, but not yet among the app's buttons.11

In Italy, today, Blink only opens self-custodial accounts.12

The till needs the address to answer the question “has it been paid?”, even with the phone switched off. Our tests:

Wallet Address Tested on Answer at the till
Blink, self-custodial name@blink.sv 11 November 2026 “Paid”, even with the phone switched off13
Glow by Breez @breez.tips, now @breez.cash 12 and 17 November 2026 “Paid”;14 on 17 November Pizzeria Le Fucine, the first shop on the new till, received a test payment with it;15 not yet tried with the phone off
Cake Wallet @cake.cash 12 November 2026 “Paid”; not yet tried with the phone off14

With Blink there were two invoices for 21 sats, paid from a Lightning wallet that isn't on Spark: with Blink closed and the phone in aeroplane mode, the “paid” answer came a few seconds after the payment, and when the phone came back on the sats were there. The shop form checks it anyway when you enter the address. Glow by Breez and Cake Wallet are two wallets on Spark and they answer “has it been paid?” from their own domain: if you try the payment with the phone switched off, following the steps in The first wallet, tell us how it went.

Which wallet to use is up to whoever uses it, and lesson 3 tells you which ones we recommend.

The trust worth knowing about

Every technical choice leans on someone. With Spark, here's who.

  • Reduced trust, not zero. Blink says so too.9 You're counting on the operators not all colluding, or all being coerced, to give a coin back to whoever held it before.
  • A handful of operators, who keep fast payments running and stand guard against anyone trying to exit with a coin they've already handed over.16 If they stop, fast payments stop and the exit remains.
  • Custodial or not? It depends on how you count the signatures. In October 2025 WalletScrutiny classified a wallet on Spark as custodial, because the operators have to sign every handover, and confirmed it in October 2026.17
  • The exit is the safety net. It costs money and takes practice, so it's worth it for sums that aren't too small: if you only hold a little, you're effectively relying on the operators.

The other roads to follow

Each one leans on someone. What changes is who, and for how long.

Road Who you rely on
Spark A group of operators: one honest one is enough, and the exit remains
Ark A single server, until the coins are renewed
Liquid The majority of a 15-member federation
Self-custodial Lightning wallets Whoever opens the channels, like ACINQ for Phoenix
A node of your own The longest road, and the one most your own
Deep dive: Ark

Ark was proposed by Burak Keceli in May 2023.18 There too the coins live outside the ledger, as pre-signed transactions that can be broadcast if needed: they're called VTXOs. A server gathers users into rounds, say every hour, and anchors them to the chain with a single transaction.19

Compared with Spark, three things change:

  • One server, not a group. Each Ark has a single operator. For a payment you've received, the same logic as statechains applies: it's safe as long as whoever paid you, and whoever paid them, don't collude with the server, and only until the renewal.20
  • Coins expire. A VTXO lasts a few weeks, 28 days on Second's server, and before it expires it has to be renewed in a new round. If you don't, the server gets the chance to take the amount back.19 The renewal can be delegated to someone else, without handing them the funds.21
  • Covenants. Ark works today without changing Bitcoin, but it needs you to be online at the right moment. With a new opcode like CTV, BIP-119, it would need fewer signatures and less presence.22 CTV is still a proposal and isn't active.23

There are two main implementations, both with free MIT-licensed code. Arkade, by Ark Labs, has been in public beta on the real network since October 2025.24 Bark, by Second, got there on 9 June 2026.25

Deep dive: Liquid

A chain alongside Bitcoin, run by a federation of 15 members. To get bitcoin out you need 11 of them. To get in you wait 102 blocks, about 17 hours.26 You rely on the majority of the federation, which signs the withdrawals.

Deep dive: self-custodial Lightning wallets

The keys are yours and the channels are real. Phoenix, by ACINQ, opens and enlarges a channel with ACINQ by itself, and it's free software.27 ACINQ can't spend: you rely on it to open the channels, and payments go through its node. Breez SDK, the toolkit others build wallets with, now recommends its Spark version, and the Greenlight one has been retired.28

The longest road, and the one most your own, is running your own node: A node of your own.

A node of your own The software


  1. Lightspark, “Introducing Spark”, Lightspark Sync, November 2024. ↩

  2. Spark, “Spark is Live”, 29 April 2025. ↩

  3. Spark documentation, FAQ, read on 3 November 2026. ↩↩

  4. Ruben Somsen, “Statechains”, Scaling Bitcoin, Tokyo 2018, and “Statechains: Non-custodial Off-chain Bitcoin Transfer”, 4 June 2019. ↩

  5. Spark, “What is Spark? A Bitcoin Layer 2 Built on Statechains” and documentation, Core concepts. ↩

  6. Spark documentation, FROST signing. ↩

  7. Spark documentation, Trust model. ↩

  8. Spark documentation, Unilateral exit. ↩

  9. The Valley's tests with Spark SDK 0.14.0 on Lightspark's test network, 1 November 2026. Internal notes. ↩

  10. Bitmentor, “Choosing wallets for your community” (docs/wallets.md), in the bitmentor repository: on 12 November 2026 a Blink address, a Glow one and a Cake Wallet one (blink.sv, breez.tips, cake.cash) passed the site's check, with verify on the address's domain and open CORS; only Blink was tested with the phone switched off. Read on 12 November 2026. ↩↩

  11. In production, 17 November 2026: Pizzeria Le Fucine, the first shop to move from the old till to the new one, took over its shop with its email, connected a @breez.cash address and opened the till, in just over a minute. The test payment that followed went through, according to those present: payments go from the customer to the shop's wallet, and the site doesn't see them. It was not tried with the phone off. ↩

  12. Spark documentation, Limitations. ↩

  13. WalletScrutiny: “Self-Custody Claims Review” of 9 October 2025, verdict confirmed on 30 October 2026. ↩

  14. Bitcoin Optech, newsletter of 31 May 2023; the Ark page collects what followed. ↩

  15. Second, documentation, “Intro to Ark”. ↩↩

  16. Second, documentation, “VTXOs”. ↩

  17. Ark Labs, “Adios, Expiry”, 16 July 2025. ↩

  18. Bitcoin Optech, newsletter of 4 April 2025, on “The Ark case for CTV” by Steven Roose. ↩

  19. BIP-119, status “Draft”; what followed on Bitcoin Optech. ↩

  20. The Block, 21 October 2025; the server is arkd, MIT licence. ↩

  21. Bitcoin Magazine, 9 June 2026; the code is bark, MIT licence. ↩

  22. Liquid, “How Liquid works”. ↩

  23. Phoenix on GitHub, Apache 2.0 licence; the single channel in ACINQ, “Phoenix splicing update”, July 2023. ↩

  24. Breez SDK on Spark; the earlier versions point there: Greenlight and Liquid. ↩