arnuschky



Offline



Activity: 517

Merit: 500







Hero MemberActivity: 517Merit: 500 New transaction malleability attack wave? Another stresstest? October 01, 2015, 07:58:10 PM #1



we're seeing a lot of malleated transactions on our nodes. Anyone else?



Tx listed on



What's the point? Another stresstest?



* or close enough Hey all,we're seeing a lot of malleated transactions on our nodes. Anyone else?Tx listed on https://blockchain.info/double-spends are also all malleated (click on links, if marked as "conflicted" blockchain.info has seem two versions of the same* tx).What's the point? Another stresstest?* or close enough

AWARD-WINNING

CASINO CRYPTO EXCLUSIVE

CLUBHOUSE 1500+

GAMES 2 MIN

CASH-OUTS 24/7

SUPPORT 100s OF

FREE SPINS PLAY NOW ertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertised sites are not endorsed by the Bitcoin Forum.They maye unsafe, untrustworthy, or illegal in yourjurisdiction. Advertise here.

RussianRaibow



Offline



Activity: 630

Merit: 500



I AM A SCAMMER







Hero MemberActivity: 630Merit: 500I AM A SCAMMER Re: New transaction malleability attack wave? Another stresstest? October 01, 2015, 11:28:26 PM #3 Quote from: arnuschky on October 01, 2015, 07:58:10 PM



we're seeing a lot of malleated transactions on our nodes. Anyone else?



Tx listed on



What's the point? Another stresstest?



* or close enough

Hey all,we're seeing a lot of malleated transactions on our nodes. Anyone else?Tx listed on https://blockchain.info/double-spends are also all malleated (click on links, if marked as "conflicted" blockchain.info has seem two versions of the same* tx).What's the point? Another stresstest?* or close enough

Here is a case of such double-spending -



Even after 29 days of broadcast, while one Tx has already got confirmed, another is still hanging in some node's mempool...



https://live.blockcypher.com/btc/tx/07dd024065a6ef12652670618e510503e1af4e0f4d75ddc6f4d2a55f002c9bc0/ Here is a case of such double-spending - https://bitcointalk.org/index.php?topic=1197096.0 Even after 29 days of broadcast, while one Tx has already got confirmed, another is still hanging in some node's mempool... I AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMERI AM A SCAMMER

chronicsky



Offline



Activity: 2226

Merit: 1160



Just looking for peace







LegendaryActivity: 2226Merit: 1160Just looking for peace Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 04:13:25 AM #4 It's strange , i have something very similar....

I do not own a miner or anything but just now i sent some payments though it doesn't show up in my blockchain wallet unless i login. I see two txs to same address of same amount , one confirmed and one not. and there is a incoming tx which is not confirmed and probably double -spent but which is not possible , it was sent using CoinBase...

Anyone knows, what's going on ?

arnuschky



Offline



Activity: 517

Merit: 500







Hero MemberActivity: 517Merit: 500 Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 06:56:07 AM #6

Interestingly, it seems that the later transactions (ie, the malleated one, not the original one) that are confirming.

At least in our case.



Can someone confirm this? More importantly, if your transactions are being malleated, which one is confirming?

Yours or the other one?



Some explanation: Malleated transactions face the same difficulty as doublespends: they need to be accepted

by a miner before the original tx (or the miner needs to replace the original tx). The first case isn't very likely,

