Bitcoin Forum
May 25, 2024, 06:03:25 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: estimatefee not working  (Read 543 times)
btc_enigma (OP)
Hero Member
*****
Offline Offline

Activity: 688
Merit: 567


View Profile
February 29, 2016, 05:13:59 AM
 #1

Hi,

I am using bitcoind 0.12 and tried estimatefee  1 , this is returning -1 on my node.
Same result on https://chainquery.com/bitcoin-api/estimatefee/1

Its returning results for block number 2 ownwards. Is this excepted or a bug ?

Foxpup
Legendary
*
Offline Offline

Activity: 4368
Merit: 3045


Vile Vixen and Miss Bitcointalk 2021-2023


View Profile
February 29, 2016, 06:58:03 AM
 #2

It is expected if no reasonable fee is likely to get your transaction into the next block, which is currently the case as there seems to be unusually high transaction volume.

Will pretend to do unspeakable things (while actually eating a taco) for bitcoins: 1K6d1EviQKX3SVKjPYmJGyWBb1avbmCFM4
I am not on the scammers' paradise known as Telegram! Do not believe anyone claiming to be me off-forum without a signed message from the above address! Accept no excuses and make no exceptions!
btc_enigma (OP)
Hero Member
*****
Offline Offline

Activity: 688
Merit: 567


View Profile
February 29, 2016, 07:36:21 AM
 #3

It is expected if no reasonable fee is likely to get your transaction into the next block, which is currently the case as there seems to be unusually high transaction volume.

How could it calculate fee for two blocks and not give a fee estimate for one block ? Also I don't see any spike in tx volume , its been same as last few days ...

I am not sure how the estimatefee algorithm works but I would assume it would track transaction in mempool to see how many blocks it took them to confirm and then take an average of fee/byte for each number of block.


Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!