Big news this week is our data partnership with FYEO, creator of KryptPass. At this stage they are going to help with testing by uploading data. Nothing sensitive right now, obviously, but they have a lot of threat intelligence data that they want to store on Autonomi, and really it’s an excellent fit.
For any of you who haven’t yet, make sure you’ve updated to node v0.112.5 with the latest launchpad. “Dave” is depending on you. Anyone on Windows who finds Launchpad is being blocked should see this post.
Also check out the latest Beta testing leaderboards. Remember, all testers will be rewarded come the Token Generation Event (TGE), and if you haven’t spun up a node or two as yet, there’s still plenty of time.
Finally, @jimcollinson, @gill_mclaughlin and @bzee are in Lisbon at the WebSummit this week, putting Autonomi out there before a global audience and meeting with like-minded folks. Here is a short update from @jimcollinson.
General progress
With some of the team attending the WebSummit, the rest of the devs have continued testing variables, bringing the Vault web app (aka Dave) to fruition and optimising resource usage.
Before he left for Lisbon @bzee raised a PR to allow access to the history (DAG) of the register data type.
Once again @mick.vandijke has been heads down in the WASM Vault web application, which the team have been user testing this week, working through workflows and retry strategies.
@rusty.spork has been testing the Vault web app (OK, Dave), starting a new trial for home nodes, as well as carrying out his usual Discord activity.
Ermine debugged some CI issues with Vault sync, and started writing performance tests to get the metrics of each function used by the Vault.
@chriso and @shu continue to work on comparing and contrasting different testnets with different variables, to check for CPU usage, memory, stability under load etc. It’s from this that we come up with release candidates and ultimately releases each week. There are still some lingering issues around CPU in some cases, and full WASM integration is a work in progress.
@dirvine is refining his python modules for node, client and self-encryption thanks for your help @riddim, @happybeing and other testers. We are waiting for the folks to get back from Lisbon to make some API changes now.
Meanwhile, on the Launchpad, @mazzi worked on preventing inconsistent states when starting/stopping/removing nodes. He also a fixed an RPC server bug which was causing problems for users, and made an error message display when Launchpad is not whitelisted on Windows devices.
@qi_ma has been writing up documentation on our measures to make the network resistant to attacks and more smoothly updatable.
And @roland continues to study connections, how we log them, how Websockets are working, and how we prevent or better explain some of the error messages we see in the logs.
@ “Dave”
