How to get fee rate in KB [SOLVED]

[bere3kin]

Hello everyone, as I know command

Code:

electrum getfeerate

gives a rate in sat/byte, but is there any way to get it straight in sat/kbyte?
Is divide it to 1000 a good idea when actual fee for e.g. will be not 3147 but 3000 rounded to 3 and divide gives 0.003 sat/kbyte, or I am wrong and it always will be 3000?
Thanks.

[BitMaxz]

So you mean you want it to make it fix to 3k sat and remove 147?
I don't understand but I think you can't be able to do that you only have two commands for "getfeerate" command that you can add

Here are two commands you can add for "getfeerate" command.

--fee_method
--fee_level

Sample command with result:

Code:

$ ./electrum getfeerate
26000
$ ./electrum getfeerate --fee_method "static" --fee_level 0.1
10000
$ ./electrum getfeerate --fee_method "static" --fee_level 0.4
50000
$ ./electrum getfeerate --fee_method "static" --fee_level 0.8
150000
$ ./electrum getfeerate --fee_method "eta" --fee_level 0.1
1081
$ ./electrum getfeerate --fee_method "eta" --fee_level 0.4
10705
$ ./electrum getfeerate --fee_method "eta" --fee_level 0.8
21190
$ ./electrum getfeerate --fee_method "mempool" --fee_level 0.1
1000
$ ./electrum getfeerate --fee_method "mempool" --fee_level 0.4
1000
$ ./electrum getfeerate --fee_method "mempool" --fee_level 0.8
20000

Source: https://github.com/spesmilo/electrum/pull/4264

Or if you want to add that you can request it directly from Electrum GitHub here https://github.com/spesmilo/electrum/pulls

[bere3kin]

No, I just trying to make a code clear and thinking about getting response in Kbyte. Looks there is no problem with fee ended by zeros, so there is no problems to divide it.

[nc50lc]

Hello everyone, as I know command

Code:

electrum getfeerate

gives a rate in sat/byte, but is there any way to get it straight in sat/kbyte?
Is divide it to 1000 a good idea when actual fee for e.g. will be not 3147 but 3000 rounded to 3 and divide gives 0.003 sat/kbyte, or I am wrong and it always will be 3000?
Thanks.

It's already showing the estimated fee rate as sat/kvB like in your example above, it's 3147sat/kvB. (electrum/commands.py)

You mean BTC/kB, or better BTC/kvB?
Like 0.003 BTC/kvByte not 0.003 sat/kvByte as shown above which is totally way below a "standard transaction's" fee rate. (should be 0.00003BTC/kvB for 3000sat/kvB or 3sat/vB)

Anyways, rounding it may introduce inaccuracy when it comes with huge transaction sizes, but it's fine in most cases.

[bere3kin]

Found nothing bad to divide to 1000 and no problem. Thanks!