{"type":"rich","version":"1.0","author_name":"npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m","author_url":"https://nostr.ae/npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-07-30\n📝 Original message:What, if any, methods would be used for miners to communicate their\nupgrade?\n\nGreg\n\nOn Thu, Jul 30, 2015 at 10:25 AM, Pieter Wuille via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hello all,\n\u003e\n\u003e here is a proposal for long-term scalability I've been working on:\n\u003e https://gist.github.com/sipa/c65665fc360ca7a176a6\n\u003e\n\u003e Some things are not included yet, such as a testnet whose size runs ahead\n\u003e of the main chain, and the inclusion of Gavin's more accurate sigop\n\u003e checking after the hard fork.\n\u003e\n\u003e Comments?\n\u003e\n\u003e --\n\u003e Pieter\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150730/846a30c7/attachment-0001.html\u003e"}