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