Topic: Transaction will not leave my wallat (Read 326 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

@nc50lc
I may opt to try that, if I can summon the currage for it. I hope there are some youtubes I can waths before trying. Thanks for tip.

@HCP
I usualy start Bitcoin Core manually and let it run in the back ground
It does show connected in green "Connected (680099 blocks)"
Yes here is link : https://pastebin.com/ASFe449V


Is it possible that the problem is with the Bitcoin Core installation? My history of events:
1. I installed Bitcoin Core
2. I did alotta things to make the setup work.
3. I then then uninstalled Bitcoin Core - and reinstalled it. I deleted the roaming files manually but! for some reason the space never cleared on my harddisk?
4. I have no error messages from the Bitcoin Core

Core evicts from its mempool transactions that aren't mined within 3 days. With the recent dip in hash rate, there has been over a dozen blocks over 1h since this weekend. Probably your tx was broadcasted but never mined. I suggest you try to send those BTC again but with a manual set fee this time. Something like 150 s/B should get you through.

Do you usually run Bitcoin Core manually and then run Armory? Or do you have Armory configured to "Let Armory run bitcoind/Bitcoin Core in the background"?

When you run Armory, does it show "Connected" in green in the bottom right corner of the Armory screen?


Can you please copy/paste the contents of your "armorylog.txt" file from "Roaming\Armory" folder to pastebin and then post the pastebin URL here.

I've checked the Armorylog.txt (you can share it for others as well) and it's normal to me, but I see that you're still failing to send transactions.

If you want, you can broadcast the transaction through other means.
To get the signed raw transaction that can be pushed through other services, follow this:

• Click "Send Bitcoins", fill up the Amount and Recipient(s) and check "Create Unsigned" then Click "Continue"
• After the info/warning window, click "Copy to Clipboard", then Continue.
• Paste the copied string and click "Sign", type your password and you can now click "Copy Raw Tx (Hex)".
• Submit that to a broadcast service like https://blockstream.info/tx/push or https://live.blockcypher.com/btc/pushtx/ and the transaction should be sent to the network.

if your Armory is having trouble "seeing" transactions from your mempool, you wont see it right away until it get one confirmation.

Aside from that, I don't have any other ideas.

After 4 days of waiting I have cleared the transaction. And the balance restored.

I'm completely stuck.

Sure I can do that - but I allready did that once, and nothing happens. It does not change anything new transaction still fails. I have not changed anything between the last two transactions, so I doubt it will change anything that I try a third time.

I have no problems deleting the transaction - and the balance is restored without any problems.

But I dont know how to send you the right information for doing diagnostics on why it does not broadcast?

So it's safe to remove them from your wallet since it wasn't broadcast at all, only your wallet knows that transaction.
You can use the same option "Help->Clear all unconfirmed" and "Help->Rescan Balance", then restart Armory (and/or your PC).
Then make a new transaction.

No, only one should suffice, I'd suggest to add it to bitcoin.conf instead.

The transaction has still not entered the blockchain - I think it is safe to say it is broken

1. Yes I get the privact warning, and I get an explorer window on where to save armorylog.txt. I just save it on my desktop and scroll through it. Its very long.
2. I checked "roaming>Armory" and I can see there is a Armorylog.txt.
3. When I use the "File>Export log" the file it wants to create is titled "armorylog_20210421_0839.txt" so it is an armorylog.txt just with some more stuff. So it is not called dbLog.txt as you suggested. Maybe I just pasted the wrong section of the log to you.

None of my transactions has been broadcasted. The ID of the latest transaction is here "3ed87afc556f3b525f104b6adcc87f78f847c24e358d1c892252097ad02bafb3"

The above transaction is still open.

The previous transaction I cleared using the function in Armory Help>Clear all unconfirmed transactions - It had also not registered anywhere

Do you recommend that I use BOTH Bitcoind and the server=1 solution I have used the server=1 solution and that made all the error messages go away

I greatly appreciate your help here

That's weird, after the privacy warning, there should be a file explorer asking where you want to create the file.
Okay, it should be the same as "armorylog.txt" from the data directory: C:\Users\jlj\AppData\Roaming\Armory

There's also a chance that the first transaction prevented the second from being broadcast that's why you're seeing it as "Not in blockchain yet".
Try pasting both transactions (if not, recipient addresses) to a blockexplorer and check if those are in the network, that should minimize the guesswork.

Yes - I had ton of problems until I added server=1 in the config file. So I have done that.

Is it a special section of the export file you want then. When I create the file I dont get an option to create the file you ask for...

That's the "dbLog.txt" not "Armorylog.txt" but it looks like Armory is working fine aside from an issue with getting a transaction data from bitcoin core's mempool.

Have you followed goatpig's advice to start bitcoind with -server parameter? (post link)
Alternatively, you can add server=1 to Bitcoin Core's bitcoin.conf file in the default bitcoin data directory (location).

https://pastebin.com/0FnhTNaM

You need to paste the Armorylog to find the root of the issue, you can get it from "File->Export Log File".
And if it's too long, you can use https://pastebin.com/ and link that to your post.
(you can censor info like PC username and data directories if you prefer)

My guess is it could be a issue on your Armory database.
If that's the case, it's easy to fix but it's best to check the logs to be sure.

You can also paste the transaction ID to blockexplorers (like https://blockstream.info/) to check if the transaction already went through.
You can get the transaction ID from: Double-click the transaction, the "Transaction ID" is above the txn info.

Hi kind people
I have been extremely glad to read all your excellent posts the last few days where I have struggled to restore an old account and sell the coins. I have solved multimpel errors and problems using them. I have succeded! As a non technical dude thats a victory.

I only have one problem left. When I make a transaction it will not leave the wallet. I tried with low fee first. Then used the "help > clear all unconfirmed transactions" to start again with 300 sat/B which I understand is high, and should make a fast transaction (30 min ish).

But again it just sits there with status "Not in blockchain yet" for several hours.

I get the warning of "not able to send through P2P network - using (whatever) instead". But from posts I understand that this is not a problem. Other than that I get no errors or warnings...

Does anyone have experience with this, and can I be doing something wrong? I will be happy to wait a couple of days if you all think that is the only thing to do. But having really struggled with getting this up and running I have a nagging feeling its just not going to happen.

Any advice?