We are now on the final stretch of the end of year missions, as such there are three important aspects that are likely worth mentioning ahead of diving into this week’s update:
-
There will be a release later today, following this release node operators will have until 12pm GMT on Tuesday, December 16 2025, to upgrade to this latest version. After this time current versions (becoming previous versions after the upcoming release) will no longer be eligible to receive emissions payments.
-
A Merkle element is included in today’s release (release notes to follow), while this is required ahead of its full release next week, it is not yet ready for public use (please see notes below).
-
Next week will be the final dev blog and company update of the year - as such the format will be slightly different and the content more expansive. There will also be an emphasis on what’s coming in 2026 Q1, as well as the status, impact and pending plans for recent work and efforts.
Core Network (Performance Improvement)
-
The team has been working on enhancing and improving ‘nodes from code’ - this will enable the team to spin up large testnets instantaneously, improving the rigour and velocity for testing and change validation ahead of any network updates and/or releases.
-
logs are going wild! The team has started evaluating how logging is done and reducing the volume of logs generated by nodes and clients. For context there is currently a huge amount of application logging happening, most of which has been deemed as unnecessary (even for developers trying to troubleshoot and debug), this will reduce the amount of resources required from peoples computers, the volume of logging files that are being generated by every node will also be reduced, meaning the team will be able to use information more readily/easily, without having to search through an excessive amount of files.
Node Running (Data Hosting)
-
Today we are releasing automatic node upgrades for Linux users, this same update will work for Mac users, although we have noticed some issues with the ‘trigger time’ of updates being inline with what is expected. This is to say, that while the updates themselves happen without issue when they begin, there can be a delay in the update being made due to the triggered time of start.
-
Changes have been made to both Launchpad and
antctlso that versions of nodes will indicate the version that they are running after an update. -
For automatic upgrades, the team have been testing in two major scenarios. The first is ‘binary-per-service’, the second is ‘symlinked binary’. These are both continuing to function as expected (i.e. working the same), after an update has been applied.
Merkle Tree (Data Upload Payments)
-
Node side and client are both being deployed today, although the client side is experimental at this time and therefore not being made readily available, until next week, when tests on MainNet have been completed/are conclusive.
-
The reason that both are being released (despite client not yet being ready/made widely available) is because the nodes need to be able to handle Merkle payment requests before the client can start making them - in other words, the upgrade of nodes needs to happen ahead of time, in order for uploads post the Merkle client being released, to be successful. This staggered process also enables the team to observe the client side deployment of Merkle to ensure its stability and success, ahead of it being deployed for use next week.
-
elated to diligence, to note, Merkle has now been tested on a network of 10,000 nodes to help ensure performance is observed as expected.
Indelible (Organisational Tool for Data Uploads)
-
This week we would like to share a video of our progress on Indelible. This demo showcases a user being able to upload a file to their Indelible server (through the web UI) and have it processing asynchronously with web hooks alerting the user to upload success.
Dave (Prototype Product for Development Updates)
- A new version of Dave has now been released (0.4.2) - this includes some bug fixes related to payments and paymaster specifically. You can find the link for GitHub HERE
Mobile Bindings (Mobile Application Building)
- The first iteration of mobile bindings for Android have been released on JitPack, while they’re in a very early state they are something that developers can use today if they would like. We will continue to update and improve the usability from here. In terms of developer efforts, the next step is to get iOS bindings working and also improve documentation, examples and tutorials across the board.
. Very very nice.
