blocks are full NOW

there are already other threads about this

https://bitcointalk.org/index.php?topic=339257.0
https://bitcointalk.org/index.php?topic=338999.0
https://bitcointalk.org/index.php?topic=338793.0
https://bitcointalk.org/index.php?topic=338452.0

most pools create 250kb blocks only

please do something!!!

> release bitcoin 0.8.6, remove stupid -blockmaxsize
> transactions > 0.01 BTC are processed before transactions < 0.01 BTC
   tell people to not send transactions < 0.01 BTC, bitcoin is not ready for micro payments yet
> transactions not confirmed after 12 hours are removed from mempools automatically
> after 12 hours there must be a cancel/overwrite mechanism

at least tell people/merchants what to do if they have never confirming transactions

massive unconfirmed transactions are coming!!!

I know you devs are busy selling coins, but you owe the community solving this problem at least, before buying your ferrari.

In the last few weeks every time I go to blockchain.info I see a lot of 243kB blocks.

243kB = 250000 bytes



This makes sense to me before May 15, because maximum blocksize was 500kb,
and until half of the block price is normal, then price is bigger if block is more than 50% full.

But why still the limit at 250000 bytes and not 500000 bytes even after May 15?

When someone pulls of an 51% Attack, this means that the last x blocks including all transactions are going to be invalid. Thats the problem.

Short:
We just should forbid overwriting more than 10 blocks. If that happens user manually selects prefered chain.

Long:
Every bitcoin-client no mather if bitcoind or gui exactly knows when such an attack is going to happen. This is when more than the last 10 blocks are going to be replaced. (You can change the number 10 to maybe 100 or something else if you want, its just an example, but I think we should keep this number as low as possible).

If that happens the bitcoin client raises an alarm and goes into freeze mode, meaning it is not accepting any more blocks until the right block-chain has been manually selected.

Basically there are 2 cases:
1) only you and some others got the alarm, because of internet problems you were accidentally building a bitcoin-subnet. In that case just continue with the real chain and you are good. This to happen is very unlikely, because you and a small number of other clients have to mine 10 blocks by yourself. You would needs weeks to mine those blocks and you would realize much earlier, that something is wrong with your internet connection.

2) A real 51% attack. Every client goes into freeze mode. The attacker cannot take advantage from the attack. The bitcoin-develeopers release a new version with the last correctly mined block as a harcoded block-hash. Everyone downloads the new version and continues as normal.

After the attack everybody would know that someone bad really has 51%. Everybody would increase the minimum confirmations to 10.

Feedback appreciated.