Weekly Developer Update: November, 20, 2025
As we hurtle to the end of the year, each member of the team (including the 3 non-devs) have engaged in a mission, these missions while collective and joined up, give each individual 3 clear objectives to achieve prior to Christmas, this links directly into the accessibility focused deployments mentioned previously, as well as the network stability aspects that are essential to have in place ahead of broader Autonomi engagement (inc data uploads). Each dev objective feeds into one or more of the following end of year development goals:
-
Improve network stability by reducing churn and make significant gains towards data permanence through the identification and ‘casting out’ of bad nodes.
-
Move toward improving accessibility, for large data uploaders, supporting the utility of ANT and network scale through the release of an Indelible demo.
-
Remove some of the friction associated with blockchain payments through the ‘best optimised’ deployment of Paymaster in both Dave and Indelible.
-
Significantly reduce the cost of using the network (data uploading), by minimising the fees associated with EVM blockchain through the deployment of Merkle Tree payments.
-
Optimise the way the team track, test, document and deploy, through role crossover, actionable insights, PR quality and streamlining of code.
Core Network (Performance Improvement)
-
The data retrieval process has now been completed, it was revealed that legacy code (also connected to the previously mentioned July release, which we have no identified had two bugs - the first of which was resolved in the last release). This secondary bug, was causing a reduced amount of replication throughout the network - replication is not just an essential part of the network, it directly impacts and mitigates issues connected to churn.
-
In regards to data loss, due to the nature (inc privacy level) of the network it is not possible to provide an accurate/useful percent. Also, it was observed that additional elements such as upload size and time of upload played a role in retrieval success. For example, the time span in which files were uploaded had a direct impact on whether they were able to be successfully retrieved - older files (pre-July) had a much higher retrieval rate than newer files (please see comment re: bug in the July release).
-
This week we have been working on fixes for replication range (which has now been expanded) as well as a bug fix for removing the legacy upload method (referenced above), which was reducing the number of time files were being replicated.
-
We also have changes coming for max stream data size, which should improve download success rate and stability of mutable data types
-
The aspects mentioned above are due to be released next week.
Node Running (Data Hosting)
-
Automatic upgrading has moved into the ‘proof of concept’ stage, this include the upgrading mechanism as well as the staggering of upgrading to support improved stability.
-
The initial version of auto upgrade will be for nodes running on Linux (assumed to be the majority of large node operators on the network). Other operating systems will follow in time, although systems such as Windows present a different set of challenges so upgrades will need to remain manual for now.
Merkle Tree (Data Upload Payments)
-
We have now started the smart contract phase of the Merkle Tree payments, moving beyond mock components in order to begin to test the integrity and structure of the payment design
-
Large test-nets are now being created to check for issues (inc potential bottlenecks) in payments
Indelible (Organisational Tool for Data Uploads)
-
Established the Indelible test suite, to enable the team to optimise the UI and test API calls, and also to integrate both these with CI.
-
Web hooks have now been created, these will enable users to be inform as to the status of their upload.
-
Improvements have been made to wallet management, which will allow users to access/benefit from one wallet rather than having to an individual wallet for each user. It also allows for multiple wallets to be used, meaning new/different funding sources can be accessed depending on primary wallet status.
Dave (Prototype Product for Development Updates)
-
Thank you to those who shared their logs with us, with the help of these, the team has now been able to identify the issue related to files uploading successfully, but subsequently not being available for users to download. The issue was created by a failure of the replication process, this will be addressed within the next release that is scheduled for next week.
-
We are also aware that when a file upload is unsuccessful that Dave should only charge for chunks that were uploaded successfully. However, we have had reports that Dave has been charging for the entire batch again. This issue will be addressed, and resolved, next week (this maybe a UI problem but we will investigate and report back).
Mobile Bindings (Mobile Application Building)
-
The team have seen a demo of a file uploading and downloading on a mobile device! It is not the prettiest of demos/video but it is exciting that we now have a native code app that is pulling directly from the network.
-
This process is essential in order for the team to identify any problems with the bindings that have been created for android and iOS, once this process is completed the bindings will be released for developer use and documentation will also be provided.
-
Along with the demo, work has continued on data streaming, archives and vaults (file directory upload and download).
Many thanks to the team, the developers, and the community that supported the team in this hard work. 
respect!
btc is a guessing game, because im uneducated, I cant make a educated guess… 
