Topic: Transaction will not leave my wallat (Read 282 times)

A last update.

Following the cleared transaction Armory went "offline" for no apparent reason. I reinstalled the Bitcoin Core, but it did not help. I then deleted the Armory installation and reinstalled the Armory. That got it online and I was able to sell the remaining BTC.

Again - many thanks for your help.

Over and out.

As it turns out the transaction eventually cleared, so I have now successfully completed a partial from my Armory wallet. I asume I will be able to sell the rest too.

You have all been extremely helpfull and patient - I deeply gratefull to you all. Thank you!

The idea would be to CPFP the tx if it has change.


If you nuked your own Core mempool in the process, it wouldn't be aware of the spentness and fail to help you with this broadcast error. The original issue of low fees on the first tx remains.

A follow up question.

The transaction that is currently blocking by being unconfirmed is from the April 19th

When using Armory, I have received no errorm essages at all, when making new transactions after april 19. They just lie there doing nothing. I only got the error message, men posting the transaction in a webpage. Does that not indicate that something is still not ok?

Maybe it would be best to only try using a web-broadcast next time and not use my own BTC core installation...

The transaction has 0 confirmations. I think it is from before I got the setup to work properly - before I got the "server=1" into botcoin core or something.

It does not say anything about BRF anywhere - I also checked the logfile and I cant find anything - so likely it was disabled.

I believe my only real option is to wait for the blockchain to clean up the transaction - and then try again :-)

Yes, quite likely everything was working OK... but there was just a timeout between Bitcoin Core and Armory so you got the weird error about the transaction not being able to be sent OK.

Then, after you cleared everything... and tried to send again... you get the "mempool conflict" error, as the coins have already been "used" in the currently unconfirmed transaction.

I would say that your current options are:

1. Just wait... your transaction will either confirm, or after 14 days is likely to be dumped by the majority of nodes and you should be able to create a new transaction (with an appropriate fee! ) and send that out without issue

or

2. Attempt to accelerate the transaction using the free ViaBTC accelerator (assuming your transaction fee rate was >= 10 sats/byte). It's hard to get one the 100 hourly slots tho... you have to send within the first second of a new hour (ie. when the clock turns XX:00!) or you'll get "submissions beyond limit" which means the 100 slots have been filled.

or

3. Check if the transaction on the block explorer is marked as RBF... blockchair.com and mempool.space show pretty clearly whether the transaction is RBF or not... if it is RBF, you can attempt to broadcast a replacement transaction that bumps up the fee... however, given the error that you are getting, it seems like it might not be RBF enabled

Ok blockexplorer was realy helpfull!!

By pasting in my Sender ID I was able to find all transactions. Both my original buy, and an unconformed transaction from this week.

It is red - and stated unconfirmed.

I can also find the transaction in my armorylog.txt

Conclusion: BTC core and Armory must be working just fine?

And you say that I must wait 14 days before the blockchain clears all unconfirmed transactions?

@nc50lc

No I have not shared my paper backup sheet with anyone. I dont think anything un-lawfull is the problem. I'm the problem.
I think I disabled RBF, but I realy cant remember.
I dont have any transactions in my Armory - I used the function "clear all unconfirmed transactions". Before clearing I checked the transaction ID on web-bage to be sure it was not registered.
My balance is restored - no problem there

"Lastly you should share armorylog.txt" - this confuses me - I thought I already did that. The text I shared came from that file. The entire file is too big for me to share using Pastebin. But if you want the entire file I can maybe make several pastebin files...


I wil try and use blockexplorer an dsee what I can find - thanks for tip...

@HCP
OK, so worst case, I wait 14 days and try again. I can live with that.
 

This error means that the input(s) that you're trying to spend are already spent by another transaction that's not marked as replaceable.
My best bet is it was your second transaction or first transaction if those aren't marked as RBF,
but Armory has "enable RBF" ticked by default (CMIIW) have you disabled RBF when creating those transactions?
If you did, then that must be the case.

If it's either of the two, and with RBF, the new transaction should replace the earlier transaction or you will get this error if it failed:And you got a different error msg which doesn't sound good if those have RBF flag (you haven't shared your wallet backup or private keys to random PMs, have you?).

You can check the address where you want to send or your own wallet's addresses using a blockexplorer, check for a transaction that looks familiar.
Lastly, you should share the armorylog.txt contents so goatpig and others can see it.

If it shows up on block explorers, then it will be in the mempool of other nodes... so no, you won't be able to delete it. At best, if it was RBF enabled, you could try and "replace" it by using RBF.

If it is only in the mempool of your local node, then shutting down Armory and your instance of Bitcoin Core, then deleting the mempool.dat file from the Bitcoin Core data directory and then restarting Bitcoin Core and restarting Armory should wipe the mempool of your local node, effectively removing that transaction.

I'd say the chances are fairly good that if your local node accepted it, it would also have been broadcast to the wider network and is likely in other mempools... so, RBF might be your only option.

Either that... or waiting the 14 days that default nodes wait until they purge unconfirmed transactions.

@HCP is it something that can be fixed? can I delete this from the memepool if I find it, or how does that work?

it will give up some of your privacy and link some addresses (and possibly some BTC value) to your Bitcointalk account (and any linked accounts)... but no one will be able to edit the transaction, steal coins or access your private keys.

It seems like one of the transactions that you sent previously did indeed make it onto the network (or at least as far as the mempool of your Bitcoin Core node) and this is why you are getting the "mempool conflict" error.

You could also try searching on a block explorer for the addresses you are sending from/to and see what unconfirmed transactions currently exist for those addresses to try and identify the previous transaction causing the conflict

I'm realy not an expert here - is it safe to post the transaction like that?

This means the transaction you are trying to create is in conflict with another transaction already in the mempool. You need to look into which outputs you are trying to spend, because there is a transaction right now in the network that isn't mined but spends from your outputs. Most likely a former attempt to spend, with a low fee. We can do something about that but first you need to identify the transaction.

Perhaps if you were to post the actual RAW transaction here in this thread?  There are other websites that you can [Guide] Broadcast Your RAW Transaction (Push TX) BTC & Alts coins

In the dialog box type getrawtransaction then paste it here using the code tag.

that would be 96.5 ... not 62.5

I see it is licensed to goatpig... (bows in awe)

How do I delete the unpublished transaction?

When I go to ">offline transaction" I get er version warning: Since Armory version 0.92 the formats for off line has changes to accomodate multisugnature... To copntinue you need to update to version 0.92 or later.

I'm using Version 0.62.5-beta-8730390989 so that is a later version than 0.92...

When I click that away I only have an option to sign transactions. I dont know where to find the Cold signed transaction to delete it?

I have done what NC50cl suggested

When I paste the Raw Tx (Hex) into https://blockstream.info/tx/push I get the below error?

sendrawtransaction RPC error: {"code":-26,"message":"txn-mempool-conflict"}

What does that mean?

Then do what nc50lc suggested:

@goatpig

I manually set it to 300 in my failed transaction! double what you suggest it should have cleared within an hour at that fee