{"type":"rich","version":"1.0","author_name":"npub1uu2fve28mkg68uequseraz8gee7qg64733lr9r2g4c0xs5pmqnuslr4rpf","author_url":"https://nostr.ae/npub1uu2fve28mkg68uequseraz8gee7qg64733lr9r2g4c0xs5pmqnuslr4rpf","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-08-04\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n\n\nOn 08/04/2015 08:28 PM, Hector Chu via bitcoin-dev wrote:\n\u003e On 4 August 2015 at 14:13, Jorge Timón \u003cjtimon at jtimon.cc \n\u003e \u003cmailto:jtimon at jtimon.cc\u003e\u003e wrote:\n\u003e \n\u003e 2) It doesn't matter who is to blame about the current\n\u003e centralization: the fact remains that the blocksize maximum is the\n\u003e only** consensus rule to limit mining centralization.\n\u003e \n\u003e \n\u003e Repeating a claim ad-nauseum doesn't make it necessarily true. A\n\u003e block size limit won't prevent miners in the future from buying\n\u003e each other out.\n\u003e \n\nIt plays both ways, the technical list requires a proof of concept and\nsimulation upon which to base judgment going forward, else we'll just\nbe talking out our backsides (like certain people) without making any\nprogress.\n\nThe tools for simulation exist: Jorge Timon created a variable\nblocksize regtest PR here:\nhttps://github.com/bitcoin/bitcoin/pull/6382\n\nNo-one needs to postulate what different blocksizes imply  - anyone\ncan run a simulation and demonstrate what they're talking about.\n\n\u003e _______________________________________________ bitcoin-dev mailing\n\u003e list bitcoin-dev at lists.linuxfoundation.org \n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQEcBAEBAgAGBQJVwMFEAAoJEGwAhlQc8H1mo/EH/2USw5YUL/7sgFAsjpXdpcS+\n9XZ0M0AK4PNSo36GBBhjaF9rRa76FtK6Vt9nLe+7lgYmeHSkcQ65OLKfP47hCnsz\n9XfVR0n7nv+0TqHQKPcjm+WNBoVndKRHGEwNQoQw//bAmO4LOcmQCMXAkk9RfaKm\n4olay0nUmAFNqh/7wVOunOUFMJNIRpy/neAlFYxRAHBIJLcc0KQNiLqAHbzwPDZq\ne9kLjtIusWwLUCgHFvox01bIEOx+VYIxzjMVRz1MNGyRGwDweg7zk54WA48nYwmx\n70Ggdde9kiLytPDwB2ey/IRE4mv/4KS2zivJy36XAsjPExTNeGKxGeGfBqXNwSI=\n=aya4\n-----END PGP SIGNATURE-----"}