Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM(<div class="post">Spent transactions can be forgotten (though they currently aren't). That would prevent your sending coins back and forth from having a big impact on block size.<br/><br/>The transaction inclusion issue is fixed by increasing fees and making non-generators aware of the current blocksize. The fees after 250KB should increase faster.<br/><br/>I think this attack would be more difficult on the real network because of the differing fee schedules. You'll have half of the network including your transactions and half of the network not including them. Half of the network considers a block "filled" at 500KB, and half at the network-enforced maximum of 1MB.<br/><br/><div class="quoteheader">Quote</div><div class="quote">Or maybe the entire size exceeded the 1 MB limit.</div><br/>You're right. That message is produced if fees bring a transaction over your balance, and the fee when the blocksize is over 500 KB is 21 million BTC. You wouldn't have gotten that if you weren't generating, since you wouldn't have known the current blocksize.</div> text/html