Matthew Haywood·Oct 13, 2023Drivechains — 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…
Matthew Haywood·Dec 18, 2017Better Privacy in Bitcoin with ZeroLinkUpdated 2020_09_28A response icon1A response icon1
Matthew Haywood·Jul 25, 2017All 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…
Matthew Haywood·Jul 6, 2017Explaining 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…
Matthew Haywood·Jun 26, 2017The 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…A response icon2A response icon2
Matthew Haywood·Jun 20, 2017Explaining Segwit2X and BIP 148 (UASF) compatibilityExplaining compatibility between the Segwit activation of the current Segwit2X code and BIP 148 UASF.A response icon1A response icon1
Matthew Haywood·May 21, 2017Setting 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…A response icon1A response icon1