Published on: 2022-03-10T11:28:55+00:00
The conversation in the communication thread revolves around the concept of Speedy Trial (ST) and its implementation in relation to CTV. ST is a short softfork attempt with `lockinontimeout=false`, and if it fails, developers decide whether to offer a UASF `lockinontimeout=true` version or not. Jeremy Rubin demonstrated the complexity of ST through a state diagram, leading to a joke about using `OP_RING` instead of implementing `OP_CTV`. Criticism of ST is discussed, highlighting concerns about miners and users having less opportunity to oppose a malevolent change imposed by miners. The trust factor of developers is also brought up, with one participant expressing distrust towards Jeremy Rubin, although acknowledging that this is subjective and off-topic.The conversation further explains that users with mining hashpower can block the initial Speedy Trial, which should prompt developers to listen to their concerns. If developers fail to do so, a counter-UASF can be written, rejecting blocks signaling for the upgrade. Clients using the initial Speedy Trial code will follow the chain with better hashpower. Therefore, users who want to resist or support a particular softfork have the ability to resist Speedy Trial and even run a counter-UASF if developers release a UASF `lockinontimeout=true` later. The conversation emphasizes the importance of understanding activation mechanisms and how users can actively resist them. In another discussion on the bitcoin-dev mailing list, Jeremy Rubin shares updates on various topics. Firstly, Sapio now has experimental Taproot support, and assistance is needed for reviewing Rust-bitcoin. Secondly, he explains the concept of Transaction Sponsors and why it doesn't have a BIP number assigned. Thirdly, James' Vaults Post is mentioned, which explores recursive CTV vaults. Fourthly, there is a conversation about adding more power to protocols and proposed solutions for infrastructure issues related to flexible covenants. Finally, there is a general discussion on naming conventions and forking, with some participants expressing concern about Speedy Trial and proposing unique names like "Hot Tub Coin Machine" and "OP_DOTHETHING".The Bitcoin Core Tech meeting on March 8th, 2022, covered several topics. Firstly, Sapio now has experimental Taproot support, and assistance is needed for reviewing Rust-bitcoin's pull request for MuSig support. Secondly, the meeting discussed transaction sponsors and their differences from RBF/CPFP, as well as the absence of a BIP number assigned to them. The third topic was James' Vaults post, which explores the customization of vaults. Fourthly, the meeting discussed the potential dangers of adding too much power to scripts and the difficulty of generating a transition function for more flexible covenants. Finally, there was a general discussion on naming protocols and forking, with participants expressing concerns about Speedy Trial and suggesting unique names for projects.
Updated on: 2023-08-02T05:50:24.597524+00:00