Happy to report that the bug fix implemented last week seems to be working, and the vast majority of home nodes (nodes behind NAT routers) are now able to connect.
The latest release candidate rc-2024.09.2.2 is now available for any intrepid explorers who want to check it out. Improvements include a first iteration of the client API, performance increases in the auditor, and speeding up and simplifying of address simulation for testing purposes.
Most of you will also have seen the clarification of the reward structure for Beta testing. Thereāll be more info about the next phase of testing shortly.
Thanks to @happybeing for the bug reports on quinn, on chunks being uploaded from the previous network and uploading the same files from different devices apparently resulting in paying for some chunks more than once. (And welcome back )
Thanks also to @loziniak for the assessment of the API. Hopefully, once the EVM wallet has been integrated, it will make more sense. At that stage, we should have something devs can work with.
General progress
We have a crack team driving investigations into the effect of the choice of chunk size and node size on various aspects of the network, including: upload and download speeds; memory, bandwidth and CPU usage; and saturation of connections at startup. The aim is to find an optimal balance between the range of devices able to run nodes and Network performance.
@rusty.spork has been delving into a few issues Windows users are still having with WinSW. Zero display of RAM usage issues and unresponsive Ctrl-x and Ctrl-s controls may be solved by shutting down Launchpad, navigating to C:\Users\[username]\AppData\Roaming\safe\launchpad\
, deleting WinSW and restarting Launchpad. Worth a try anyway if you are having problems.
@mazzi opened a PR to improve the flexibility of the layout on the Launchpad status screen and dialled in some options, so users do not need to set a Discord username in order to connect to the Beta network.
Meanwhile, @bzee has been working on various aspects of the API, which is now just waiting on a few updates elsewhere. Heās been working on fixing a bug in how registers are fetched and updated and improving parts related to in-memory self-encryption. Together with Ermine, heās also involved in working on API resolutions with WASM.
@mick.vandijke worked on the node manager to make it compatible with the new node start commands that require some EVM (Ethereum Virtual Machine) network settings. Mick reports that API integration tests are now passing, so the whole register create/update, file upload and put workflow are now working with the EVM payments system through the client API.
@qi_ma has been helping to resolve some issues raised by the community with respect to upload anomalies along with @roland, as well as investigating the metrics that would be affected by changing chunk sizes and node sizes, and what that might mean for performance.
Working in the same neck of the woods, @anselme is engaged in a security review of EVM payments.
And last but by no means least, @chriso and @shu have been working on nightly releases. This is motivated particularly by the Launchpad, so we can get more experimental features out to users outwith the two-week release cycle, for quicker feedback. We eventually aim to have a nightly āchannelā where users can continually upgrade to pull in the latest nightly versions.