# SuperScalar: Laddered Timeout-Tree-Structured Decker-Wattenhofer Factories With Pseudo-Spilman Leaves **URL:** \ **Category:** Protocol Design\ **Tags:** lightning, factory\ **Created:** [November 4, 2024, 3:40pm UTC](https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories-with-pseudo-spilman-leaves/1242 "2024-11-04T15:40:11Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![8144225309](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/8144225309/32/1776_2.png) [@8144225309](https://delvingbitcoin.org/u/8144225309)\ **Post date:** [July 13, 2026, 9:44am UTC](https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories-with-pseudo-spilman-leaves/1242/3 "2026-07-13T09:44:33Z")
This design now has a working implementation. The report includes signet exhibits covering the factory lifecycle, the pseudo-Spilman leaves, old-state poisoning, and more: > [@SuperScalar: an implementation report](https://delvingbitcoin.org/t/superscalar-an-implementation-report/2705): > > SuperScalar puts many self-custodial Lightning clients behind a single on-chain UTXO, with no soft fork and no trust in the coordinating LSP. It is @ZmnSCPxj’s design ([SuperScalar with pseudo-Spilman leaves, t/1242](https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories-with-pseudo-spilman-leaves/1242)); this post reports a working implementation. Everything below ran on regtest or signet. There has been no external audit, and mainnet is deliberately behind an explicit --i-accept-the-risk flag. Code (C, MIT, at [v0.2.0](https://github.com/8144225309/SuperScalar/releases/tag/v0.2.0)): [github.com/8144225309/SuperScalar](https://github.com/8144225309/SuperScalar). Four binaries: superscalar… --- _[View the full topic](https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories-with-pseudo-spilman-leaves/1242)._