Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: Bambolinaclava on March 29, 2024, 09:41:35 AM



Title: fee estimation disabled
Post by: Bambolinaclava on March 29, 2024, 09:41:35 AM
HI,
i tied a knot with the raspibolt guide, the blockchain is synced and so is electrs. I have the problem that the node tries to synchronize but fails, I see that it tries but fails, because from the logs it says: fee estimation disabled. how can I solve it?
Thank you
HI


Title: Re: fee estimation disabled
Post by: nc50lc on March 29, 2024, 11:56:14 AM
Blockchain is synced but the node fails to sync?
Anyways, based from the error, Bitcoin Core may be having trouble providing fee estimates which could be an issue in Electrs.

What are the config set in your bitcoin.conf file? (do not include private lines, of course)
Or at least tell if it has any settings that'll lead it to skip receiving mempool transaction like blocksonly=1.


Title: Re: fee estimation disabled
Post by: Bambolinaclava on March 30, 2024, 09:12:20 AM
HI,

yes the value of blocksonly is 1, should I set it to 0?

thanks

hi.


Title: Re: fee estimation disabled
Post by: ABCbits on March 30, 2024, 09:54:09 AM
HI,

yes the value of blocksonly is 1, should I set it to 0?

thanks

hi.

Yes, you should set it to 0 and restart Bitcoin Core process. It's needed in order to get unconfirmed transaction which needed to perform fee estimation. Take note it may take a while before your node receive most unconfirmed transaction which needed for better/more accurate fee estimation.


Title: Re: fee estimation disabled
Post by: Bambolinaclava on April 02, 2024, 06:34:18 AM
hi, ok thanks now it works.
curiosity. why is the value set to 1 in the raspibolt guide if I don't like it?
Thank you
HI


Title: Re: fee estimation disabled
Post by: nc50lc on April 02, 2024, 06:42:54 AM
hi, ok thanks now it works.
curiosity. why is the value set to 1 in the raspibolt guide if I don't like it?
That's for optimization purposes, it's way faster to sync that way.

Also, if you're talking about their "bitcoin-client.md" guide from Github, here: github.com/raspibolt/raspibolt/blob/master/guide/bitcoin/bitcoin-client.md (https://github.com/raspibolt/raspibolt/blob/master/guide/bitcoin/bitcoin-client.md#reduce-dbcache-after-full-sync)
It's noted to comment-out the config after it fully synced the blockchain since the node shouldn't be needing those optimizations later.