Hi All,
This is my April progress report.
What was done:
- The first public Satellite node was launched at https://ss-alpha.online. The Satellite code was pushed to a beta release, including the setup docs (Release v0.1.0-beta · mike76-dev/sia-satellite · GitHub).
- The web UI repository was forked (GitHub - mike76-dev/sia-web at satellite) to enable two new features: the Satellite configuration page, and the satellite indicator on the Contracts page (see the screenshots):
- On the client side, most of the Satellite code was moved to an external package (GitHub - mike76-dev/renterd-satellite: Satellite package for use within Sia renting software).
- The calls of the contract formation and renewal RPCs involving a Satellite were integrated into the
renterdautopilot loop: whenever a Satellite is enabled by the user, this code is invoked instead of the native code. - An alpha version of the client (Release v0.2.0-alpha · mike76-dev/renterd · GitHub) was released to enable the Satellite testing for the public. The release was announced on the Sia Discord (Discord) and on Reddit (Reddit - Dive into anything).
- As per @Nate’s suggestion, the Renter-Satellite Protocol (RSP) was modified to enable trustless contract formations and renewals. This new version of the protocol (RSP2) is now being tested on my test Satellite.
What comes next:
- In addition to fixing any bugs revealed during the testing of the Satellite, I need to discuss with the Sia team about how to integrate the Satellite with
renterd. Unlike L2 services, which could be run as standalone modules, Sia Satellite is more like L1.5, which makes it difficult to separate the Satellite code fromrenterdcompletely. - A follow-up proposal (Grant Proposal: Sia Satellite II) with an extended scope of the Satellite features was submitted.