Lightning’s scalability has hinged on Just-In-Time channels, which today require total trust in a single service provider like ACINQ's Phoenix wallet. This creates a centralizing force, locking users into one company’s infrastructure.
Thomas V, the founder of Electrum, proposes a system that makes the blockchain the referee. If a Lightning Service Provider receives a payment but refuses to open the channel, the user publishes the payment's pre-image to the chain, creating a public fraud proof. He argues this shifts the model from cooperative trust to adversarial verification.
“This isn't just about security; it's about regulatory survival. By removing the trust requirement, providers might avoid being classified as custodians.”
- Thomas V, Bitcoin Optech
The scheme adds economic skin-in-the-game: LSPs must commit and potentially burn bitcoin to establish a reputation. Fraud would burn their stake, making cheating more expensive than honest operation. Thomas contends even a 99% success rate is enough to deter institutional-scale fraud.
Simultaneously, developers are patching a privacy leak. Researchers found dual-homed nodes running on both Clearnet and Tor can be correlated via identical address timestamps, unmasking a user’s IP. The fix injects noise - likely by reporting older timestamps for Onion addresses - to break the fingerprint without cluttering the peer table.
This week's technical debt clearance saw Bitcoin Core finally merge PSBT version 2 after five years, enabling modular collaborative transactions. BIP 451 also standardized a dust disposal protocol, allowing users to batch worthless UTXOs into a single burn transaction to preserve privacy.
The moves collectively aim to make Lightning more trustless, private, and interoperable - essential steps if it hopes to rival traditional payment rails.
