I wasn't involved at all in the discussions, but the cryptopunk in me wonders if this isn't malice. Running out of DB entries in the client can be predicted wit

I wasn't involved at all in the discussions, but the cryptopunk in me wonders if this isn't malice. Running out of DB entries in the client can be predicted with reasonable accuracy. "Accidentally" slip in this bug, and "fix" it in a future version. Then time a major transaction to coincide with the fork you know will happen, and bam! Engineered transaction reversal. That would be one great hack. But my imagination is probably just getting the best of me.