Some of you may remember an article I published years ago, Understanding Lightning Network Using an Abacus
The key idea is simple: Spark doesn’t move bitcoin on-chain between users. It replaces who holds the valid authorization to spend them. The on-chain bitcoin doesn’t move. What changes is which two puzzle pieces fit together. To keep this explanation focused, I intentionally didn’t get into Spark’s unilateral exit mechanism. It’s an important part of Spark’s security model, but it would distract from the core idea I want to convey here. What matters is that Spark is not a system where users are permanently dependent on the SE. While everyday transfers rely on joint authorization, Spark also provides users with a way to spend their funds on-chain without requiring the cooperation of the SE. That escape hatch exists by design, it’s just outside the scope of this explanation. About Author
