The Sia Foundation Roadmap

This Sia roadmap provides mid to high level insight into core Sia development. It will be updated once a quarter at minimum, and will show an outline of what we’re currently working on, why we’re working on it, and what we have in mind after that’s done.

We’re focusing on updated versions of all the core components of the Sia network - renting, hosting, and hodling. These updates will bring significant improvements to scaling, performance, and modular internal architecture to meet the needs of individuals, enterprise users, and exchange partners. Furthermore, each component will be paired with a powerful new user interface, all with the overarching goal of making core Sia software more “legible” to end users. “Legible” is the antonym of “black-box:” in a legible system, the user can easily discern why any particular decision was made, and can override those decisions as they see fit. This goal follows naturally from the Foundation’s mission of empowering users.

Project Board

The new Sia renter, replacing the current siad renter module. Drawing on what we’ve learned from siad, skyd, and us, we designed renterd from the ground up to be modular and horizontally scalable. Although the average user likely won’t notice, a renterd deployment is actually a set of interconnected services. As such, it can distribute workloads in parallel across multiple machines, and can be configured to store its metadata in any SQL backend. This flexibilty makes renterd easier to integrate with other Sia ecosystem software, such as Sia Satellite and S5, and addresses the scalability barriers that have historically hampered enterprise solutions.

April 2024

June 2024

  • Add support for RHP4
  • Improve upload parallelism

The new Sia host, replacing the current siad host module. The host module has been chronically neglected for years, and suffers from poor upload performance, data integrity issues, and a general lack of user-friendliness. hostd is our greenfield reimagining of the Sia hosting experience, bringing a sorely-needed refresh to our host community. Aside from addressing performance bottlenecks, hostd also offers superior metrics and monitoring tools, which will allow users to make informed decisions about storage allocations, contract parameters, pricing, and quality of service.

April 2024

June 2024

  • Automate data integrity checks
  • Add support for RHP4

September 2024

  • Support Postgres as an alternative to SQLite
  • Support additional volume types to optimize performance for distributed file systems

The new Sia wallet, replacing the current siad wallet module. walletd aims to be the go-to option for exchanges, miners, or the average hodler who needs a secure place to store their SC. Accordingly, it supports both hot and cold setups, including multi-sig schemes and hardware wallet integration. And like renterd and hostd, walletd comes packaged with a sleek, yet powerful UI, which can be securely accessed from any device.

Note: you don’t need walletd to be a renter or a host; renterd and hostd include their own built-in hot wallets.

January 2024

  • Support SQLite - Done

May 2024

  • Add “Indexer” mode enabling easier integration for exchanges - In Progress
  • Beta Release - In Progress

The new Sia explorer, replacing and going far beyond the current siad explorer capabilities. explored will serve as both a standalone blockchain explorer with a web interface, and as a library providing powerful indexing and searching capabilities to third-party explorers (e.g. SiaStats) and “lite-client” systems like narwal. explored will be developed and launched alongside the Utreexo overhaul, making it one of the world’s first Utreexo-native block explorers.

June 2024

  • Beta release

“Utreexo” is an umbrella term that refers to an upcoming radical overhaul of Sia’s consensus code. The primary change is the transition from a large, unwieldy database of UTXOs to a compact cryptographic accumulator, bringing myriad benefits to performance, scalability, and functionality. This is a big deal: it requires changing the block and transaction formats, which have been untouched since Sia’s mainnet launch back in 2014. As such, we are taking this opportunity to clean up a few other warts in Sia’s consensus code, giving the project a solid foundation for many years to come. For a more technical dive on how Utreexo works, check out Luke’s blog post here and MIT Bitcoin talk here.

May 2024

  • Upgrade Zen testnet

RHP4, short for renter-host protocol 4, is the next iteration of the protocol hosts and renters use to communicate. Our goal for RHP4 is to increase the parallelism of data uploads, reduce protocol overhead, and improve download performance. A new protocol is required to enable some exciting new features to be available after the Utreexo hardfork, such as early contract termination, capacity reservation, and contract renewal fund rollover. RHP4 will also enable storage consumers to download and upload data directly in the browser without installing additional software.

February 2024

  • Finalize spec
  • Implement RHP4 client in coreutils

April 2024

  • Test RHP4 on Anagami

May 2024

  • Release experimental SiaJS SDK
  • Test RHP4 on Zen

fsd is our experimental implementation of an IPFS node with specific optimizations for storing and retrieving data from the Sia network. We plan to open source it in the near future once it has stabilized more and we’ve verified that pinned content is discoverable and accessible by other IPFS nodes.

June 2024

  • Release alpha
Document version date: Apr 22, 2024
May 3, 2024
  • Adds a hostd-js library.
import { Hostd } from '@siafoundation/hostd-js'

export async function example() {
  const hostd = Hostd({
    api: 'http://localhost:9980/api',
    password: 'password1337',
  })
  const state = await hostd.stateHost()
  const volumes = await hostd.volumes()
  console.log(state.data, volumes.data)
}
May 3, 2024

It turns out that Chris 's hunch was right and that we are not tracking sector upload estimates at times we should be, even worse we currently don't track anything at times we should be penalising the host for being slow. I added explicit logging for when we penalise a host for being (super) slow, so going to follow this up on my node to be sure.

Overall I thought it was a little tricky to come up with a good way to fix it and to write a solid unit and/or integration test for it. If we really want to check the exact errors we would need an integration test but that would involve a level of orchestration we are currently not capable of doing from an integration test. The unit test I came up with is not exactly what I was hoping for but it does cover all branches.

Closes https://github.com/SiaFoundation/renterd/issues/1167

May 2, 2024

This implements soft delete for spent elements, sidestepping the issue of reverts clobbering the chain index. Spent elements will be pruned 144 blocks after their spend height. This also reverts the removal of the chain_indices table to use the foreign key as a bug sanity check.

May 2, 2024

This PR passes an appliedIndex to revertChainUpdate which is used whenever we re-add elements. Before, we were re-adding those elements using the revertIndex which is definitely incorrect because we go and delete those in revertIndex. I renamed revertIndex to removeEvents and changed it to only remove events because if a revert is processed correctly the elements should already have been removed.

The idea of an appliedIndex as the counterpart for every revertIndex feels a bit naive maybe but I decided to propose it nonetheless because I don't see what's wrong with it either. If we can't do that I feel the only thing we're left with is soft deletion but that comes with its own issues, mostly complexity trade-off.

May 2, 2024

Fixes #85

May 1, 2024
  • Fixes a panic when calling [GET|PUT] /settings/pinned with explorer data disabled
  • Adds explorer info to the [GET] /state/host endpoint
View full activity feed →