Protocol for zero-conf transactions

The discussion revolves around a newly proposed protocol for zero-confirmation transactions, which employs a co-signing server trusted by the recipient. This protocol is likened to existing two-factor authentication mechanisms such as the one used in Blockstream Green. However, it introduces a novel use of a connector output, ensuring that the recovery timelock only commences when a unilateral exit is initiated. This design aims to eliminate the need for periodic refreshes or redeposits of long-lived Unspent Transaction Outputs (UTXOs).

Critics of this protocol argue that it fundamentally resembles traditional financial systems like PayPal, relying heavily on a 2-of-2 multisignature setup. The concern raised is that this model requires users to depend excessively on a third-party server for executing "pre-signed change exits." This dependency could potentially compromise the integrity and autonomy of the transactions, as there are risks associated with the server's failure to perform as expected or becoming dishonest (equivocation). Such reliance transforms the system into what can be described as an "interpretive, permissioned spreadsheet" rather than a robust decentralized protocol.

Furthermore, contrasting views emphasize the superiority of using Layer 1 (L1) solutions where mathematical enforcement of policies is standard, as seen in technologies like Taproot. In such systems, the address itself represents the state, and the covenant directly embodies consensus mechanisms, negating the need for any trusted third-party intervention. This approach highlights the principle that if an asset requires human-operated servers to prevent issues like double-spending, it does not represent a true asset but rather an illusion. Critics advocate for the adoption of simpler, more foundational solutions that do not rely on potentially fallible external entities to guarantee transaction security and integrity.