Update 20th February, 2025

Good news: ANT is now tracked on CoinMarketCap and CoinGecko. We are in conversation with two more exchanges, and we’re talking to our partners again about data uploads - for real this time.

For those who missed the X Spaces on Wednesday, there’s a recording now available. We’re planning several more of these half-hour explainers. You can attend without an X account so do tune in if you can.

Valentine’s Day :heartbeat: (cos we love ya) saw the announcement of rewards distributions. Hopefully those of you participating in the beta who have submitted your wallet address will have received yours now. If you haven’t done that, please do so. Holders of MaidSafeCoin who sent their coins to the burn address also started receiving ANT on this date. Any issues with folks who burned not receiving airdrops will be addressed. We are working on a process to remedy and will announce when ready Any Qs please ask.

Another post worth noting in case you missed it in the absence of updates, is NFT claims for MaidSafe Shareholders and those part of Loan Agreement using MAID by @bux. If this affects you, make sure you’re up to speed.

The Autonomi network is growing at a remarkable pace! With 5,187,900 nodes now powering the network (at time of writing), we’re building one of the most decentralised, resilient, and secure infrastructures in the world. This is just the beginning. The future of autonomous networks is here!

General progress

@anselme has been working on pointer put resiliency improvements, file API renames/polish, and fixing outdated Python docs.

He’s also drafted docs for how data works on the Network, including self-encryption and datamaps, and tested upload and download from the CLI on the live network.

@bzee has been debugging some problems on the network with client uploads and low-level networking.

@bzee and @qi_ma have noted that uploads become less successful over time as the network grows. We think this is to do with replication choking when new nodes join. Qi raised a PR as an attempt to resolve it.

@chriso has been fixing problems in testnet-deploy that occurred from a huge NAT refactor we did. He’s also looking at upscale testing to try and ascertain whether some performance issues we have noted, which were not apparent before, are due to some kind of regression.

Ermine continued working on his PR to replace RPC server with metric server in antctl, and also cleared a few issues in CI.

Lajos worked on implementing and testing an API to query the total circulating ANT token supply and also put some hours into the Claims and Foundation Emissions contract, which is now ready for audit.

@mick.vandijke worked on updating the service manager crate to optionally stop restarting crashed services. Now we just need to listen for and pass the service exit code to the antctl. He also tested the limits of UPnP and worked on trying to get antctl to recognise when an antnode fails due to a UPnP error.

@qi_ma raised a PR to address some logging and CI test issues. He also reviewed a PR which could affect connection pruning related to relay. Plus he issued a fix to resolve a suspicious deadlock, which may address some of the upload failures observed during scaling tests.

@roland was checking the behaviour of the relay servers and how they handle clients dropping off.

And @shu has been guiding the rest of the team in investigating excessive CPU usage and other resourcing issues.

Big shout to markwylde who brought history to registers on the CLI and HEX for register content. :pray:

55 Likes

Holy mackerel I wasn’t expecting this!

Thanks so much to the entire Autonomi team for all of your hard work! :woman_factory_worker: :man_factory_worker: :woman_factory_worker:

Remember to get plenty of rest and take time off so you don’t burn out! :fire:

20 Likes

Thank you team! Your hard work does not go unnoticed. We are in such a good place now. Go Autonomi, cant wait until they add Autonomi in the English language dictionary soon, lol

18 Likes

Third. now to read.

10 Likes

Updating the network. This is now still a manual process I assume. There were once proposals for automatic updates is this still the plan? And if 50% of the nodes are updated are they still compatible or do you basically create 2 networks?

10 Likes

Will download also be looked at since it also gives error and such from time to time, maybe it will get a similar fix as uploads when that bug is found and solved.

6 Likes

Regarding how much network size and rewards have been stirring discussion, I expected to hear a bit more about it, than this:

5 Likes

Excellent update - thank you as always to ALL involved whether full-on devs or those who enable them to get on with it

I’d like some analysis of just where these 5m nodes have suddenly appeared from though. It is undeniably a triumph for those that created code that has scaled so well. Heres hoping they will still scale well when under realistic load.

Good to see

My impression was that small uploads were occasionally problematical and larger ones just didn’t work at all.

And yes, this does deserve congratulation, well done @markwylde

14 Likes

me too , its clearly automated, to speculate imo likely hosted in large Hyperscalers or colo cloud sites?

8 Likes

I suspect we will all have ideas, I have not given it much thought, but who knows really. It’s certainly not us, but … where we are heading in some ways I hope we never find out but I also hope the network handles mass churn etc. as well.

Not trying to be obtuse, but I am not motivated myself to really know this answer, but it’s fun guessing for sure.

24 Likes

It’s great that you says it outright, because in the future there will be accusations of pre-mining and this will be one of the points why vampire attacks will need Fair Launch


Check out the Dev Forum

8 Likes

Would be good to know the node-launchpad and antctl software download metric counts from the autonomi.com website weekly, and compare those numbers with antnode actual growth, , same for github downloads…
as of Feb 20 1228 EDT Discord stats:
48 Pioneers
96 TrailBlazers
222 Online (others) at the moment
= 366 engaged and visible community members (snapshot)

5,000,000,000 antnodes divided by the above (not inc anonymous players?)
= 13661 antnodes per visible member engaged

so not likely those visible are driving ALL the antnode growth.

4 Likes

Would be a mistake for Maidsafe to care perhaps?
Privacy tech where the developers seek out node operators.

We users though, I think thats fair game, who would not be curious.

7 Likes

I think we need to shrink the random rewards see if they stick around :thinking:

4 Likes

That’s where the blockchain payment parts would allow detectives to seek out wallets getting lots and lots of small rewards and see where they go and so on.

I remember back in our ico days, there was so much of that. I remember we were apparently reselling mtgox coins or something and it did spook folk who believed it. We cancelled some buys and returned coins to some big names. Then the binance guy or something (cannot remember the actual one) came out shouting, it’s us, it’s us it’s not mtgox, but still many crypto experts and publications kept posting we were mtgox folk or something.

It was wild and I am sure we will see many more of those things happening. At least it was eventually shown to be a false accusation, but I still remember those screenshots entitled “I am genius, I have proof they are thieves” or whatever it was :smiley: :smiley:

Looking back it’s hilarious, but also it shows how bad news and accusations travel faster than light and Einstein was totally wrong :smiley: :smiley:

15 Likes

old Italian proverb, “throw enough spaghetti at the wall, and some of it will stick,”

imo a clear fair launch statement with transparency from Maidsafe management , keeps the spaghetti from sticking. :wink:

8 Likes

Wow, it’s great to have a Thursday update again. Hope it keeps going with the regularity that has been so wonderful for the last few years.

16 Likes

I’m not concerned too much about Where the recent rapid bump in nodes is coming from, except as a cautionary point of a potential of bad actors who could do a destructive rug-pull by withdrawing a large percentage of nodes to disrupt the network at a crucial phase while the network is still relatively small. Any thoughts on that?

8 Likes

There are people holding millions of tokens, it is more likely that one of them is protecting his investment from just such an event caused by many small players. If you look at the sales we have people selling at every 12 hour payment - they have most likely launched servers for $50 (running 3000 nodes and making $600-700 per month at current prices per server) and are draining the uniswap liquidity by playing short-term against the network. The big player is gradually draining the well of free money for those players who would surely shut down their servers at the first sign of potential loss…


Check out the Dev Forum

9 Likes