pull down to refresh

331 sats \ 4 replies \ @Murch 10 Mar \ on: An open-source and free alternative for tracking Bitcoin metrics bitcoin bitcoin_beginners lightning charts_and_maps Construction_and_Engineering

Very cool project! I was leafing through your dashboard and had a few suggestions:

  • [1]: Given that the minimum transaction relay fee of Bitcoin Core is now 0.1 s/vB, perhaps it would make more sense to express the AVG TX FEE with at least one decimal precision.
  • [4]: I think in the Mempool status chart, "Mempool size" is referring to two different things. The mempool limit of 300 MB refers to the total memory usage of deserialized transactions, not total virtual size of transactions. Since Mempool Space is currently reporting about 35 MvB of transaction data, but 185 MB of memory usage, I think you’re showing the former, but comparing to the limit for the latter.
  • [6/7]: Active Nodes by Country is interesting, but node density by country seems a bit odd. When speaking about density, I would have expected the node count per capita rather than per country. E.g., France and USA’s node count per capita is very similar, but USA has twice the nodes of Germany, but 4× the people.
  • [8] Similarly, El Salvador has a tiny population compared to Brazil and USA, but a respectable count of businesses on the BTC Map.
write
compose
48 sats \ 3 replies \ @Khunsa OP 12 Mar

Thank you very much for your comment, it was very helpful. Fixing the mempool status was a bit complex because I ran into some issues in that part, but I managed to adjust it. Even so, I still have a couple of small doubts, and I’d like to know whether the fix looks correct to you or if there is still something I should review.

reply
129 sats \ 2 replies \ @Murch 12 Mar

Yeah, looks much better! I’m just not sure about “official” mempool usage. It’s just the statistics of wiz and Simon’s node that we are looking at. ;)

The node density is cool now. It caught me by surprise how many countries had more nodes than the USA. Perhaps add a decimal precision?

reply
27 sats \ 1 reply \ @Khunsa OP 13 Mar

Thank you very much for the support. Yes, those are UX details that slipped past me, but I’ll be correcting them shortly. Your observation about the mempool helped me a lot I learned a few new things, such as what you mentioned about Simon’s mempool 😅 and that everyone tends to run their own version.

Regarding the density in decimals, would it look something like this?

75/M → 75 ÷ 1,000,000 = 0.000075

Wouldn’t that become a rather large number of digits visually? I mean in terms of responsiveness and readability wouldn’t it make the value harder to interpret?

reply
6 sats \ 0 replies \ @Murch 13 Mar

I meant that you could continue doing “per million”, but add a decimal like “mm.d/M” so France through Canada would be disambiguated a bit more.

reply