Tuesday saw a fascinating Spaces session featuring @traktion (IMIM), @rreive (CanMan), @edmund_sutcliffe (REGRU) and James Stafford (SOMA) speaking about their projects. Do have a listen if you didn’t catch it. An X account is not required.
REGRU was also the subject of an AMA session with Edmund on Wednesday.
Elsewhere on the projects front we have AntAI a decentralised, open-source AI assistant built for privacy from @makkomaster, @rolandr’s Ark system for backups and long-term data archival, more news on @zettawatt’s Colony (search) and @oetyng’s Rryn (backup), @saykor’s Queeni (AI assistant), @bochaco’s Formicaio (node launcher), @happybeing’s dweb (website publisher) and many more – apologies for not being able to namecheck everything that’s going on. 
Plus @loziniak opened a discussion on a common design patterns repository for high level datatypes.
We’re working hard on tightening up our documentation. There is a lot of it and we’re well aware of gaps and some things being out of date. Rusty is putting together some info on currency transfers in general and @bux shared a source of truth for NFT claims for shareholders.
There have been a fair few bug fixes this round including with nodes apparently not starting and one to correctly obtain the EVM network for wallet balance.
Some of these have made it into the latest hotfix release. For Launchpad users, to upgrade to version 0.4.0 of antnode, you must upgrade to 0.5.9 of the launchpad.
Impossible Futures latest
Voting has now ended. Our 12 finalists will be announced at 11:00 GMT, on Monday 19 May.
With the finalists verified, informed, and locked in, we’ll be on to the next phase: Backing will commence at 13:00 GMT, on Monday 19 May. We know that many of you will be keen to know what is coming, what’s involved, and how it all works, so we’re preparing a comprehensive guide! Here’s a sneak peak of those docs to keep you in the loop: Impossible Futures: A Guide to Backing This is still draft at the moment but we believe it important to be able to get eyes on, and understand the next stage.
Once again a massive pat on the back to everyone who has got stuck in and voted, championed the impossible, and to all our builders—finalist or not—for making this happen. There are some incredible and inspirational uses of Autonomi unfolding and assembling in front of us. And nothing stops that, on the unstoppable Network we all own!
Don’t miss @bux’s post on the opportunities to nominate judges.
General progress
@rusty.spork has been putting together some guides about NFTs, currency conversions and transfers, including how to send Eth on Arbitrum from Coinbase.
@anselme dug into a security vulnerability spotted by @bzee and managed to create a fix that is also backwards compatible. He also integrated don't-repay-for-failed-uploads CLI side in light-client-networking. What is LCN? Well, our networking stack is large and complex (12k lines of code) and is shared between the node and the client. Light-client-networking is an attempt to break away from this heavy piece of code and replace it with a simple 1k-lines-of-code alternative that the client can use. It’s a huge code simplification client side that should lead to significant performance improvements, but it’s still a work in progress.
@qi_ma looked at potential network security issues and worked on splitting payment and upload flows on the client light networking branch. He also joined the investigation into the Launchpad issue.
@vphongph has been making good progress with Python bindings with 25 classes and 221 methods now added. 
@bzee has been polishing the self-encryption node.js bindings and working on documentation.
@chriso and Ermine led the investigation into why Launchpad users were reporting nodes not starting. If you are on version 0.5.7, you can’t upgrade within the Launchpad to antnode 0.4.0. This is because of a renaming of --home-network to --relay. The service definition does not get updated and so 0.4.0 will not start because it no longer supports a --home-network argument. This is true whether you are using uPnP or not.
So, if you want to upgrade to antnode 0.4.0, you must upgrade to Launchpad 0.5.8. If you start with a completely fresh setup on either 0.5.7 or 0.5.8, when you initially try to add nodes, it seems like it’s doing nothing but NAT detection is running in the background and taking several minutes. There is no indication of that in the UI. Once the NAT detection completes, the nodes start OK, using uPnP or not. We are working on an improved UI for this.
@jimcollinson has been following up on questions about NFTs and currency conversions and is working on some Q&A documentation there. The shareholder website has been updated to include a guide for individuals to fund transaction fees, and we also have info on switching Maid to Ant.
Lajos tested the Phase 2 contract on Sepolia and discussed some issues with the auditors.
And @mick.vandijke worked on fixing connection issues with (mobile) wallets on the IF frontend (and added auto-reconnect)
@roland worked on the deployment of the reachability check PRs and documented the various connection errors that we see. Most of these errors now have an explanation and seem logical. The reachability work consists of adding a delay to dialback and fetching connection status, which eliminates the errors but requires a new confirmation process; then adding reachability check support to node, node manager and deployer. Roland has deployed a testnet and found that symmetric NAT private nodes are able to detect that they are not reachable and use the --relay flag automatically. The other nodes are detected as reachable.
Finally @shu had been working with @roland on remaining edge cases & errors around his reachability check PRs. He also created an ELK dashboard specifically to filter out NAT hairpinning noise.
for both speed and quality.
