pull down to refresh

250 sats \ 4 replies \ @sime 30 Nov 2022 \ on: estimatesmartfee vs Trezor Suite bitcoin
Funny. I was diving into this recently as well. Though for slightly different reasons.
estimatesmartfee returns in kilobytes. You need to divide the result by 1000 for it to make sense.
From the manual:
Estimates the approximate fee per kilobyte needed for a transaction to begin confirmation within conf_target blocks if possible and return the number of blocks for which the estimate is valid.
Trezor Suite uses that exact same method for guestimating fee prices.
write
preview
0 sats \ 3 replies \ @ek OP 1 Dec 2022
Oh, wow, thanks, you are right! Missed it mentioning kilobyte..
Long term mystery solved. Just set up new monitoring for my node and encountered this issue again. Except this time, I can ask people on SN :)
What were your reasons?
reply
0 sats \ 2 replies \ @sime 1 Dec 2022
Complaints that fee estimation in Trezor Suite are not that accurate.
Wanted to compare what is offered natively in Bitcoin Core vs Trezor Suite. And the answer is that it's 1 to 1.
You can confirm it on this endpoint: https://btc1.trezor.io/api/v2/estimatefee/6
6 = conf_target
reply
0 sats \ 1 reply \ @ek OP 1 Dec 2022
Ah, haha, nice! Are you working for Trezor? Or just a pleb wanting to verify things themselves?
reply
3 sats \ 0 replies \ @sime 1 Dec 2022
The former.
reply