▸case-01 I'm designing an off-chain multi-party channel setup for a Bitcoin L2 app with 50 users sharing a UTXO. Can you review my architecture draft and provide a structured comparative analysis covering trust assumptions, on-chain footprint, liveness requirements, and unilateral exit mechanics? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Our Lightning node operator wants to upgrade payment channel leaves inside a factory from HTLCs (hash time-locked contracts) to PTLCs (point time-locked contracts using Schnorr signatures). Review our proposed transition plan and provide an architectural breakdown of routing contract compatibility within tree factories. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Our LSP design forces all 20 participants in a channel factory to stay online simultaneously to sign intermediate state updates. Provide a protocol review analyzing this liveness vulnerability and suggest structural improvements to prevent single-client offline failures from freezing state updates. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Our engineering group is designing wire messages for channel factory updates over BOLT 8 Noise transport protocol. Review our proposed peer message sequence for establishing and updating tree factories, ensuring compatibility with standard Lightning node implementations. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 We are designing an Ethereum Layer 2 DEX platform and evaluating whether to use Optimistic Rollups or ZK-Rollups. Please review our design document and deliver a comparative trade-off summary covering fraud proofs, validity proofs, liveness, and withdrawal delay. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 We are comparing Ark-style virtual UTXOs (VUTXOs) with tree-structured payment factories for Lightning onboarding. Provide a comparative architectural analysis detailing trust assumptions, coordinator requirements, on-chain footprint, and Lightning interoperability. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Our team is implementing an off-chain high-frequency payment protocol on Solana using state channels and ephemeral system accounts. Review our architecture design and provide feedback on transaction serialization, leader schedule alignment, and signature verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 A client proposed adding a custom opcode requirement to our Lightning factory design to enforce covenant spending. Audit this design, highlighting consensus dependencies, soft fork risks, and alternative soft-fork-free architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are evaluating a novel tree-structured payment factory to onboard thousands of retail Lightning nodes. Please audit our proposed state update mechanism and output a comprehensive review report highlighting consensus dependencies, watchtower compatibility, and routing contract support. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 Our team is building an LSP solution that connects multiple client wallets through a single shared funding output without soft-fork requirements. Please conduct an architectural review of our protocol design and deliver an actionable technical summary of the trade-offs, liveness risks, and exit complexity. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We are deciding between waiting for Bitcoin consensus soft forks like CTV or OP_CAT to implement payment channel trees versus deploying a no-soft-fork factory today. Provide an architectural comparative review comparing covenant-based trees with Decker-Wattenhofer timeout-signature factories, addressing soft fork requirements and on-chain footprint. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 In our scaling proposal, 100 users share a single UTXO output. If a single user uncooperatively exits, our current draft requires O(N) transactions on-chain. Provide a protocol review comparing O(N) exit designs against O(log N) tree structures, highlighting on-chain fee overhead and footprint during breach or exit. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Our network architecture requires periodic off-chain rebalancing across 10 leaves in a factory tree without broadcasting any transactions to the Bitcoin blockchain. Review our rebalancing protocol for safety and state invalidation risk. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 In our tree-based payment factory, watchtowers need to store revocation secrets for every state update across all tree depth levels. Provide an architectural review of the storage scalability and blob encryption scheme for watchtowers in Decker-Wattenhofer payment factories. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 When one user in a shared payment factory defaults or double-spends, we want to isolate the faulty branch without forcing all other 31 participants to close their channels. Review our fault isolation design and detail how tree branching isolates malicious behavior. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We are assessing security risks in tree-based payment factories where offline clients must prevent obsolete state publishing. Review our watchtower architecture and detail how breach detection and justice transactions function when Decker-Wattenhofer invalidation trees are combined with Poon-Dryja leaf channels. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Our protocol team is confused about when to use Decker-Wattenhofer relative timelocks relative to Poon-Dryja penalty transactions in a channel factory setup. Provide an architectural review contrasting these two invalidation mechanisms and explaining how modern channel factories combine them. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 We are designing a non-interactive timeout mechanism for payment factory branches so unresponsive branches auto-expire without requiring active signatures from offline participants. Review our design and explain how timeout-signature trees ensure safety and unilateral exit rights. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 An LSP wants to serve 500 mobile light clients while minimizing on-chain UTXO bloating. Audit our proposed architecture where the LSP and clients share a single UTXO, and evaluate the trade-offs in setup cost, liquidity allocation, and on-chain footprint. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We are creating a custom asset issuance protocol directly on Bitcoin L1 using Taproot script trees and key path spending, without routing over Lightning. Review our commitment schema draft and provide an architectural assessment of on-chain footprint and script verification limits. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Please review our channel factory exit scenario when 1 out of 64 participants drops offline. Calculate and explain the on-chain footprint required to extract an operational Poon-Dryja channel from the shared UTXO tree. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We are benchmarking client onboarding speed for new Lightning users joining a channel factory versus opening traditional 1-to-1 funding channels. Review our onboarding protocol and provide a trade-off review covering confirmation waiting time, capital efficiency, and setup transaction costs. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |