I have some small transaction recently with the fees recommend by latest Core 0.11.1, the first confirmation came in after 3 hours.
The problem with the network just now was the super slow generation of blocks, taking around 30-40minutes per block. This can be due to bad luck. My transaction was stuck for roughly one hour with a good amount of fee. What's your transaction ID? 
Topic: Are we stress testing again? - page 4. (Read 33190 times)
I have some small transaction recently with the fees recommend by latest Core 0.11.1, the first confirmation came in after 3 hours.
Hopefully not too many noobs with them that could get the impression bitcoin is lame and slow.
Edit: I have a poloniex withdraw with enough fee that hangs since hours. And if really no spam is going on then i really would wish that some people wake up and realize that this IS a real problem.
Edit: I have a poloniex withdraw with enough fee that hangs since hours. And if really no spam is going on then i really would wish that some people wake up and realize that this IS a real problem.
Ah crap ... again ?
Nah, just the usual additional traffic that comes with price swings.
Ah crap ... again ?
I'm pretty sure that this stress test is mostly legitimate bitcoin-fever. https://bitcoinfees.github.io/
yep : 184 000 ... 
These may be legit. Lots of volume the past couple of days.
Ah crap ... again ?
Yesterday i sent some transactions to poloniex and 2 of the three transactions had been malleated. So copies were created and showed up. They didn't confirm of course.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
Did both transactions confirm eventually? How long did it take to confirm. Hope the delay did not affect your trading.
and
Yesterday i sent some transactions to poloniex and 2 of the three transactions had been malleated. So copies were created and showed up. They didn't confirm of course.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
My bot is paused for a long time.
Are you sure that your original txs have low-S signatures?
Because some users malleate "non-standard" transactions to "standard" form.
https://bitcointalksearch.org/topic/malleability-counter-attack-malleate-to-lows-instead-of-dropping-highs-1204959
See, i sent 3 bitcoin transactions. I logged in now and the deposit list looks like this:
2015-10-22 18:51:39 COMPLETE
2015-10-22 18:48:21 PENDING (0 of 1 confirmations)
2015-10-22 18:48:21 COMPLETE
2015-10-22 18:47:42 COMPLETE
2015-10-22 18:47:42 PENDING (0 of 1 confirmations)
You see two transactions didn't confirm, three did. Though the two nonconfirming seems to be malleated versions of 2 of the other transactions. Same time, value and target. So that was part of the malleability attack it seems.
Sent from electrum 2.3.2.
Yesterday i sent some transactions to poloniex and 2 of the three transactions had been malleated. So copies were created and showed up. They didn't confirm of course.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
My bot is paused for a long time.
Are you sure that your original txs have low-S signatures?
Because some users malleate "non-standard" transactions to "standard" form.
https://bitcointalksearch.org/topic/malleability-counter-attack-malleate-to-lows-instead-of-dropping-highs-1204959
Yesterday i sent some transactions to poloniex and 2 of the three transactions had been malleated. So copies were created and showed up. They didn't confirm of course.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
Did both transactions confirm eventually? How long did it take to confirm. Hope the delay did not affect your trading.
Yesterday i sent some transactions to poloniex and 2 of the three transactions had been malleated. So copies were created and showed up. They didn't confirm of course.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
So it's really so that 2 attacks run now. Might be from the same person trying as much harm as possible.
https://blockchain.info/tx/3384d689ecc481f0815b2d94b119c15a8e86f56789d0dfe0c76b7a56f170ecdc
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
No. Because several inputs were unconfirmed when tx arrived to bc.iLook at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
Yea , i thinks that too because i've played some earlier bets which was un-confirmed and i immediately played all with all the amount in my addy.
https://blockchain.info/tx/3384d689ecc481f0815b2d94b119c15a8e86f56789d0dfe0c76b7a56f170ecdc
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
No. Because several inputs were unconfirmed when tx arrived to bc.i Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
https://blockchain.info/tx/3384d689ecc481f0815b2d94b119c15a8e86f56789d0dfe0c76b7a56f170ecdc
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
Your fee was 20 times higher than the minimum fee. The confirmation time matches the calculated confirmation-times shown on cointape.com. Check the website out. It's pretty usefull.
https://blockchain.info/tx/3384d689ecc481f0815b2d94b119c15a8e86f56789d0dfe0c76b7a56f170ecdc
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
I guess so? Weird, I've been watching tx getting confirmed in less than hour with lower fees than you included in yours.
https://blockchain.info/tx/3384d689ecc481f0815b2d94b119c15a8e86f56789d0dfe0c76b7a56f170ecdc
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
Look at my trx. it get confirmed after 110+ mins .. wow . maybe it was because of lower fees ?
that we don't have it now because those, who should implement it, have a financial interest that bitcoin is not working fully fine.
Yes, right.But not only this.
It can not possible in our Universe to create something "which is good [for everyone]"
Well, I guess we all give up now.
I have the feeling many gave up, yes. But i think we only need to wait a while until everyone sees how stupid a "fee market" would be. We have to pay 30 times the minimum fee for standard transactions now. And this is only a problem because of spam transaction.
If you imagine having more than enough legit transactions that would fill, let's say 2MB blocks constantly then it really will get nuts. Because it is impossible that all legit transactions can confirm. The fee market will rise exponential and still alot of people would pay not enough.
Such a bitcoin would die pretty fast. It would be useless because unreliable. And the lightning network will die on the same day.
I really did not think bitcoin will stay in such a politics zone.
the thrid way is a block espiration delay already coded, i remember ... like after 1003 blocks, the transaction is purged.
i have read this in a thread or the wiki, but i can't remember how to do the search to find this.
i have read this in a thread or the wiki, but i can't remember how to do the search to find this.
There are two ways for a transaction to be rejected.
The first is "effective" rejection as opposed to "official" rejection, and that's what happens when a conflicting transaction gets into the block chain. Basically, if one of the inputs of your transaction gets spent by a different transaction, and that different transaction is more than one or two blocks deep in the block chain? Forget it. Your transaction, although some places may keep it in the mempool indefinitely, is never going to happen. (well, unless a chain reorganization reaches all the way back to the block with the conflicting transaction and kicks it out. But what are the odds of that?)
The second way for a transaction to be rejected is relatively new; with the most recent build, transactions marked as being more than 72 hours old get kicked out of the mempool if they haven't confirmed.
But there's a point about this 72-hour rule; no miner is under any obligation to follow it. It becomes non-standard and won't be relayed by default after that point, but If the miner hasn't kicked it out of their mempool, and no conflicting transaction has gone through, and the miner gets around to including it in a block a week later, it will go through.
The first is "effective" rejection as opposed to "official" rejection, and that's what happens when a conflicting transaction gets into the block chain. Basically, if one of the inputs of your transaction gets spent by a different transaction, and that different transaction is more than one or two blocks deep in the block chain? Forget it. Your transaction, although some places may keep it in the mempool indefinitely, is never going to happen. (well, unless a chain reorganization reaches all the way back to the block with the conflicting transaction and kicks it out. But what are the odds of that?)
The second way for a transaction to be rejected is relatively new; with the most recent build, transactions marked as being more than 72 hours old get kicked out of the mempool if they haven't confirmed.
But there's a point about this 72-hour rule; no miner is under any obligation to follow it. It becomes non-standard and won't be relayed by default after that point, but If the miner hasn't kicked it out of their mempool, and no conflicting transaction has gone through, and the miner gets around to including it in a block a week later, it will go through.
Jump to: