Good ideas and conversation. No ads, no tracking. Login or Take a Tour!
The fork has not yet been implemented, nor has there been much agreement about if it is needed, or how to do it. Thus, this madness. Also, this isn't just about the blocksize, but the effect of many duplicate transactions clogging up the memory pool on a node. EDIT: I made a related post the other day. BitcoinXT, the bigger blocksize fork (the max blocksize change has not been implemented) has a fix for what is happening now: