Quote from: taltamir on March 14, 2013, 02:43:04 PM

Quote from: evilpete on March 14, 2013, 03:52:07 AM

Quoting what I said above: "Upgrade" includes upgrading their bitcoind/bitcoin-qt etc to 0.8+ OR setting the DB_CONFIG entries mentioned above.

AND not OR.
There is no point in setting anything in 0.7-;
0.7 can NOT make a block that 0.8 rejects.
0.7 AND 0.8 can both make blocks that 0.7 will reject due to a bug in 0.7-.
0.8 can be configured to only make blocks that are accepted by everyone.

.. and 0.8 won't make a block by default that is rejected by 0.7. Miners had to explicitly raise their -blockmaxsize, which is what happened. It was suggested on a thread in the miners forum and a few folks tried it out. And we saw what happened.

Quote

Quote

Releasing a 0.8.1 won't fix anything. All that it can do is clamp the value that you can set the max generated block size to. The problem is the code is still there, and so is 0.8. If somebody wants to compile a custom 0.8.1 from source with the limit at 1MB, they can.

Default configuration is included in the source code and as such anyone who compiles an 0.8.1 without explicitly altering said code would get the new configuration.

You're missing the point. I'm not talking about the default configuration, which is "safe" by default everywhere. 0.8 is safe by default. The problem is when somebody maliciously makes a bdb-buster block because they either want to cause trouble, or because they figure out a financial advantage to do so.

Quote

Quote

If more than 51% of the hash power applies the DB_CONFIG fixes (even on 0.7) then they'll accept it and build on it.

This wont cause trouble to anyone except for themselves, they will be generating blocks that are rejected by the chain until and unless 51+% are using 0.8+, at which point those using obsolete bugged version are forced to upgrade.

Read what I said. The only thing preventing another bdb-buster fork is that 51% of the hashpower are running a broken 0.7 on purpose. If that changes, eg: miners apply the fixes to 0.6 or 0.7, or a ton of asic solo miners turn on at 0.8, then we're back in fork territory when somebody wants to cause trouble. If the miners fix their bdb config they'll behave just like 0.8 next time a killer block comes along.

But the last thing we need is more people downgrading to 0.7. It just delays fixing this land mine.