Author

Topic: Problem with invalid transactions (Read 1563 times)

legendary
Activity: 1428
Merit: 1093
Core Armory Developer
May 04, 2012, 07:44:24 PM
#5
if someone could point me in the right direction to remove them from my client, I haven't tried a rescan because I don't think it would remove them.

Hacking manually in the wallet.dat is totally acceptable. (I assume I'd need some sort of BDB CLI client)

I found it nearly impossible to get some invalid transactions out of my wallet.  Though, I didn't try pywallet...

If the wallet was created with a version of the client before 0.6.0, you can import the entire Satoshi wallet into Armory (Wallets->Migrate Bitcoin Wallet).  From there, you can sweep the relevant addresses or move the coins out from under those invalid Tx.  Once the tx hits the blockchain, go back to the original client which will see those tx as actually invalid and will complaining (well, it should)
member
Activity: 61
Merit: 10
legendary
Activity: 1372
Merit: 1007
1davout
May 03, 2012, 03:46:25 PM
#3
Bumpity bump.

If someone had a pointer for this, would help me Smiley

if someone could point me in the right direction to remove them from my client, I haven't tried a rescan because I don't think it would remove them.

Hacking manually in the wallet.dat is totally acceptable. (I assume I'd need some sort of BDB CLI client)
full member
Activity: 144
Merit: 100
April 27, 2012, 06:52:54 PM
#2
7dae7272a356d1340d02a81690951e7323823b9f534da1c8b120acb08b106f4c is in block 177208.

I don't see the other one in my debug.log.
legendary
Activity: 1372
Merit: 1007
1davout
April 27, 2012, 01:53:09 PM
#1
I'm currently encountering a weird issue with Instawallet's bitcoind.
It is a stock client with a TX/block monitoring patch, but without Jan's previous patches (green-address, zero fee).

I have two invalid transactions in it : for some reason, two users trying to send funds generated what was seen by the network as an invalid transaction.

They appear when doing a gettransaction against instawallets client, but they are nowhere else to be found (blockexplorer.com and blockchain.info)

So it'd be really nice if someone could grep them out their debug.log to see what was wrong with them.

And it'd be even nicer if someone could point me in the right direction to remove them from my client, I haven't tried a rescan because I don't think it would remove them.

TX IDs are :
 - 7dae7272a356d1340d02a81690951e7323823b9f534da1c8b120acb08b106f4c
 - f0dd9c4847eb6dc0f7ddb021ab8a315fb2653b8d04ff2f39f3e62bce59951177
Jump to: