Armory already asks for fees to be raised if it deems to be necessary, I've had that happen once. So that means the current algorithm of fee calculation isn't the best one?
Armory's fee estimation is a based on a reimplementation of Core's own rules from over a year ago. That method is not sustainable long term for many reasons.
Can't Armory interact with bitcoind in order to calculate fees? Through the estimatefee and estimatepriority commands?
Doesn't armory already use bitcoind's estimatefee for calculating fees? I thought that it only uses the default when bitcoind doesn't have enough data to estimate the fee.
Only when Armory is setup to connect to the RPC, which takes place when bitcoind is managed by Armory.
Proper fee estimate is something I consider critical, it shouldn't rely on an optional feature. Auto bitcoind was developed and will remain a convenience feature, this is not something I want to force users into. It already has demonstrated itself unstable several times in the past.
Also, relying on the RPC is in direct conflict with blocks over P2P, so I don't intent to increase Armory's dependency on that.
