pull down to refresh

Since BTC Frame is no longer free or open source, and because I always liked how friendly it was for displaying metrics, I decided to build my own open-source and free version for anyone who wants to take a look. I’m sharing it here: https://www.satoshidashboard.com/ . The idea is to create something useful for the community, something that can grow over time and keep adding value with more features, panels, and tools. If you have ideas or suggestions, I’d be happy to hear them.

New project update: #1454421

reply

Great work! I could be wrong but some of the colors seem off on the maps ..like some of the lighter colored countries are showing more density numbers than the darker colored ones

reply

Thank you very much for the support and the observation. I will correct it. If it’s not too much trouble, could you indicate it more specifically with a photo reference so I can inspect it precisely? Sometimes screen colors differ, and that might be why I didn’t notice it.

reply

This could be because I'm in dark mode but for instance shouldn't the US be darker colored than Canada and Russia?

reply

By the way, do you use any extension that changes the colors of web pages? What browser are you using? What device are you using? Could you confirm whether you’re viewing it in light mode or dark mode? I’m reviewing the issue, and it might be related to the automatic color settings, so that information would help me clarify things better.

reply

I use the experimental force-dark mode in brave browser on a PC with system darkmode enabled as well. Hope that helps!

reply


Great catch. I honestly didn’t know this issue existed for dark color modes. I’m going to focus on fixing it, and I’m attaching an image here showing how I see it from light mode. I should be able to correct it soon, since it’s a pretty important defect right now. Thank you very much for the heads-up.

reply
331 sats \ 4 replies \ @Murch 10 Mar

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.
reply

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

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

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

Great work!! I check it daily now!

reply

Thank you for the support. By the way, we have an app update today with some small adjustments that were complicated to implement but are quite good.

reply

fantastic I’ll check it out tomorrow

reply
6 sats \ 1 reply \ @OT 10 Mar

I like it! The first page is nice and simple.

reply

Thank you very much. Yes, that’s the idea: to make it simple, friendly, and easy to read all the Bitcoin charts. Recommend the app to your friends

reply

Great work, love it!

reply

Thank you very much to you, recommend them to your friends.

reply
reply

Your reponsive look good on your mobile. By the way, I updated the app and updated the AVG TX FEE data.

reply

Do you mean freemium?

reply

If you're referring to BTC Frame, yes, basically, before they had several windows that one could see completely for free. Nowadays, you have to buy their device in order to view it. That's why I created Satoshi Dashboard, so that people who liked that app could continue viewing this data for free.

reply

Very nice !

reply

Thank you very much, sir. There is a new update for the app today. You can go check it out.

reply

Pretty slick, thanks for sharing.

reply

Thank you very much. By the way, we have a new update today. Also, feel free to recommend it to your friends.

reply
6 sats \ 2 replies \ @035736735e 13 Mar -42 sats

You did not shrug off Murch’s mempool and density feedback. You went back, wrestled with the implementation, learned about how Mempool Space is actually just one node and that everyone runs their own version, and then came back and asked if the fix made sense. That is the right instinct. Metric dashboards live or die on the details and you are clearly willing to think in terms of what the data really means, not just what looks nice on a chart.

You are also pushing on the right questions around UX. The node density example shows it. You understood the point about per capita but you are also thinking about how it will actually read. Throwing raw numbers like .000075 on the screen is technically accurate and completely useless for a casual viewer. That is not you being sloppy, that is you recognizing that a dashboard is a communication tool, not a research notebook. It would be much clearer to express density as nodes per million people or per 100 000 and show maybe one decimal. Let the user see quickly that El Salvador is punching above its weight without needing to parse micro notation.

The other thing worth saying directly is this. You are filling in a structural gap. When projects like BTC Frame flip from open to closed, it is not just that access costs money. It is that the community loses the ability to inspect, fork, and adapt the tool. Over time that pushes Bitcoin telemetry into the same pattern as the legacy financial world. Nice interfaces, but controlled pipes. An open dashboard with an open codebase keeps a piece of the observability layer in the commons where it belongs.

So the next logical step is to make it easy for people to build on what you started. That could mean

A public repository with issues labeled for first time contributors

A simple contribution guide for proposing new panels or data sources

A roadmap where ideas like new charts, density refinements, and display modes can be discussed before you implement them

You clearly care about UX and are responsive in the comments. Channel that into a small but healthy contributor culture and this can become the shared frame a lot of people wanted BTC Frame to be.