I’ve noticed autonomi.com doesn’t seem to be updating the Nodes Online value anymore. It’s been 4,465,900 for quite a while, even during new node version rollouts.
Why? Is there a more accurate alternative to watching the network stats?
I’ve noticed autonomi.com doesn’t seem to be updating the Nodes Online value anymore. It’s been 4,465,900 for quite a while, even during new node version rollouts.
Why? Is there a more accurate alternative to watching the network stats?
The site is updated manually at the moment. We have written an internal POC service that returns those two stats (network size & raw capacity figures) when requested via HTTP call.
However, it needs to get integrated with the main website provider, and likely needs a signed certificate for the service itself so the entire home webpage can be dynamically updated in near real time (say up to date stats within 1 hour (cached)).
No ETA yet as to when that will get done just yet, but we are aware off the issue and concern.
Please don’t waste dev time on this. Just update it now and again. Thanks!
I disagree. I would like the information and don’t consider it a waste of time. Please get to it when you can, thanks!
I agree and it is in the works according to Shu. We may think it’s a waste of dev time but it is important for PR not to appear amateurish. EDIT: and a useful for the community, showing others etc.
It could also come across as having something to hide, when progress shows anyone paying closer attention that things are progressing well.
Ok, but it may take days to write the code, which takes 5 mins to update manually. Just feels like spending 5m once a week would allow time to be better spent elsewhere. Just my opinion though.
Sure but then it’s another thing they have on their minds, pushing toward context switching inefficiency. It’s not necessarily a priority, but the sooner it can be automated the sooner there’s 1 less distraction lingering on the devs’ minds.
Yeh, but that isn’t happening and that 5m per week soon adds up too. They have recognised that and so all is good, or will be when it happens.
In the meantime we have the estimates that NTracking provides. Maybe we have a quick poll every day from people running NTracking and people can take the average of those? I’ll go first: 3.47M nodes.
Shu kindly created this, from Discord:
Percentages:
its impressive how fast the upgrades happen when the ant is taken off the table for the old versions
Absolutely, with the minimum version being 2025.6.1.3 for emissions rewards… folks moved super quickly to do the upgrade, which is what we want!!
95% is an internal metric / threshold, though one could argue what is truly required to great length, .
We think there will be minimal impact to the network at 95% being at 2025.6.1.3++ and it will allow us to remove the code base / PRs dealing with the legacy external address connection
manager.
@Shu please let us know when we hit the 95% target
The dev team isn’t spending time on this as much as one would think. Its been Jim and company who have been updating the website with the stats daily or periodically, though I believe Jim is now on vacation so… (I am not sure who steps in to full fill this specific task as backup but I am sure someone will in his absence).
No one is trying to hide the daily stats off the network, its just a been a matter of time and resources here. Accuracy is important to us, and to the stakeholders (community) in general.
Yes, we have recognized that this is not worth the daily input each day, but the solution isn’t so simple as is to implement based on all the other priorities off the network at hand.
Regardless, this is not an easy ask from day one. The sample off network size and raw capacity have to be taken from 100s of antnodes if not more and then post processing on that, prior to even being displayed by a website. In addition, the whole workflow needs to be in a high availability environment and multiple layers of cache and error handling so the main website doesn’t simply give an error or 0 value. The POC accounts for a lot of this but its a POC at this point.
There is a lot of different priorities and tasks in-flight, this is just one of the many, so we will see how fast it gets handled, and when.
Big sticks usually work
Given that the network regularly gets reduced by 10% or more (eg. when there is an upgrade going on or the node whale has a bad day) I think it will be fine with pulling the plug on 5%.
I think we just passed the 95% mark, .