Greetings all and happy May Day! We’ve had a few questions about the voting process for Impossible Futures (IF). Rather than go through them all again we suggest you read these FAQs if you haven’t already.
A little more background. As @jimcollinson mentioned on Discord, we landed on this process to create a model that gives:
Built-in security: So mass-bot tactics are expensive and impractical, so you know results come from real voters.
A stronger turnout: Because it aims to widen appeal, adds some excitement, and gives something back for people having…
Skin in the game: Because you’re not just clicking a button; you’re investing attention, belief, and a little risk. Along with…
A stronger ecosystem: Because, a little risk filters out weak ideas early, so the overall network grows with real builders and real believers.
Another week another release. You do not need to upgrade for this particular release to receive emission rewards. This is because the node part of the release only makes very small changes related to logging. The feature of this release is in the client, for uploads.
The latest version includes address analyzer capability: ant analyze [address] . This allows the CLI to determine what is stored on the network from a datamap or public address.
On the community front, @loziniak released v0.4.0 of his alternative API to access Autonomi Network with Autonomi 0.4.4 API and cleaner network selection during connection.
Discord user rouse released PubAnt, a site that shows you how to publish your own website on Autonomi.
And @traktion offered a new minor version of AntTP with some refactoring on the streaming side and minor fixes. Traktion has also been running some performance tests on the network – with encouraging results.
Not to be outdone, @happybeing rocked up with an update to dweb which includes some client-side improvements.
General progress
@Anselme spent time fixing bugs and supporting folks on Discord. He put in some changes to make Alpha net easier to join by the CLI and fixed a bug found regarding register keys not being saved in vaults. He and @vphongph also put their heads together to think about how we might progress a DNS. Anselme also released an app to simplify file sharing on the network. Check it out!
@chriso got the latest release out and upgraded all our production nodes, before moving on to the Alpha nodes. The latest release has improvements to the client for uploads and also sorts out an issue on smaller networks we have with the peer cache being cleared out after 24 hours.
Ermine attempted to reproduce a handshake signal error in the local testnet but has so far been unable to reproduce it. He worked to spawn nodes with actual network addresses (192.* series), in parallel debugging public testnet with symmetric-private nodes to check if we can get the same handshake errors there.
Lajos worked on the IF frontend, setting it up to work with Reown/wallet connect, and migrated everything to use wagmi instead of ethers which is better for production. He created a simple frontend to test voting and the leaderboard.
@mick.vandijke wrapped up the max gas fee options PR and updated the README for the emissions service. He also worked on improving error reporting when transactions fail and adding different presets for setting max transaction gas fees.
@vphongph added more Python classes/methods and worked on a key saving bug with @anselme.
@qi_ma helped a community member with uploads, and investigated reported issues. He looked into issues around backward compatibility, and some CLI refactors that could improve user experience. He raised a PR to reduce log flushing to disk, which has caused issues with the ELK stack (monitoring), and tweaked the client config for more robust performance on slow connections.
@roland got reachability status monitoring working as intended and removed the –relay flag for the full cone private nodes in the testnet deployer. Nodes behind full cone NAT gateways are equivalent to port forwarded nodes, and hence they don’t require the --relay flag. He fixed a bug with the save_time calculation. The cache is also flushed out much more frequently now to the file system (from 24h to 3h) and is being moved towards being a FIFO. Also the max bootstrap sync interval has been increased to aid connectivity. Another PR from Roland improves visibility into connection errors.
@shu continues to work on our ELK system, which is key to close monitoring of our developments to the network.
Hopefully the gtlds are decentralized, so i register .bitcoin, but you can register 21000000.bitcoin
But seriously it’s so nice to see so much third party dev activity now taking place. And what looks like some minor bug fixes here and there.
& 
.
.