Update 27th February, 2025

Forget GTA VI and all that nonsense. Everyone knows the best video game ever is Tetris. And now courtesy of @wydileie it’s available on Autonomi. Not to be outdone, @josh has pitched in with his Python app. Props too to @ambled for setting up a community faucet, and @neo for starting a directory of public files. Beautiful stuff chaps and inspiring to see. :pray:

Much less welcome has been the spike in gas prices. Being tied temporarily to the blockchain for payments makes price spikes an unfortunate fact of life for now, but it has spurred the team on in putting forward designs for the native token.

Another sticking point we are working through is MAID burns yielding no ANT. Thanks for your patience with this, guys. Please see this post for more info.

Back to the good news (it’s an emotional rollercoaster this week :sweat_smile:) – we’re pleased to announce that ANT is listed on another exchange: MEXC.

Even more good news – we have a new team member Victor who is already getting stuck into the code.

And the latest autonomi release is nearly ready at the time of writing. It contains a fix to reduce client upload failures, refinements to relaying for initial connection, UPnP enabled by default in antctl, archive and files improvements and a fix for out of bounds array error in antctl.

General progress

@anselme refactored addresses, making them uniform and more logical. Now all addresses are similar and have the same API. He adapted the Python bindings and merged archives, files and datamap download in the CLI.

@bzee updated Project Dave and raised several PRs to fix some build and compilation errors.

@chriso has been working on the next release candidate, including adding fixes to reduce client upload failures. For reliability, we are defaulting to the UPnP connection protocol with a –no-upnp flag for antctl users that don’t wish to use it. Plus, the RC includes some improvements to the bootstrapping process.

@dirvine is across pretty much everything, in particular making sure that changes we make don’t have negative knock on effects elsewhere in the network. Obviously, this is crucial now that we’re live.

Ermine fixed a record_store metrics count bug. He also worked on improving the behaviour in transferring funds between nodes. We are still seeing some odd behaviour there at times.

Lajos has been active in managing the audit process, helping the auditors get on board so they can start checking the smart contract.

@mick.vandijke investigated the current high gas fees, scoped out the tasks for an idea of making relay clients share rewards with their relayer nodes, and worked on node-side code for that. He also raised a PR that means we no longer use port 4343 by default for EVM testnets, instead letting the OS decide which port to use. This allows us to run multiple testnets in parallel for testing. Another PR from Mick forces node bootstrapping to wait for the UPnP port mapping process to complete.

@roland fixed a UPnP issue, and created a PR to bake the initial bootstrapping process inside the network code to make nodes and clients behave in the same way to prevent overloading of the peers in the bootstrap cache. He also worked to make the identify client check more accurate and the relay server initialisation more explicit.

@rusty.spork has been active as the go-between bridging the community and the devs, as usual, this week reporting back on a question from @southside who spotted a discrepancy between number of stored chunks and what the metrics are reporting.

@qi_ma wrote an RFC to reintroduce the native token, inspired by the recent spike in gas fees. He also raised a PR to allow a peer’s node version to be fetched, and introduced a metric to track the percentage of nodes on each version.

@shu built out a new dashboard for ELK for processing our nginx logs. He also added internal dashboard panels to show an estimated distribution percentage of antnodes based on different bundled package versions and an estimate of percentage of network nodes that are relay nodes for the upcoming release.

And new team member Victor worked on the client Python code, running tests and working on more testing to improve the coverage.

66 Likes

First for the first time ever

25 Likes

Second. Now to read.

17 Likes

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

And thanks to the community members volunteering time and crypto to build our infant network! :building_construction: :factory:

22 Likes

Great update! Nice to hear the native token getting love.

21 Likes

Thanks as always to all concerned and a big welcome to the the new team member, Victor. I hope your time with Autonomi is productive and mutually beneficial.

Nice to see the community contributions coming in from @neo, @wydileie @josh and @ambled, even nicer to see that the native token seems to be staying pretty near the top of the agenda.

We seem to be moving forward on all fronts. Urrah!!!

29 Likes

Thx 4 the update Maidsafe devs

Warm welcome Victor, are you the Victor that @southside mentioned before? :crazy_face:

@wydileie, @josh, @ambled, @neo and @southside :clap: :clap: :clap: :clap: :clap:

Hopefully all data on the Network have atomic swap

Keep hacking super ants

20 Likes

Great update team Autonomi. You’re doing seriously amazing work on this live, and soon-to-be world changing network :clap:

Highlighting what people are already doing with the network is a brilliant way to open the update. Well done to all who are building stuff for the network!

