In our Spaces session on Wednesday we tackled the Web3 sovereignty illusion, why AWS still controls “decentralised” apps (aka how do we de-Jeff the web?), the myths of IPFS, and why perpetual data is a necessity for digital sovereignty. Thanks @rrieve for stepping up to share your wisdom. You can catch the session here (no X account required).
In ANT news, our supply got verified on CMC so we’ve moved up over 2000 spaces in rankings, reclaiming our rightful spot at #1070. 
Pitching in on Marketing
On marketing, check out the press release for REGRU, which is not only great for spotlighting a worthy project, but aids in the ongoing work to highlight the significance of the Network for a broad range of industries.
You can help out in the marketing efforts by re-posting, commenting, and sharing these stories. This thread on REGRU is a great place to start:
Some community highlights:
@zettawatt set up an Autonomi Developer Council call to chat about the network and other matters.
@bochaco updated Formicaio (Docker based node launcher) to introduce the --data-dir-path CLI argument to set the path for storing all node data and tracking information for nodes.
@happybeing updated dweb enabling deterministic port allocation which ensures the same app will always open on the same port and so can use local storage for session related data, along with other improvements.
@oetyng gave an update on progress with Rryn (data back up) including a readme and some explanations of processes and thoughts.
@riddim gave us some idea of plans and progress on the Friends chat app, there were advances in @loziniak’s Community Token proposal, and there was an update from @safemedia about the Autonomi Browser extension.
General progress
@anselme reviewed the light client network (LCN) [also known internally as CLN 
] code and addressed a few issues. Tests on LCN confirm positive results, which should improve put quorum errors. He also submitted an improved fix for put quorum errors, and worked on the planned networking refactor to incorporate LCN.
@qi_ma has also been looking at the quorum error handling in the LCN branch, along with @anselme and @mick.vandijke. He raised a PR with the libp2p team concerning anomalies with error handling. He also raised a PR to remove unused client-only ant_networking methods, and an internal one for simplifying the ant_networking config API.
@chriso has been looking at comparisons and testing related to the LCN branch. He also addressed an issue where Windows Defender is flagging safe.exe and safenode.exe as reported by the community, and raised a PR to support the --upload-interval argument in deploy and client deploy commands.
Ermine tested the rpc-removal PR (we’re replacing RPC with metrics services) with Launchpad and antctl to ensure stability. He concluded that a new antnode upgrade mechanism is needed to preserve data without resetting the launchpad nodes and is working on that now.
On transactions, Lajos started working on the paymaster smart contract for gasless ANT payments.
@mick.vandijke noticed slower download speeds using LCN compared to the stable branch and put in a fix which has meant LCN is actually a bit faster now. He also raised a PR for better file upload and listing output, updated the “spawn a single node” example and identified a new issue with the Autonomi client.
Meanwhile @roland investigated high disk reads from our comparison results and continued integrating the new metrics into the node manager. He raised a PR (#3000 - it seems like yesterday that we crossed the 1000 barrier! Shows how fast we are moving) to organise PUT validation errors into a separate enum and expose metrics for nodes. He also rebased the FIFO bootstrap cache to main and integrated metrics from the reachability check PR he’s been working on for the past few weeks.
@shu documented instructions for traffic shaping and random packet loss on internal NAT gateway droplets. He also worked on integrating metrics for reachability status, PUT errors and metrics published on the website.
Finally, @vphongph implemented a local node spawner in unit tests to enable parallel test execution, reducing run time compared with serial tests. He’s working on the implementation now.
from 