rich1.0npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nhttps://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nnjumphttps://nostr.ae📅 Original date posted:2015-12-08 📝 Original message:On Tuesday, December 08, 2015 11:40:42 PM Jonathan Toomim via bitcoin-dev wrote: > Agree. This data does not belong in the coinbase. That space is for miners > to use, not devs. This has never been guaranteed, nor are softforks a "dev action" in the first place. > I also think that a hard fork is better for SegWit, as it reduces the size > of fraud proofs considerably, makes the whole design more elegant and less > kludgey, and is safer for clients who do not upgrade in a timely fashion. How about we pursue the SegWit softfork, and at the same time* work on a hardfork which will simplify the proofs and reduce the kludgeyness of merge- mining in general? Then, if the hardfork is ready before the softfork, they can both go together, but if not, we aren't stuck delaying the improvements of SegWit until the hardfork is completed. * I have been in fact working on such a proposal for a while now, since before SegWit. > I don't like the idea that SegWit would invalidate the security > assumptions of non-upgraded clients (including SPV wallets). I think that > for these clients, no data is better than invalid data. Better to force > them to upgrade by cutting them off the network than to let them think > they're validating transactions when they're not. There isn't an option for "no data", as non-upgraded nodes in a hardfork are left completely vulnerable to attacking miners, even much lower hashrate than the 51% attack risk. So the alternatives are: - hardfork: complete loss of all security for the old nodes - softfork: degraded security for old nodes Luke