Optimistic payout in BitVM implementations like Citrea?

In the discussion regarding the security and operational mechanisms of cryptocurrency transactions, particularly in the context of deposit and withdrawal processes on blockchain bridges, a critical point is made about the nature of UTXOs (Unspent Transaction Outputs). When a user makes a deposit followed by a withdrawal, the UTXO utilized for the withdrawal is not necessarily the one created during the deposit. Instead, withdrawals operate on a First-In-First-Out (FIFO) basis, where each withdrawal corresponds to a deposit in sequence. This necessitates that all deposits be presigned by a consistent set of signers, ensuring uniform trust assumptions across all transactions. This setup is crucial because a withdrawal today might be executed against a deposit made much earlier, meaning the signers of that original deposit are also the signers guaranteeing the current withdrawal.

The conversation further explores the implications of signer participation and the robustness of co-signing protocols in these systems. The argument is presented that broader participation in signing processes potentially strengthens the system’s security, contrasting with closed participation, which could pose significant risks. Additionally, the dialogue mentions ROAST—a protocol designed for robust co-signing—as an example of efforts to enhance security measures, though its practical application and testing remain uncertain.

Moreover, the discussion critiques certain design choices within these systems, particularly those that appear largely cosmetic and do not substantially contribute to trust or security. For instance, the BitVM design was mentioned as lacking substantive trust inheritance, as it can be bypassed, undermining its theoretical benefits. The dialogue underscores the necessity for openness in signer identities and participation to prevent concentrated attacks and ensure diverse, decentralized control over transaction verification, hence enhancing overall system integrity and user trust. This approach is advocated over more restrictive configurations, which limit verification to a smaller group of participants, thereby increasing vulnerability to targeted attacks and long-term security threats.