It all depends on how many inputs you have. Armory gives you your nodes fee estimate if you turn the RPC on

Turn on your node RPC.

How did you grab the receive address from Armory? What version are you using?

You would see the transaction regardless of the coins' destination since you are spending something at the very least. Did you do anything out of the ordinary after creating the transaction? Also post armorylog.txt. Use pastebin.

post logs

post armorylog.txt

No, use the testing build for 0.96.1

If there's change, you should CPFP. Otherwise clear unconfirmed and push again.

Chances are you didn't push a proper fee.

Your transaction doesn't seem to have hit the network at all. If it's being displayed in Armory's ledger, pick Help ->  Clear Unconfirmed Transactions, then restart Armory and try to resend.

Ah I see. That can only happen in offline mode. Will push the fix in a few.

You don't need to build for that really. The issue was on the Python side, you'd have to pull form the testing branch and repackage with py2exe (assuming you want to create a .exe)

Fixed the backup center issues yesterday, you'll have to build yourself or wait for another build.

Double click works for me. Can you try to narrow it down? Which area of the line are you clicking? As for right click menu, there isn't one for this dialog.

You should always update when possible. Use the testing build for 0.96.1:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.2-testing


The relevant factors are, in the following order:

- storage speed
- core count
- ram

Since your graphics card is low end (x400 for nvidia is as bad as it gets), I'm guessing your computer is short on RAM and uses a HDD.


It won't be able to run on the SegWit chain when that comes around. It also has some security concerns seeing it still uses the phone home code.


More like

It could. It's just cheaper to rebuild Armory's DB from scratch to confirm than to nuke Core's DB, thus why I told you to rebuild.

It will never mine, CPFP it.

Use 0.96 and CPFP the change.

This is indicative of a bad block of disk or a corrupt ArmoryDB. If a full rebuild of the DB yields the same issue (at the same spot), then your on disk data is corrupt.


That's usually what happens after the running into a bad block during DB build.