0

My blockchain isn't synced yet. Thus, fee calculation didn't work. Therefore, I chose user defined fee and entered what btc.com suggested.

But my bitcoin-qt (v0.20.1) went for 255 satoshis instead of some 10 thousands or so. (A rough guess, since I can't recall the actual amount any more.)

The question is: Did I encounter a bug or is there some hidden magic involved?

  • 1
    How did you enter it? – Pieter Wuille Nov 8 at 21:56
  • 1
    How large is the transaction in kvb? A 0.728 kvb transaction with 350 sat/kvb would be 255 satoshi. Could this be a confusion about units? – Pieter Wuille Nov 8 at 22:06
  • 1
    This does seem to be a confusion about units! Typical feerates on the network right now seem to be around 10000 sat/kvb at least (judging by jochen-hoenicke.de/queue/#0,24h). Many sites use sat/vb rather than sat/kvb or BTC/kvb. – Pieter Wuille Nov 8 at 22:13
  • 1
    My theory: if you actually entered 350 sat/kvb in Bitcoin Core, it may have rounded it up to 1000 sat/kvb (which is the absolute minimum for it to be relayed on the network, even absent any mempool pressure). If the transaction was 255 vbytes (which is very plausible), you'd get 255 sat as fee. – Pieter Wuille Nov 8 at 22:17
  • 1
    If you paid a fee so far below market rate, there is no reason why it would confirm. – Pieter Wuille Nov 8 at 22:22
1

I believe you're confusing units here, and entered a value intended as sat/vB in a place that expects sat/kvB.

Perhaps you intended to use 40 sat/vB (=40000 sat/kvB, or 0.0004 BTC/kvB), which would translate to around 10000 sat (or 0.0001 BTC) for a typical transactions.

When interpreted as 40 sat/kvB, it would be far below the minimal relay fee on the network (1 sat/vB, 1000 sat/kvB, 0.00001 BTC/kvB). The sender software you used may have rounded it up to 1000 sat/kvB instead, and used that - which may translate to 255 sat for a typical transaction. That is far below the current blockspace market rate, and may explain why your transaction hasn't even propagated (blockchain explorer sites don't even show it as unconfirmed).

| improve this answer | |
  • 1
    Maybe jonatack is working on changing the units in bitcoin core. Not sure if there is already an open pull request. Else we would need a calculator to do all the conversion in bitcoin core soon for users :) – Prayank Nov 8 at 22:59
  • 1
    Most of the tools, websites, other wallets etc. use sat/vbyte so there was some discussion about it here: github.com/bitcoin-core/gui/issues/64 – Prayank Nov 8 at 23:42
  • 1
    If you use the PSBT or raw transaction RPC API you can see the transaction before deciding to sign and/or broadcast it. I don't know about the GUI. – Pieter Wuille Nov 9 at 0:02
  • 1
    You can start by opening an issue on github.com/bitcoin-core/gui. Beyond that, either doing it yourself, or paying someone to do it :) – Pieter Wuille Nov 9 at 0:13
  • 1
    I don't understand your question. – Pieter Wuille Nov 9 at 0:23
0

Many thanks to Pieter Wuille for his quick help.

I got confused with units. The correct input would have been some ten thousand satoshis for bitcoin-qt is calculating in Kilo Bytes.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.