I'm the guy flooding the mempool btw - I'm trying out NicholasDoriers experiment, on testnet. I had to shut it off since it's not filling up as quickly as I'd like. It was being made easier by AntMiner or whoever not filling blocks - I didn't think my laptop could keep it up.
Anyway, I guess if you posted this topic because you were waiting for a transaction to confirm, it's a sign of what'll happen when mainnets blocks are full.
Good. Continue. Start doing it on mainnet if possible. There should be some kind of fund. An address where people can send bitcoins to that will be used to spam the network. Make them all suffer.
To give a little context on why we are unhappy:
All API services for testnet are breaking because of this. Chain.com, Blockcypher, Block.io. Blocktrail seems to be the only one to be keeping up but they dont have a proper API to make curl calls. The APIs show the following errors:
- No notification on new transaction
- Incorrect balance (up to negative balances) for addresses
- Denial of tx broadcast because "referenced transaction not known"
These issues obviously come from the Bitcoind instances dropping transactions and the databases that the APIs are using miss entries. I would say an API should be better than this, but whatever.
This test is exactly what we needed. It shows how crucial a fast decision on the blocksize issue is.