Not sure whether this has been posted here already but this site will help in determining the ideal fee to use for your transactions.
http://www.cointape.com/
I see that the current suggestion is to use around 41-50 satoshis per byte in order to get your transaction into the next block.
Topic: Stress test is underway - Watch your fees. - page 4. (Read 5210 times)
Blockchain is showing a backlog of 55MB right now so I guess that it is still on.
Good to hear that normal transactions are getting through. I read somewhere that
some miners are ignoring the dust spam.
Good to hear that normal transactions are getting through. I read somewhere that
some miners are ignoring the dust spam.
ohh no.. so much spam to send and the network is not confirming it all in the first block. the horror.. the horror.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
For those you might be in a hurry to get a confirmation it is a pain in the ass. Ignoring that won't make the problem magically go away.
Is it over or still going on? I sent various transactions in last 10 hours with regular fee and they all got confirmed normally, I just recently made some transactions (like an hour ago) with same amount of fee and they got through in normal amount of time as well. It was not like that in last stress test where some of my transactions were stuck for almost an hour. I think this one is not as powerful as the last one was.
But thanks for letting me know, I'll add more fee in the next ones just to be safe.
I hate these stress tests. it doesn't even have any benefit for anyone.
The "stress test" functions as a vaccine. There are short-term costs and long-term benefits.
Some wallets will develop features to help their users more easily manage/avoid stuck transactions in a bid for more users. Some exchanges will do a good job of riding the wave and attract more customers.
ohh no.. so much spam to send and the network is not confirming it all in the first block. the horror.. the horror.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
For those you might be in a hurry to get a confirmation it is a pain in the ass. Ignoring that won't make the problem magically go away.
ohh no.. so much spam to send and the network is not confirming it all in the first block. the horror.. the horror.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
nothing to see here. business is usual. only spammers have issue and complain about this. the resilient bitcoin network is dealing with spam properly. as for the backlog. it should just be dumped.
Meanwhile, here is what you can see on some other block explorers and monitors:
https://www.blocktrail.com/BTC/: 65k unconfirmed transactions, 112 MB mempool
https://tradeblock.com/bitcoin/: 89k unconfirmed transactions
https://www.blocktrail.com/BTC/: 65k unconfirmed transactions, 112 MB mempool
https://tradeblock.com/bitcoin/: 89k unconfirmed transactions
Why such a difference between these explorers?
If we get global adoption this will be the norm. So what's the issue?
It's called a stress test for a reason, it's designed to test out whether the network could even handle this many transactions at once and what should be done with it. Since it's a very scientific thing to do to try and break the blockchain like this hopefully it will help stop the bickering among the developers and let them find a proper solution to the blockchain size issue.
Thanks for the warning OP!
If we get global adoption this will be the norm. So what's the issue?
You guys are aware that Coinwallet isn't even spamming the network (well they are not spamming theoretically, but they still are spamming in the sense). They are just giving away free bitcoins located in many different addresses, they are providing private keys for these addresses. What's clogging up the network actually is human greed, many users are trying to claim these free coins. Essentially, Bitcoin users are destroying its own network at the moment.
No, this is purely a result of Coinwallet spamming the network. Consider the reason why the outputs they are "giving away" cause transactions to be prohibitively large. This is merely "phase 2" of a dust spam attack -- the default unspendable outputs (spam) are being cleared.
Spam or not how is this different than a fuck load of users trying to use the network at the same time? Technically speaking.
There's only one way to deal with spam. Ignore it.
Perhaps you have something more interesting to do with your time.
Perhaps you have something more interesting to do with your time.
The problem is that the bitcoin network and protocol is not designed to be capable of "ignoring" spam. So you can ignore it all you want but bitcoin is being hurt by it right now.
Maybe he was referring to the point that miners could ignore low fee transactions, and thus the spammers. But anyways it's definetly true that bitcoin is being damaged by this spam.
Even tho the network isn't still designed to defend itself against this now, it could be, but they choose not to.
The fix is simple: (quore from coblee)
"There's code in Bitcoin that says if someone sends a tiny amount of coins to an output, make sure that he pays the mintxfee. This makes sense because you wouldn't want someone creating "dust" spam by sending small amount of coins. BUT the code still only enforces the same mintxfee if you send to many small outputs. The fix is simple: require a mintxfee for each tiny output."
Why are we not doing the same fix on bitcoin ?
what fee must we use for the next month as this spam gets cleared?
Yes, that's their goal - a month of backlog :/
You guys are aware that Coinwallet isn't even spamming the network (well they are not spamming theoretically, but they still are spamming in the sense). They are just giving away free bitcoins located in many different addresses, they are providing private keys for these addresses. What's clogging up the network actually is human greed, many users are trying to claim these free coins. Essentially, Bitcoin users are destroying its own network at the moment.
No, this is purely a result of Coinwallet spamming the network. Consider the reason why the outputs they are "giving away" cause transactions to be prohibitively large. This is merely "phase 2" of a dust spam attack -- the default unspendable outputs (spam) are being cleared.
Meanwhile, here is what you can see on some other block explorers and monitors:
https://www.blocktrail.com/BTC/: 65k unconfirmed transactions, 112 MB mempool
https://tradeblock.com/bitcoin/: 89k unconfirmed transactions, 104 MB mempool
https://bitcoinfees.github.io/: 124 MB mempool size
http://statoshi.info/dashboard/db/transactions/: 137k unconfirmed transactions
http://munin.bitcoin-fr.io/bitcoin-fr.io/n.bitcoin-fr.io/index.html: 134k unconfirmed transactions, 116 MB mempool
https://www.blocktrail.com/BTC/: 65k unconfirmed transactions, 112 MB mempool
https://tradeblock.com/bitcoin/: 89k unconfirmed transactions, 104 MB mempool
https://bitcoinfees.github.io/: 124 MB mempool size
http://statoshi.info/dashboard/db/transactions/: 137k unconfirmed transactions
http://munin.bitcoin-fr.io/bitcoin-fr.io/n.bitcoin-fr.io/index.html: 134k unconfirmed transactions, 116 MB mempool
what fee must we use for the next month as this spam gets cleared?
There's only one way to deal with spam. Ignore it.
Perhaps you have something more interesting to do with your time.
Perhaps you have something more interesting to do with your time.
The problem is that the bitcoin network and protocol is not designed to be capable of "ignoring" spam. So you can ignore it all you want but bitcoin is being hurt by it right now.
They are making their point in support for bigger blocks.
Not really. They are creating an artificially inflated scenario, spreading FUD, and generally being assholes because no one likes XT. They're not proving anything, other than what a bunch of dicks they are.
I agree that it's a low ball move, but they do make a point that bitcoin can be attacked in this way. Instead of attacking them, devs should make the
same fix for this spam issue like Coblee did with LTC. Fast and simple solution, but no, it's much better to argue about bigger blocks and alternative clients..
imho if you can't send a dust transaction with no fee in a meaningful time, bitcoin has lost it's purpuse.
They are making their point in support for bigger blocks.
Not really. They are creating an artificially inflated scenario, spreading FUD, and generally being assholes because no one likes XT. They're not proving anything, other than what a bunch of dicks they are.
coinwallet.eu is getting an error 522.
I guess they couldn't handle their own stress test!
I guess they couldn't handle their own stress test!
As announced CoinWallet has started spamming the blockchain.
The backlog of unconfirmed transactions is know at 10 MB (ca 2 hours) and growing.
To get your transactions confirmed in a decent amount of time make sure to include an
appropriate fee.
CoinWallet disclosed target is to create a 1 month (720 hours) backlog.
https://bitcoinmagazine.com/21842/coinwallet-begins-pre-test-bitcoin-network-schedules-largest-stress-test-begin-september-10/
https://blockchain.info/unconfirmed-transactions
The backlog of unconfirmed transactions is know at 10 MB (ca 2 hours) and growing.
To get your transactions confirmed in a decent amount of time make sure to include an
appropriate fee.
CoinWallet disclosed target is to create a 1 month (720 hours) backlog.
https://bitcoinmagazine.com/21842/coinwallet-begins-pre-test-bitcoin-network-schedules-largest-stress-test-begin-september-10/
https://blockchain.info/unconfirmed-transactions
hi.. speaking of adding an amount of fees..
how will i do that? isnt it just automatic?
im sorry , i really dont know about this.
so i hope someone give me advice how to do it.
thanks.
i cant get at the free money blockchain.info is overloaded with requests on these private keys... 
Jump to: