Quote from: RustyRussell on November 28, 2017, 03:10:35 AM

Woot! Thanks, removing them, and with C++ signer, it worked.

I'm going to assume the situation has not change with the Python signer, right? Definitely something weird with the wallet state.

Quote

Still have those 4 confirmed txs which Armory thinks aren't confirmed (and offers to bump fee). I'll append tomorrow this one gets similarly stuck.

There are 3 possible states:

1) The ZC DB is corrupt and still shows the tx as unconfirmed, while they also appear as confirmed in the ledger. In this case, you can clear unconfirmed tx from the Help menu and restart Armory.

2) The ZC never actually mined. In this case, they may or may not be in the in a miner's mempool. You can just RBF these. You'll probably have to build the current state of testing as it has the RBF fixes in there. If you want signed builds, you'll have to wait till I'm done with this accursed BTG signer.

3) Your DB is stuck and can't see new blocks, therefor will never see these tx mined. You can check for this state by comparing Armory's top block (bottom right corner) to your network's top block. In this case, I'd need to see dbLog.txt before I can give you recommendations on how to proceed.