Topic: Double spend with armory (Read 928 times)

If it's unconfirmed, it's floating around in a few people's mempools, there's no such thing as "unconfirmed on the blockchain".

What happens is: first the transaction hits your mempool. Then it hits the mempool of those you're connected to. That repeats until it's in the mempool of one or more miners. Then the miner/s keeps it around in their mempool until they think it makes most sense to confirm it in their latest block. Then, and only then, does the tx hit the blockchain.

It will be removed if the second transaction is confirmed before the first one.

Ok thanks

just a last question: will the 1st transaction (txid: c4f30af21bac4398544534c39351aac2a2158e48a0690edcea818240fa44fc1)
be removed from the blockchain or will remain there, unconfirmed, forever?

If the transaction confirmed, then there's nothing to be concerned about. But you can't control what someone else thinks about the situation, you can only explain the situation (i.e. this is a deliberate double spend, but to the same Bitcoin address, which is not an attempt to steal).

With the BTC confirmed and in your counterpart's wallet, you could tell them to test this by attempting to spend the funds you sent. A clever way to do this would be to get them to include a fee that's too low, that way they can test that the coins are spendable without having to actually pay pointless transaction fees (as the transaction most likely won't get relayed to or confirmed in a block by any miners)

Hello guys,

yesterday i sent 3 BTC but after 3 hours of 0 confirmation i used the option "clear all unconfirmed", i restarted armory and found the update balance with the 3BTC back.

So I've resend the transaction and after a while it finally got confirmed but it says "double spend" (Warning! this transaction is a double spend. You should be extremely careful when trusting any transactions to/from this sender.) so the guy thinks im scamming him!

1st send txid: 8c4f30af21bac4398544534c39351aac2a2158e48a0690edcea818240fa44fc1
2nd send txid: b44ef709daa9a01b0b2c4eb4b8e5c9e091e9d837bba5bc3bc0cc7532d411747e

I've rebuilt and rescan the database: I have armory 0.95.1 and bitcoin-qt 0.13.1


What can I do?? please help

I was successfully able to double spend after so much tinkering and waiting. Now I need to fix armory because its stuck on scanning transaction history

It is, but I'm not sure it makes sense that doing that would help. The best option, sadly, is probably to send a watching-only copy of the wallet to goatpig. If you've encountered a bug that's so far never manifested for others, then it's important to diagnose and fix that. Otherwise, how can you (or others) have any assurance that it could not happen again?

Yes, I am using Armory 0.95.1. I been trying to sweep the privkeys into bitcoin core recently too. I've gotten it into bitcoin core but even while the coins are available, it doesnt look like they are spendable (if I attempt, it will give me an invalid tx id that dont exist on blockchain.info). I've tried electrum but it gives an conflict error. I honestly do need the coins soon and hoping that by the end of today it will be truly available, but from what it looks like, there isnt much that can be done unless the the transactions are all confirmed. Is it possible to manually confirm a transaction using a miner?

Using 0.95.x? I believe a bug has crept in to the Clear Unconfirmed feature, I couldn't get it to work recently. Deleting manually the files ./armory/databases/zero-conf* did the trick for me (i.e. both of the 2 files beginning zero-conf)



Bear in mind that the last time you might have rescanned the blockchain with bitcoind, there were fewer blocks AND those blocks had fewer transactions to check.



It doesn't remove it from the network, only from the Armory unconfirmed cache. In practice, that will do alot to remove the transaction from the network (given a little time), as all other Bitcoin nodes will evict the low-fee transaction from their mempools once it's remained unconfirmed for >72 hours. It possibly didn't propagate very widely anyway, but there is an off-chance that some node with a very permissive mempool size (and/or a tweaked rejection timeframe) might retain the low-fee transaction long enough that it confirms (it's a lottery, but a small percentage of low fee transactions are still getting processed, they're just much less frequent)

Im not the person who would sign stuff without reviewing it. Thats like signing a contract without reading the fine prints however I am waiting for the bitcoind to finish the rescan (again) before I attempt anything else to see if it will clear its mempool as I may just keep the coins in the wallet itself. However thanks for the info of doing it from bitcoin-cli.

since you're using bitcoind, something like this should work in your case:
bitcoin-cli createrawtransaction "[{\"txid\":\"91c9c046afda04186be488f784e7e0619b5f9eae3974a9951411b78af421f9dd\",\"vout\":1}, {\"txid\":\"72816bed825f0f488003949901fa7275887991abe8e7983a1117cd1e62114ec1\",\"vout\":2},{\"txid\":\"b0a61e7842b556ced310357aabb7df7ed88097e09d6fd6b25efccb413e189bf4\",\"vout\":0}]" "{\"188DN1tYGQsUbGgXuKmhuo8ATd5T4npsvs\":0.11679356}"

This should create a raw, unsigned transaction using the listed inputs (the 3 tx-ids, and which output of the txid has to be used as an input) to create an output of 0.11679356 to 188DN1tYGQsUbGgXuKmhuo8ATd5T4npsvs.
The sum of inputs - the sum of the outputs = the fee... Do your calculations to select an appropriate fee this time!

(in*180 + out*34 + 10 plus or minus 'in') * recommanded fee
(3 * 180 + 1* 34 + 10) * 100 = 58400 satoshi's = 0.000584 BTC

inputs => 0.11437916 + 0.0025 + 0.0003144  = 0.11719356
inputs - fee = 0.11719356 - 0.000584 = 0.11661356
so if you'd create an output of 0.1166 just to be sure, you should be ok


results in

Afterwards, you can use bitcoin-cli to sign the raw transaction.
(bitcoin-cli signrawtransaction HEX)

Do your homework and doublecheck my inputs/output, decode the hex and make sure you agree with the unsigned hex before even attempting to sign it!!!!!!!!!!!!

Is it common for this to happen? Armory usually does tell me about having a higher transaction fee but recently it havent, but would would the recommended fee should be set too so i could possibly set it by default.

Also I selected to clear the unconfirmed transaction and restarted armory but it is still there. How long does it usually take?

Apparently the queue of unconfirmed transactions is building up quickly so a higher fee is required.
https://bitcointalk.org/index.php?topic=1690349.120
https://blockchain.info/charts/mempool-size

The transaction is https://blockchain.info/tx/c1156446f2cebfc2befdca708d05e6dfa6730cc026de428b2c0662bb3c82ea0a/0 though I may create the transaction myself. I have attempted to import the private keys to bitcoind itself but it takes so long to rescan (which is odd since it never took this long).


I may try that. I thought that only just remove them from the transaction list, didnt know it removes it from the network.

Has the transaction been accepted by the network? You can try doing a clear all unconfirmed and rescan.

I don't have a lot of experience with armory, but i think you could easily export the private key of the address whose inputs you want to double spend...
Using this private key, you could use bitcoin core or the sourcecode of coinb.in to create a transaction using the same inputs as the stuck transaction, then sign this raw transaction using the private key and broadcast the new transaction.

If you could show us the tx id of the stuck transaction, i could make a raw, unsigned transaction doublespending the inputs of the stuck, unconfirmed, transaction, so you only have to sign and broadcast it.

How would I go about double spending with armory? I have send some coins to another wallet over 48 hours ago and it is still unconfirmed. I tried rebroadcasting the transaction but no luck and do not know why this happened when the transaction fee was at 0.0001 btc.