While we all wait for improvements to uploads to be rolled out (the latest fix is looking good but was not quite ready for prime time at time of writing) we have a new dev tool to announce. Ant Analyzer is a CLI tool created by @anselme to read and decode addresses on Autonomi Network. It processes addresses to identify the type of data located there (e.g. Chunk, DataMap, Public Archive). It also decodes content stored at these addresses, such as files, metadata or nested structures, and can inspect uploaded files or folders to reveal their structure, metadata and chunk distribution. Builders will be able to use this tool to ensure files are correctly chunked, encrypted and stored on the network for debugging purposes and to better understand how data is stored on the network.
For those that missed the explainer on emissions, we currently have four emission services running. Every 120 seconds, each service initiates a reward round, selecting 100 random nodes from the live network. Each selected node earns 0.05662462854 ANT tokens. Over the next 12 weeks, we will be correcting the emissions error spotted by the community so it matches the plans in the white paper.
While the tasty carrot of encouragement 
remains our social tool of choice, weāre also unveiling a wee punitive stick to persuade upgrade laggards to do the right thing. From Monday 24th March, to qualify for emissions payments you will need to be running the latest node version. More in this post, where youāll also find info about the Impossible Futures programme to support app builders, which kicks off on April 22nd.
Please read @rusty.sporkās post about a vulnerability in cryptowallets, including Metamask, on Chrome browser. It includes a simple test to see if you may be compromised. Better safe than sorry.
Finally two big thumbs up (maybe three if youāre using Stable Diffusion) to @happybeing for his release of dweb which allows viewing and publishing of websites created using standard web tooling (e.g. Publii, Svelte, static site generators or plain HTML/CSS) on Autonomi, and to @bochaco for pushing at least two new releases of the Docker-based Formicacio node manager in the last week. 
General progress
Anselme is working on a low-level network analyser to track Kad queries. The aim is to provide information about overall network health, the parameters we need to set to maximise performance, resilience of our API tools, and how our network works in practice.
In his spare time he also created Ant Analyzer, a versatile tool to read and decode addresses on Autonomi Network @vphongph has been testing this tool and is writing a tutorial on how to use it.
@bzee continued implementing Node.js bindings in the API. Most are now complete.
@dirvine has been digging deep into the libp2p implementation of Kademlia in search of efficiencies in the way nodes manage their routing tables.
@chriso continues to push fixes and improvements in our test networks and client as we seek to improve upload performance.
Ermine raised a PR to refactor verify_data_location and verify_routing_table testcases with nodespawner on the road to finally removing the rpc code.
Lajos has been working on security considerations for the Foundation emissions as well as smart contract architecture for the Impossible Futures programme.
@mick.vandijke has been amending the emissions process so that it agrees with the original scheme set out in the white paper. Mick also found and fixed an error in testing which the emission service failed due to the client failing to populate its routing table in time.
@qi_ma raised two PRs (2846 & 2848) to address node-side issues that might result in the payment to be rejected, causing upload failure. Qi and @chriso also investigated the effect of large churn events on download and upload performance, finding that recent fixes do seem to improve the situation. Plus Qi advised community members on what to look for in the logs to track whether chunks are being returned properly.
@roland raised a PR to return exit codes on failed uploads and downloads for debugging.
And @shu worked on further revision of documentation for UPnP simulation. He also worked on a POC for having Port Restricted Cone NAT simulation in Digital Ocean, where we run our tests. This means the team will eventually have UPnP, Randomised Symmetric NAT, Port Restricted Cone Nat, and Full Cone NAT simulation on Digital Ocean for internal and production testnets.
