Topic: Armory 0.96.4 release (Read 728 times)

That has nothing to do with the fee estimate code, it is a hardcoded value that serves as a user warning.

ok, here's a great example of the poor fee estimator from the node.  as i showed you from the screenshot above, the error window from Armory was saying the minrelaytxfee was supposed to be 200 sat/b.  to get around with having to fiddle with changing my bitcoind minrelaytxfee or limitfreerelay i decided  to tack another low fee of 1.3 sat/b instead and broadcast the raw hex thru a block explorer.  sure enough, i got a confirm in <10m.

This is a local thing, your own node is rejecting the tx. Fee logic is quite complicated actually, the age the utxo and the spent value in relation to the tx size as well as a min flat fee per tx all come into play. Lowering the minimum broadcast requirements below default for your node will allow you to push that tx to your node's mempool, but chances are it won't broadcast at all to the network.

These are the 2 settings you can mess with for Core:

Yeah, thanks. But why have I never had this problem before? And which bitcoind are we talking about, mine or one of the 8 connected peers?  if it's mine, maybe i could set the minfee lower to allow the tx to spread across the network?  In the past, I could submit low fee tx's like this and at least they'd get into the mempool but maybe not confirm for hours or days. Has there been some sort of default minfee coded into the more recent versions of Core?

edit:  this seems to suggest this is the reason i'm having trouble submitting low fee tx's.  and it seems to suggest that the holdup is occurring locally from my instance of bitcoind.  is there a way to lower the minfee within bitcoind to allow broadcast for these low fee tx's?  the reason i find these restrictions somewhat distressing is that i've found ALL fee estimators to be lacking due to mempool volatility.  in the past, i've gotten similar low fee tx's to confirm within a couple of blocks despite estimators predicting way more number of blocks to confirmation:

>== Added ==
   - Updated fee estimate query from node to improve estimateSmartFee call introduced in Bitcoin Core 0.15.
   - The block confirmation target slider now spans from 2 to 100 blocks (previously 2 to 6).
   - You can now pick between 2 fee estimation profiles: conservative and economical. Refer to the estimateRawFee section of
     the Core 0.15 changelog for more information. A tooltip has been added to the GUI with a quick description.
   - If your node does not support the estimateSmartFee method, the code will fallback to the previous estimateFee method.

Ah, that's the confusion. RBF means re-spending an output that is the in mempool. This error means you have not met the minimum relay fee of the node your Armory instance is connected to. Therefor the tx you created never made into the node's mempool, hence there is nothing to RBF. You have to recreate the tx from scratch with a better fee.

nothing is in there

edit:  here's the error window.  clearly i submitted with too low a fee.  but i see no way to access the enabled RBF function to resubmit:  https://imgur.com/a/vFJLUB2

Check the RBF coin control dialog, the output should be in there.

96.4 linux and it was checked.  i left it checked.

probably has to do with error as i mentioned above.  it something to the effect that whatever node i'm connected to rejected the tx b/c the fee was too low.  at that point there was no other choice than for me to manually construct a brand new tx with a higher fee to try and get it to go thru.  but then the fee i chose was still too low and the same thing happened two more times.  which is why i asked above how to use RBF to try and make it simpler; but it isn't possible given the lack of the turquoise tx in the GUI.

Implies problems. RBF tx's are always colored that way in the Transaction window.

RBF should be default checkbox-ed on the Send Transaction form. In your case maybe not?

Are you using 96.4, or something earlier? (there were bugs in RBF before 96.4)

couple questions:

i don't see a turquoise tx in main GUI.  is this b/c the error window i got when trying to broadcast this offline tx said something about "the node will not relay b/c the fee is below the minimum relay fee"?  is that error referring to my full node (one that i can adjust to allow relay) or an outside node that rejects my broadcast and terminates it?

when i open the RBF window, it just says "none".  when i click "Accept" the window just disappears with no apparent action.  i've sent RBF enabled tx's before but have never had to use it and the tx's cleared just fine.  what's going on?  i thought all UTXO's were RBF eligible?

Right click the "turquoise" tx in the in main ledger and pick "Bump Fee". You can also see RBF eligible UTXOs in the RBF control dialog that you can access from the Send GUI (the button is right under Coin Control).

What's the proper procedure to actually use the RBF feature to resubmit a failed minfee relay tx with a higher fee?

Copy/Paste your log file using pastebin.com... then post the unique URL that it creates when you save it. That might make it easier to see if anything else is causing the issue.

I was on 0.96.3

At first install attempt of 0.96.4 it couldn't write ArmoryDb.exe (as I recall, or something similar) as if it was still running in the background (I didn't check). Second install attempt didn't complain

hi there,

just updated my BTC and wallet to newest version , core works fine but wallet only goes in offline mode , cant see my balance . since im not a pro with bitcoin software , does anyone has any tips ? i have the armory wallet on expert user ....

thanks in advance

Looks like you're having a database issue. What were you on before upgrading to 0.96.4?

Hi,

Upgraded to 0.96.4 on win64
Nothing happens when I click "Send Bitcoins", except the following in my armorylog.txt:

2018-07-22 19:36:18 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3452, in clickSendBitcoins
  File "qtdialogs.pyc", line 4593, in __init__
  File "ui\TxFrames.pyc", line 150, in __init__
  File "ui\WalletFrames.pyc", line 232, in __init__
  File "ui\WalletFrames.pyc", line 347, in updateOnWalletChange
  File "ui\TxFrames.pyc", line 346, in setWallet
  File "ui\TxFrames.pyc", line 395, in setupCoinSelectionInstance
  File "CppBlockUtils.pyc", line 4140, in getCoinSelectionInstance
DbErrorMsg: >

(and I don't know how to attach the whole log file here...)

I'll just add args to feed the log/pass from armory's own config files

Usually I provide the credentials in /home/user/.bitcoin/bitcoin.conf which only contains two lines: rpcuser and rpcpassword. Then a have a global bitcoin.conf in /etc with all the options I need. To enable armory to read my credentials I copied bitcoin.conf (with only rpcuser/password) to satoshi-datadir.

You mean have args to provide the rpclog/pass in the armory.conf? Reading another .conf than the one your node is started with would not help and introduce a lot of confusion.