Welcome Victor! Hope you have a wonderful time working with Autonomi.

Every cloud has a silver lining they say :smile:

Very pleased to hear Native is getting attention, but it’s great the team can work on that while also having a live network to monitor, tweak, improve, and use to show the world what Autonomi can do.

Thanks again team Autonomi… keep up the great work, and of course don’t burn yourselves out!

18 Likes

I appreciate the kudos, but I didn’t really do much. I took @Traktion’s project and stuck a web server in front of it. Kudos should go to him.

17 Likes

Nice update team. Great to see native token planning/efforts underway.

So much going on, it’s become impossible for me to keep up with everything - really rely on these updates to have any sort of big picture view of :ant: now.

Thanks to everyone for another good week.

Cheers :beers:

14 Likes

Please note though, our short term roadmap is all about stability and API etc. for now. It’s on our minds but all hands on stability and growth of use of the network right now. Then let’s see what magic we can do :wink:

34 Likes

I’m just standing on the shoulders of many giants before me! Autonomi, Actix, etc! :sweat_smile:

Great to see this out in the wild! Really great to get more folks involved in the app experience side of things! :star_struck:

21 Likes

The team is doing a great job, but words of praise are also due to the @wydileie @Josh @ambled i @neo for special contributions :clap: :clap: :clap:

Also a warm welcome to Victor to the team! :ok_hand: :slightly_smiling_face:

I didn’t think we’d hear anything about a native token so soon, hence this is great news!

22 Likes

I’m glad to hear that - I think there’s big enough tasks atm that will keep everyone busy before it’s time to get the native token rolling… =) can’t wait for the feature complete api

16 Likes

UPnP…why is it here… it’s disabled in routers and Operating Systems and no-one from Maidsafe is going to advise enabling it.

We have either Port Forwarded Nodes or Nodes that rely on relay services.

We should be empowering folks to ‘port forward’ and making it known that superior earnings going forward rely on it.

The Docs need to have a comprehensive Port Forwarding section (Currently instructions for antctl and antup are hidden away in Github)


Some port forwarding instructions built upon @neo advice on Discord:

Port Forwarding will provide the best chance to earn ANT tokens on the Autonomi Network.

You can educate yourself about ‘Port Forwarding’ by a simple web search, plenty of resources out there.

Below is how we do it for the Autonomi Network….

Example based on 100 nodes using a UDP port range of 50001-50100

——————————————————————————-

To use ‘port-forwarding’ you NEED to action the following 3 items:

  1. Internet router with a UDP port forwarding range of: 50001-50100
  2. Operating System firewall with inbound /outbound rules for antnode on UDP ports: 50001-50100
  3. UDP ports 50001-50100 entered into either launchpad, or the antctl CLI

** Failure to do any one of 1-3 means your nodes ‘will appear to work’, but will NOT receive any requests for quotes, thus no emissions or chunk storage = NO earnings

———————————————————————————

Sometimes you can do all of the above and still not earn (this happened to me)

If your public IP is between 100.64.0.0 and 100.127.255.255, then your ISP is using ‘Carrier Grade NAT’ (CGNAT).

Because of this, you have a double NAT, which makes it all but impossible for you to port-forward from your home router.

Ask your ISP if they offer a “Static IP address without CGNAT”, not only will it fix port forwarding woes, but in my experience also improves household internet experience.

————————————————————————————

15 Likes

cc @JimCollinson on the docs. Yes I think we need to explain CGNAT as well, so nice one.

upnp however is used and works in many cases and if it does then cool, bu otherwise we do need to be very clear on how to port forward (which is the best for us right now).

Nice detail here @chrisfostertv and it does need to be very much up front for home users to see.

8 Likes

I hope you keep us posted about the percentage updated? Or maybe someone from the community (@riddim ? :slightly_smiling_face:) can make tool to see this?

Works nicely for me, and when I look at the router UI, the result seems exactly the same if I would have done it manually.

4 Likes

I’m running next to no nodes anymore :wink: sorry but my view of the network is hardly very insightful nowadays …

4 Likes

I’m wondering how many of the millions of nodes are using port forwarding and if it’s over 99% should efforts be made to help the 1% using something else and isn’t it wise to focus all efforts on what is mainstream and likely to remain mainstream.

In plain text, the probability of an end user launching nodes decreases with every million current nodes in the network. What normal person is going to bother launching nodes for 1 cent tokens per month instead of buying them from the market?


Check out the Dev Forum

4 Likes