My current max fee is 0.0043584 BTC/kB
This is tedious (math is hard) to translate to Sat/B for users, which most sites use by popular convention. This will alleviate further fee confusion and help people conform to the same known glossary.
Examples:
https://bitcoinfees.21.co/
https://blockchain.info/tx/68973cd03a6d264c1396cb1e60f27fe87214f90aa20e70abb39cc201c706a1c5
you can change the issue title and edit your original post... there is no need for a new issue.
sat/byte should be standard imo.
I agree.
we could also add the color codes used in https://jochen-hoenicke.de/queue/#24h
I have a commit for adding sat/byte on my repo for my own use (my-tweaks branch). I avoided submitting a PR on this because I thought the general consensus was that it was not wanted. I'd be happy to submit a PR on it so that I don't need to keep my own version. Here is link to commit - only one line changed anyway.
https://github.com/neocogent/electrum/commit/2274c312ea390169ade73fabb1764b3db8fbce7b
Personally, that commit would be tipping point for me using Electrum over Blockchain, who has a very friendly fee calculator at the moment.
Would you consider cherry picking that commit into an updated repo, and making a PR for it, @neocogent ?
I've rebased as a fresh branch called fee-sat-byte and created a PR for this one line change. Even if it's not merged soon you can pull this into your local repo as a branch with:
git fetch upstream pull/2667/head:sat-fee-byte
and then test locally.
Tested on my local wallet and looked ok on my tx dialog preview.
IMHO the fee should be set by entering "satoshi per byte", anything else results in tedious math, or overpaying.
tedious math
0.00123456 BTC/kB = 123 satoshis/byte
What I did in my brain: "read the first 5 digits after the decimal point."
So tedious.
Note: I don't care either way, so I have no opposition to switching to satoshi/bytes... but the argument "that maths are hard" is silly. It's just multiplying by 10,000 which literally means "move the decimal point 5 places to the right" or "read the first 5 digits after the decimal point"
@dabura667
IMO The math isn't hard but if you don't use it every day then remembering what factor to use leads to errors. It's not uncommon to be looking at the amount and be thinking "now was it move 5 dec places or 3 or 4". If I did a tx every day I'd no doubt keep it fresh in mind but when doing one every couple months I always have to work it out again, which isn't hard, but then try to be sure I'm not making a silly error. So that's why I made a sat/byte PR - no chance of mistakes.
@dabura667
It needs to be understood. Every single time you require a user to manually do something, they will screw it up. When it comes to money, you want it standardized, simple, as little work for the user as possible. :)
PR was merged after corrections
Most helpful comment
sat/byte should be standard imo.