the second requires the miner to run some non-standard software (Peter Todd's RBF-FSS).



If it's mostly malleated transactions that are confirming, we're facing something new. Either someone is

colluding with miners, or many miners are running RBF-FSS, or there's a bug.

chronicsky



Offline



Activity: 2226

Merit: 1160



Just looking for peace







LegendaryActivity: 2226Merit: 1160Just looking for peace Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 07:39:00 AM #7

one incoming tx is pending , which will sooner or later be ok i suppose....

BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....

How does it affect me ??











The bitcoins has been deducted twice and am not getting it back i suppose...





any ideas? The real problem am facing here because of this is not 0 confirmation but something else...one incoming tx is pending , which will sooner or later be ok i suppose....BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....How does it affect me ??The bitcoins has been deducted twice and am not getting it back i suppose...any ideas?

arnuschky



Offline



Activity: 517

Merit: 500







Hero MemberActivity: 517Merit: 500 Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 07:49:04 AM #8 Quote from: chronicsky on October 02, 2015, 07:39:00 AM

one incoming tx is pending , which will sooner or later be ok i suppose....

BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....

How does it affect me ??







The bitcoins has been deducted twice and am not getting it back i suppose...



any ideas?

The real problem am facing here because of this is not 0 confirmation but something else...one incoming tx is pending , which will sooner or later be ok i suppose....BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....How does it affect me ??The bitcoins has been deducted twice and am not getting it back i suppose...any ideas?

This is the malleability problem: someone is creating copies of transactions that result in the same result but look different to the network (different transaction id).

In your screenshot, you see that both transactions are "doing" the same thing. They are basically the same tx under a different name.

As long as one of the two confirms, you're good. You can ignore the one that does not confirm.



And no, bitcoins aren't deducted twice, don't worry. Only confirmed ones count towards your balance.

Note that your wallet software might be confused and thus show an incorrect balance until the unconfirmed tx is discarded. This is the malleability problem: someone is creating copies of transactions that result in the same result but look different to the network (different transaction id).In your screenshot, you see that both transactions are "doing" the same thing. They are basically the same tx under a different name.As long as one of the two confirms, you're good. You can ignore the one that does not confirm.And no, bitcoins aren't deducted twice, don't worry. Only confirmed ones count towards your balance.Note that your wallet software might be confused and thus show an incorrect balance until the unconfirmed tx is discarded.

chronicsky



Offline



Activity: 2226

Merit: 1160



Just looking for peace







LegendaryActivity: 2226Merit: 1160Just looking for peace Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 07:55:39 AM #9 Quote from: arnuschky on October 02, 2015, 07:49:04 AM Quote from: chronicsky on October 02, 2015, 07:39:00 AM

one incoming tx is pending , which will sooner or later be ok i suppose....

BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....

How does it affect me ??







The bitcoins has been deducted twice and am not getting it back i suppose...



any ideas?

The real problem am facing here because of this is not 0 confirmation but something else...one incoming tx is pending , which will sooner or later be ok i suppose....BUT, i sent some coins and now when i open my wallet and check - it shows me two similar tx to same address - one confirmed and one not....How does it affect me ??The bitcoins has been deducted twice and am not getting it back i suppose...any ideas?

This is the malleability problem: someone is creating copies of transactions that result in the same result but look different to the network (different transaction id).

In your screenshot, you see that both transactions are "doing" the same thing. They are basically the same tx under a different name.

As long as one of the two confirms, you're good. You can ignore the one that does not confirm.



And no, bitcoins aren't deducted twice, don't worry. Only confirmed ones count towards your balance.

Note that your wallet software might be confused and thus show an incorrect balance until the unconfirmed tx is discarded.

This is the malleability problem: someone is creating copies of transactions that result in the same result but look different to the network (different transaction id).In your screenshot, you see that both transactions are "doing" the same thing. They are basically the same tx under a different name.As long as one of the two confirms, you're good. You can ignore the one that does not confirm.And no, bitcoins aren't deducted twice, don't worry. Only confirmed ones count towards your balance.Note that your wallet software might be confused and thus show an incorrect balance until the unconfirmed tx is discarded.

Actually i checked and the balance has been deducted twice , means i will get this btc back once the unconfirmed tx clears? but we can't say it will even clear right



Actually i checked and the balance has been deducted twice , means i will get this btc back once the unconfirmed tx clears? but we can't say it will even clear right

shorena

Legendary



Offline



Activity: 1498

Merit: 1346





No I dont escrow anymore.







Copper MemberLegendaryActivity: 1498Merit: 1346No I dont escrow anymore. Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 07:56:35 AM #10 Quote from: chronicsky on October 02, 2015, 07:55:39 AM

Actually i checked and the balance has been deducted twice , means i will get this btc back once the unconfirmed tx clears? but we can't say it will even clear right

-snip-Actually i checked and the balance has been deducted twice , means i will get this btc back once the unconfirmed tx clears? but we can't say it will even clear right

Well for bitcoin core you could just rescan the wallet, Im not sure how you would do that with... what looks like blockchain.info. Well for bitcoin core you could just rescan the wallet, Im not sure how you would do that with... what looks like blockchain.info. Im not really here, its just your imagination.

amaclin



Offline



Activity: 1260

Merit: 1008







LegendaryActivity: 1260Merit: 1008 Re: New transaction malleability attack wave? Another stresstest? October 02, 2015, 11:14:19 AM #19 Quote from: basil00 on October 02, 2015, 11:00:19 AM This "attack" probably stops spam scripts that generate long chains of unconfirmed txs. The main word is "probably".

Spam engine should not broadcast predefined set of transactions, but should monitor all transactions on the network from different nodes and build on-the-fly next transaction on top of previous one received from the peer. Splitting the "chain" to a "binary tree" just adds more fun



Better way to stop spam is to malle spammer chain txs on mining pool.



Quote It might actually be a good thing to leave this running. I do not think so. I do not see any benefits for me running it. Today. The main word is "probably".Spam engine should not broadcast predefined set of transactions, but should monitor all transactions on the network from different nodes and build on-the-fly next transaction on top of previous one received from the peer. Splitting the "chain" to a "binary tree" just adds more funBetter way to stop spam is to malle spammer chain txs on mining pool.I do not think so. I do not see any benefits for me running it. Today.