Basically, This estimates the cost to go .75 MB deep in the chain at the time of the request. Each block usually takes 1mb off the chain, so it's isn't very aggressive and transactions can take some time to confirm. Being not aggressive kind of helps not contribute to unnecessary blockchain bloat.
I think you'll be shocked at the price difference and the speed these estimates confirm!
https://freebitcoins.com/xchange/api/v1/btcfee ({"satsPerVbyte":"102"} at the time of this post)
I think you'll be shocked at the price difference and the speed these estimates confirm!
https://freebitcoins.com/xchange/api/v1/btcfee ({"satsPerVbyte":"102"} at the time of this post)
I really like the idea behind it; it's pretty much what I've been doing manually looking at Johoe's mempool stats. However, for some reason, it seems to be returning 10 satsPerVByte right now, despite there being 45+ MB of transactions greater than paying greater than 10 sat/byte.
That's exactly what I did as well. The same website too!
Good eye, something broke, Xploited is fixing the API call right now... because your right, 10 looks hella low atm.
I forgot to mention, we have it set to a minimum of 10, even if the network is lower. I've just seen the network blowup in the low numbers too fast... 10 seems to be a decent number.
I'll post when she's fixed... it should just be a minute.
Fixed. https://freebitcoins.com/xchange/api/v1/btcfee
We also bumped the estimator up the .75 MB deep to 0.50 MB deep.
Good luck Ethan.