Matthew HaywoodDrivechains — potential issues as they relate to BitcoinAn overview of some possible issues with drivechains (a shorthand term for BIP300/BIP301) that may impact the Bitcoin network itself…Oct 13, 2023Oct 13, 2023
Matthew HaywoodAll roads lead to Segwit — Segwit2x, BIP 91 Segsignal and UASFI have written previously about Segwit2x, UASF and the road to Segwit activation. Since publication of that article bit 4 has locked in and…Jul 25, 2017Jul 25, 2017
Matthew HaywoodExplaining the Segwit2x Hard Fork and Bitmain’s UAHFDiscussion within the Bitcoin community is starting to shift from the activation of Segwit to focusing on the potential likelihood of…Jul 6, 2017Jul 6, 2017
Matthew HaywoodThe Road to Segwit Activation — UASF, Segwit2x and Segwit Signalling ExplainedAs opposed as the supporters of each solution may be, UASF BIP 148 and Segwit2x are essentially trying to do the same thing — activate…Jun 26, 20172Jun 26, 20172
Matthew HaywoodExplaining Segwit2X and BIP 148 (UASF) compatibilityExplaining compatibility between the Segwit activation of the current Segwit2X code and BIP 148 UASF.Jun 20, 20171Jun 20, 20171
Matthew HaywoodSetting up a Raspberry Pi running Raspbian as a Bitcoin UASF BIP 148 node — compiling from source…The User Activated Soft Fork (BIP 148) depends on the support of users. By running a UASF BIP 148 node you can support the drive to…May 21, 20171May 21, 20171