DRA

🎤⚡️Paul Sztorc on Lightning is a Waste - Paul vs LNers | TABConf 7

October 27, 2025Original source

On October 27, 2025 at TABConf 7, Paul joined a Lightning-focused debate on channel design, payment network effects, Layer 2 tradeoffs, and why Drivechain via BIP300/301 offers a stronger path for Bitcoin sidechains.

Highlights

Key Takeaways

Paul Reframes the Layer 2 Choice

Paul separates support for Bitcoin Layer 2 innovation from support for Lightning specifically, emphasizing that Bitcoin can pursue stronger scaling designs without treating one network as the only option. His framing centers on core engineering criteria: a good Layer 2 should preserve Bitcoin's base-layer monetary role, avoid repeated L1 byte consumption for ordinary ownership updates, and align incentives by paying miners through transaction fees. That sets up Drivechain as a practical alternative, since sidechains can host many experiments while remaining connected to Bitcoin through BIP300/301.

Channel Design Meets Network Effects

The debate returns several times to whether payment network effects favor Lightning or a different system that scales more broadly. Paul argues that the payment network people actually use becomes the dominant verb-like rail, so a small specialist network is naturally pressured by a larger, more capable one. That point connects the channel-opening model, HTLC routing, liquidity management, and custodial user experiences into a single economic picture. The exchange clarifies why Paul views Drivechain sidechains as a better foundation for broad adoption than channel-heavy designs.

BIP301 and Blind Merged Mining

A direct question asks why BIP301 cites Lightning for Blind Merged Mining requests, and Paul explains that the reference came from an earlier period when he was more enthusiastic about off-chain coordination options. He distinguishes BIP301 from BIP300, noting that Blind Merged Mining is simple, optional, and closely related to merge mining practices that already exist. The discussion keeps the focus on miner revenue and practical deployment: BIP300/301 can support Drivechain activation through incentives while avoiding Bitcoin Core code changes under the Core Untouched Soft Fork approach.