{"push_id":1414508309,"size":1,"distinct_size":1,"ref":"refs/heads/excessiveBlocks","head":"781740a6d4773efa357165e6e709c414c7611e5b","before":"1e92d5db46e784c1ff5b1800cf9af633b5abb3ae","commits":[{"sha":"781740a6d4773efa357165e6e709c414c7611e5b","author":{"name":"TomZ","email":"11f03a0d46404ec40a9c3561f383b9ea98b4b209@freedommail.ch"},"message":"Make Classic use excessive-block sizing strategy.\n\nThis removes all traces of BIP109, the 2MB blocksize proposal.\n\nIn its pace I insert the concept of market equilibrium based blocksizing.\nTechnically this means;\n\n* We remove from the consensus rules the max-block-size.\n* We introduce a command-line-argument that defines the max-block-size.\n\nClassic chose to use -blocksizeacceptlimit as a desciptive name, but for\ncompatibility with BU has an alias for its -excessiveblocksize.\nValues are in whole megabytes, but floating point values are accepted with\nan accuracy up to 100KB.  So, you can have \"3.5\" as blocksizeacceptlimit.\nThis value will be put in the coinbase-comment as \"EB3.5\" in this example.\n\nIn short;\nMiners can continue to use the -blockmaxsize argument or bitcoin.conf\nsetting to limit the size of blocks they generate!  All nodes can also use\nthe `-blocksizeacceptlimit` option to limit the size of the blocks accepted\nfrom (other) miners.","distinct":true,"url":"https://api.github.com/repos/zander/bitcoinclassic/commits/781740a6d4773efa357165e6e709c414c7611e5b"}]}
{"actor":{"display_login":"zander"}}