🏷️ Categories: bitcoin-dev
quoting naddr1qq…zhv5📝 Summary: Payment pools and channel factories face limitations in interactivity, affecting user fund security. Proposed solutions include introducing a coordinator or partitioning balances, but these may not be economically practical. A potential solution is to prevent off-chain group equivocation by editing the funding utxo to allow for registration of new off-chain subgroups. CoinPool's idea of including user pubkeys and balance amounts in Taproot leaves could be used for privacy-preserving payments and contracts. OP_EVICT requires participant cooperation for a single participant to withdraw funds, which may not be safe. TLUV or MERKLESUB offer more flexibility, but no sound covenant proposal combines TLUV and EVICT-like semantics. The best direction to solve interactivity issues is still uncertain.
👥 Authors: • ZmnSCPxj ( ZmnSCPxj [ARCHIVE] (npub1g5z…ms3l) ) • Antoine Riard ( Antoine Riard [ARCHIVE] (npub1vjz…x8dd) )
📅 Messages Date Range: 2023-09-25 to 2023-09-26
✉️ Message Count: 3
📚 Total Characters in Messages: 21373
Messages Summaries
✉️ Message by Antoine Riard on 25/09/2023: Payment pools and channel factories face limitations in interactivity, affecting the security of user funds. Proposed solutions include introducing a coordinator or partitioning balances, but these may not be economically practical. A potential solution is to prevent off-chain group equivocation by editing the funding utxo in a way that allows for the registration of new off-chain subgroups. CoinPool's idea of including user pubkeys and balance amounts in Taproot leaves could be utilized for privacy-preserving payments and contracts.
✉️ Message by ZmnSCPxj on 26/09/2023: The email discusses the issue of interactivity constraints in payment pools and channel factories and proposes a solution to mitigate equivocation of off-chain balances.
✉️ Message by Antoine Riard on 26/09/2023: OP_EVICT requires participant cooperation for a single participant to withdraw funds, which may not be safe. TLUV or MERKLESUB offer more flexibility. No sound covenant proposal combines TLUV and EVICT-like semantics. The best direction to solve interactivity issues is still uncertain.
Follow Bitcoin Mailing List (npub15g7…08lk) for full threads
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.