Stuck transactions - possibly new attack? - page 2.

DannyHamilton

legendary

Activity: 3514

Merit: 4895

Quote from: djeZo on February 13, 2014, 12:37:08 PM

I can give you TXIDs, but you won't be able to find them... so whats the point of it?

I am using bitcoin-qt, RPC API for everything related to BTC handling, and of course, integrated accounts in bitcoin client.

Issue a "getrawtransaction" with the transactionID that you are having a problem with.

Post the results of the getrawtransaction here.

We can then use "decoderawtransaction" with our own bitcoin wallets to see what the inputs and outputs are. Analyzing this will likely indicate why your wallet is unable to broadcast the transaction.

thenoblebot

sr. member

Activity: 364

Merit: 252

I think the transactions are being mutated intentionally (although it does happen once in a while in normal course). I have made a (tentative) proposal here (https://bitcointalksearch.org/topic/working-around-malleability-catching-the-culprit-if-there-is-one-463350)of how to go about identifying the pool responsible for it, IF it is being done by a pool at all. Once we can identify it then that should solve the majority of such problems.

klondike_bar

legendary

Activity: 2128

Merit: 1005

ASIC Wannabe

Quote from: djeZo on February 13, 2014, 12:37:08 PM

I can give you TXIDs, but you won't be able to find them... so whats the point of it?

I am using bitcoin-qt, RPC API for everything related to BTC handling, and of course, integrated accounts in bitcoin client.

I checked bunch of transactions that were made by same customer (person X) going to same rig provider (person Y), and were only few or even less minutes appart. There was total of 8 transactions, 6 were at the end confirmed, 2 are still not and pending (since 12.2.2014 20:45 CET time). After these transactions, same customer hired other rigs some hours later and these transactions were then confirmed. Does that mean that it is safe to assume these 2 non-confirmed transactions will never be confirmed and should be deleted and resent?

I am having a similar issue where a txid cannot be found on blockchain even after almost 10 minutes. I had a malled transaction before, so perhaps my address balances are all out of sync.

what can/should I do?

djeZo

hero member

Activity: 588

Merit: 520

I can give you TXIDs, but you won't be able to find them... so whats the point of it?

I am using bitcoin-qt, RPC API for everything related to BTC handling, and of course, integrated accounts in bitcoin client.

I checked bunch of transactions that were made by same customer (person X) going to same rig provider (person Y), and were only few or even less minutes appart. There was total of 8 transactions, 6 were at the end confirmed, 2 are still not and pending (since 12.2.2014 20:45 CET time). After these transactions, same customer hired other rigs some hours later and these transactions were then confirmed. Does that mean that it is safe to assume these 2 non-confirmed transactions will never be confirmed and should be deleted and resent?

coastermonger

sr. member

Activity: 367

Merit: 250

Find me at Bitrated

care to post any more info on these?

djeZo

hero member

Activity: 588

Merit: 520

Is there another form of attack going on bitcoin network right now?

I have several outgoing transactions (not malled ones - legit, created by my bitcoin-qt client) that are never confirming. Fee was paid for them, TXID cannot be found on blockchain. I have never seen this before. But now they are poping up after incident with malled transactions. Worth mentioning is that some of these are being sent to same address and having same amount - maybe there are some nodes in bitcoin network that are filtering malled transactions the wrong way and filtering out my legit transactions now?

How should I proceed in solving this? I still have bunch of malled transactions (but these are dating few days back). The accounts/addresses of these new "stucks" are not related to past malled ones.

Would be the proper way to clean up stuck transactions and perform resends?

Topic: Stuck transactions - possibly new attack? - page 2. (Read 2944 times)