{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-22\n📝 Original message:On Mon, Jun 22, 2015 at 02:18:19PM -0400, Gavin Andresen wrote:\n\u003e I promised to write a BIP after I'd implemented\n\u003e increase-the-maximum-block-size code, so here it is. It also lives at:\n\u003e https://github.com/gavinandresen/bips/blob/blocksize/bip-8MB.mediawiki\n\nIt's important that we see a wide range of realistic testing of what an\n8MB limit could look in the near future. An important part of that\ntesting is load testing.\n\nAs of writing the BIP above has no mention of what switchover rules will\nbe used for testnet; code floating around has August 1st 2015 as that\ndate. I propose we use August 1st 2013.\n\nThis switch over date should be set in the _past_ to allow for the\ncreation (via reorg) of a realistic full-load blockchain on testnet to\nfully test the real-world behavior of the entire infrastructure\necosystem, including questions like the scalability of block explorers,\nSPV wallets, feasibility of initial syncronization, scalability of the\nUTXO set, etc. While this is of course inconvenient - 2 years of 8MB\nblocks is 840GB worth of data - the Bitcoin ecosystem can-not afford to\nmake a change like this blindly.\n\nI'm sure with a $3.5 billion market cap at stake we can scrape together\nthe resources to voluntarily run a few hundred full-load full-nodes for\ntesting a change with the potential to destroy that market cap.\n\n-- \n'peter'[:-1]@petertodd.org\n00000000000000000b953816d4c31e79b04d5b075bcacb8cf20e54ee3b61c316\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/4f20e897/attachment.sig\u003e"}
