set output value using config.uint in cli

[bucko13]

Send tx behavior in CLI was inconsistent with other clients which enforce satoshis as value unit. CLI expected value in bitcoin.

[nodech]

There might be 2 reasons I see why old way is better:

1. easier to use from terminal (in BTC)
2. rpc method createrawtransaction also accepts BTCs as value.

[bucko13]

beta-13 moved over to use satoshi values in most places in the client so this is largely to keep it consistent with that. We probably don't want to go back again since that was a breaking change to begin with (https://github.com/bcoin-org/bcoin/blob/master/CHANGELOG.md)

With regards to using Satoshi values vs. Bitcoin, I have also used other clients that operate using satoshis as the default value (21.co comes to mind but I think there are others). Generally I think it makes most sense to use satoshis too because fees are typically denominated in satoshis/kb and, in terms of human error, though you should try and mitigate against this anyway, if an error were to be made, it would be way better to accidentally put 1 in when they meant 100000000 then the other way around. And in terms of it being easier to write in BTC from the terminal, given the valuation of Bitcoin lately, outside of a testing environment, most will usually be writing numbers with many digits anyway.

Anyway, my feeling is that having consistency around the API should be the priority and then leave it up to devs to change the formatting depending on their use case.

[chjj]

I think we should keep it denominated in bitcoin. Writing satoshis on the command line can be painful.