SuperScalar: Laddered Timeout-Tree-Structured Decker-Wattenhofer Factories

Posted by ariard

Sep 17, 2024/07:28 UTC

The timeout condition in question requires clients to establish an online presence before a predetermined deadline, subsequently necessitating their exit from the mechanism. This exit strategy can be executed either independently by the client or in collaboration with the Lightning Service Provider (LSP). However, this approach encounters significant challenges in scenarios involving widespread off-chain force-closures, as detailed under the "Forced Expiration Spam" section within the lightning paper. Specifically, the implementation of a timeout condition may inadvertently trigger a large-scale migration to on-chain transactions. Such a shift intensifies competition for the already limited block space available on the blockchain. Moreover, there is no protocol-level assurance that the LSP will be online at the critical moment when the timeout expires, which is essential for batch processing of exits. This lack of guaranteed LSP availability at crucial times adds an additional layer of complexity to managing exits under the timeout condition.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback