Short(ish) one this week as @chriso stole the update’s thunder by getting the latest Autonomi release out of the door ahead of time. Also there’s a fair few folks on holiday, getting married, going to the dentist and so forth.
So the main, if second-hand, news is we have an update. The main changes are integrating the latest version of libp2p, simplifying the bootstrap cache to be a FIFO, changes to logging and using libp2p request-response (req/resp) direct messaging for clients to send records to nodes, as explained last time.
Please update your nodes if you haven’t already.
Thanks for the feedback so far. We hope you’re seen an improvement in upload and download speeds and reliability. On very large files, streaming is not yet operational so you may run out of memory downloading. We’re considering a hotfix for this. On additional chunks being stored, this can happen. Not all records will be relevant records. If the situation doesn’t stabilise we’ll look again.
Update on the latest release
Following this week’s significant network update, we’re pleased to report the rollout is progressing well, with approximately 90% of nodes now upgraded.
We appreciate your timely and detailed feedback throughout this process. To be clear about the issues some community members are experiencing:
- Downloads: Some chunks are randomly failing to be retrieved (importantly, they’re not lost—they just can’t be obtained at the specific moment they’re requested)
- Uploads: Quotes cannot be obtained for some chunks due to client connection issues
- Emissions: Some upgraded nodes are not being quoted in the rewards system
For the download and upload issues, it’s worth noting that we didn’t observe these problems during our release candidate testing phase. This suggests the issues may be related to the natural settling period as the update propagates across the network and nodes adjust to the new version. We’re continuing to monitor these patterns as the upgrade beds in.
The emissions issue is still under active investigation. While our monitoring shows the service appears to be operating as expected, we recognise something isn’t working as it should for affected nodes. We’re working to identify the root cause and will update you as we learn more.
These temporary disruptions are expected as the network stabilises and the upgrade takes full effect. However, we recognise we can improve how these errors are presented to users. Enhancing our error messaging, UX error states, and logging has been a major focus of our development discussions this week, and we’re committed to making these interactions clearer and more informative.
Impossible Futures Program Update: Mainnet Migration
Calling all finalists!
We know today was your deadline to get your apps live on mainnet, and we want to address how this week’s network update affects you.The good news: With the network now 90% upgraded, things are settling down nicely. While migration should in many cases be as straightforward as changing the network ID, with the recent release just bedding in, we want to give a little grace on the deadline.Updated timeline:
- New deadline: Please have your apps deployed to mainnet by July 21st
- Judging prep period: July 22nd - 29th
This gives you a few extra days to ensure everything is running smoothly on mainnet while still qualifying for prize consideration.
What’s next: We’ll be releasing guidance on Tuesday with tips on how to best prepare your applications for the judging process. And you’ll have the week of the 22nd onward to get this all together. We’ll include some guidance what our judges will be looking for, and how best to present it.
If you have any questions or run into issues during migration, please don’t hesitate to reach out to the team.
Thank you for your patience, hard work, and relentless innovation… Here’s to the impossible!
Community moves
@riddim updated the readme to Friends messenger with methods and optimisations that should help other devs who want to create Web Apps on Autonomi.
@ambled released an image of Autonomi Transation Reporter on DockerHub.
@safemedia [added](safemedia :IF: Autonomi Browser Extension - Unleash Autonomi in your Browser - #166 by safemedia) “uploading via the extension when using the local client” to the Autonomi Browser Extension “because why not?”
The hyperactive @safemedia also posted a Skunkworks thread where everyone can post their technical concepts and MVPs.
@zettawatt has been stress testing and polishing the Colony GUI this week. In doing so he hit the large file issue mentioned above. Streaming is on its way to sort this out.
And @happybeing suggested Colony as a good candidate for Internet Archive. IA is indeed in our sights but we want to have a solid offering first.
ICYMI: What comes after Big Tech?
@jimcollinson explores the post-platform economy, and what comes after Big Tech. It’s happening, fast. Are you ready?
And of course, we are fighting the beast from within the beast it always helps to watch like, sub, and all those algorithm-charming things, until we’ve finished building something better together. So please do share far and wide!
General progress
@anselme continued modifying the API to integrate streams for large file downloads . He worked on simplifying replacing in-memory encryption with the stream-based encryption.
@mick.vandijke is working on resuscitating Dave. We can rebuild him. We have the technology. We can make him better than he was.
@qi_ma refined some error handling and verification issues with request/response.
@shu has been on the internals, pulling data from Elasticsearch into Grafana for visualisation (as and when required instead of Kibana), and alerting purposes and trialling a POC for a smoke test dashboard that answers the questions required every time a testnet is deployed, i.e. visual confirmation via GUI all in one place.
Also,wrapped up end to end internal integration documentation for QEMU for ARMv7 and AARCH64 architecture emulation on DO. We hope to get internal workflows created to allow non x86_64 binaries to be automatically tested as well down the line.
@Vphongph has been digging into the Python API and reviewing the different methods and classes that may not be consistent after a user reported some issues.
And @jimcollinson’s working on an explosive new video. 
Good luck IF generation 1 the real pioneers 
