Author: ZmnSCPxj 2022-03-09 14:42:36
Published on: 2022-03-09T14:42:36+00:00
The conversation 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. The complexity of ST was shown through a state diagram by Jeremy Rubin, causing someone to joke about using `OP_RING` instead of implementing `OP_CTV`. Criticism of ST is discussed and it is stated that users with mining hashpower can block the initial Speedy Trial, which should cause developers to stop and listen. If they fail to do so, a counter-UASF can be written, which rejects blocks signalling for the upgrade. Clients using the initial Speedy Trial code will follow the chain with better hashpower. Therefore, users who want for/against a particular softfork can resist the Speedy Trial and even run a counter-UASF if developers release a UASF `lockinontimeout=true` later. Overall, the conversation emphasizes the importance of understanding the mechanisms of activation and how users can actively resist them. The IRC logs are linked for reference, and the idea of blindly trusting individuals like Jeremy Rubin is discussed.
Updated on: 2023-06-15T17:51:19.112543+00:00