Lightning Sparks
summary
Spark combines state chains and payment trees so one on‑chain UTXO spawns many off‑chain leaves and supports 4,000 transfers per tree before renewal, but unilateral exit requires the wallet to publish a personal UTXO and roughly a dozen fee‑bumping transactions (uses pay‑to‑anchor in Bitcoin Core v29), wallets like Wallet of Satoshi and Blitz already integrate it, the operator SDK is MIT but the SSP server is closed, current model is a two‑of‑two federation and all activity is a public transaction ledger, with observed latencies around 6–8s.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:49Spark familiarity
- 3:13Spiral’s Spark journey
- 5:40Spark architecture
- 8:08Open source setup
- 9:54Payment trees and state chains
- 13:04Exit costs of payment trees
- 14:28Happy path fees
- 16:14Spark vs custodial solutions
- 18:00Business and regulatory benefits
- 20:07Spark design risks
- 21:56Privacy and public data
- 23:01Future improvements
- 24:46Key takeaways
- 25:27Q&A
