Our primary development goal for 2024 is to launch the “v2” hardfork. “v2” is our codename for a massive overhaul to Sia’s consensus mechanisms. It will modernize Sia’s core consensus code and provide a number of usability, performance, and quality-of-life improvements to the network.
After the hardfork, we will be working on reducing onboarding friction for users, developers, and enterprises including:
- Light worker agents for
renterd to increase horizontal scalability for enterprises, but also enable users to download and upload objects from all of their devices.
- Simple SDKs for developers to interact with the Sia network directly.
- A mobile and web app that lets all users take advantage of the cost savings, privacy, accessibility, and performance advantages of decentralized storage without the hassle of buying crypto or managing storage contracts.
“v2” 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.
- UTreexo
- Near instant syncing
- Reduced blockchain size
- Improved UTXO spend policies
- “Composable” unlock conditions
- HTLC support for atomic swaps
- Storage contract changes
- Early contract termination
- Collateral efficient renewals
August 2024
- Reset Anagami testnet - Complete
November 2024
December 2024
- Release v2.0 ready software
- Announce activation dates
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.
- Improved upload and download performance
- Concurrent uploads
- Decentralized uploads and downloads in a browser without downloading software
October 2024
- Implement RHP4 client in
coreutils - In Progress
December 2024
- Release Sia SDK beta - In Progress
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.
August 2024
- Price pinning for gouging settings - Complete
October 2024
- Add support for RHP4 - In Progress
November 2024
- Release hardfork ready v2.0.0 alpha
December 2024
- Release hardfork ready v2.0.0
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.
October 2024
- Add support for RHP4 - In Progress
- Release hardfork ready v2.0.0 alpha
December 2024
- Release hardfork ready v2.0.0
The new Sia wallet, replacing the current siad wallet module. walletd aims to be the go-to option for average holders, lite wallet developers, exchanges and miners that need a secure place to store their SC. Accordingly, it supports both hot and cold setups, including multi-sig schemes and hardware wallet integration. Like renterd and hostd, walletd comes packaged with a sleek, yet powerful UI, which can be securely accessed from any device.
Note: you do not need walletd to be a renter or a host; renterd and hostd include their own built-in hot wallets.
September 2024
- Improve support for exchanges - Complete
December 2024
- Release hardfork ready v1.0.0
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.
October 2024
December 2024
- Release hardfork ready v1.0.0
Document version date: Oct 24, 2024Nov 20, 2024
- Files and directories can now be selected and moved in bulk to a destination folder via drag and drop or the multi-select actions menu. This works even when selecting files (and entire directories) from across multiple different origin directories.
Nov 20, 2024
- Add settings gouging, pinned, s3, and upload patch APIs.
Nov 20, 2024This PR disallows partially updating settings in the bus.
Nov 20, 2024This PR adds. v2 host announcements via the host_addresses table. Up to 5 addresses per protocol per announcement will be stored for each host.
The IP validation remains similar to what it was before. All addresses of a host are resolved and then we make sure there are only up to 2 addresses associated with a host.
This PR also gets rid of the persisted resolved addresses instead of doing the same for v2 addresses. In exchange, we don't consider host's for which we fail to resolve addresses as "redundant" anymore assuming that every host that fails to resolve either does so because it's our own fault, or because it is offline/misconfigured which means the host scans will eventually treat it as offline.
NOTE: I verified that v2 hosts are picked up and added to the database for the v2 tests but the tests won't pass before all parts of the renter are migrated to support v2. The f/u PR continues the work by implementing scanning.
Closes https://github.com/SiaFoundation/renterd/issues/1668
Nov 20, 2024Bumps the all-dependencies group with 1 update in the / directory: go.sia.tech/web/renterd.
Updates go.sia.tech/web/renterd from 0.66.0 to 0.67.0
Release notes
Sourced from go.sia.tech/web/renterd's releases.
Minor Changes
- fe888991: Invalid and not found routes now redirect to the home page.
Commits
5b4aafd chore: release packagesaeb3615 chore: upgrade clusterfe88899 fix(apps): add 404 page and redirect206fe8d test(explorer): add e2e tests for all routesd6e4c8a fix(explorer): strip addr from input and output hrefs6172484 fix(explorer): fix network request calls when navigating to block by heightb70880f chore: update changeset with missing closes0322114 fix(walletd): generate seed address no prefixd794e60 refactor: standardize syncer peers response datad2a2083 chore: export renterd/v0.66.0 hostd/v0.50.0 walletd/v0.23.2- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot merge will merge this PR after your CI passes on it@dependabot squash and merge will squash and merge this PR after your CI passes on it@dependabot cancel merge will cancel a previously requested merge and block automerging@dependabot reopen will reopen this PR if it is closed@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
Nov 20, 2024Bumps the all-dependencies group with 3 updates in the / directory: go.sia.tech/core, go.sia.tech/coreutils and go.sia.tech/web/renterd.
Updates go.sia.tech/core from 0.6.1 to 0.6.2
Commits
0b6d8d1 Merge pull request #231 from SiaFoundation/nate/add-txn-idf5479af types: add recursion comment24a1ed6 types: address comments8941fc1 types: add ID field to transaction JSON7b530e0 build(deps): bump the all-dependencies group with 2 updatesa872ea8 Merge pull request #230 from SiaFoundation/nate/json-consistencyabd95cc ChainIndexElement camelCase9450b1a FileContract.UnlockHash Hash256 -> Address2a3a1bf Merge pull request #227 from SiaFoundation/nate/fix-finalization-encodingde1461f types: fix finalization json encoding- See full diff in compare view
Updates go.sia.tech/coreutils from 0.6.0 to 0.7.0
Commits
6172c9c Merge pull request #119 from SiaFoundation/nate/zen-heightsbf1f218 push zen v2 activation height9ebf043 Merge pull request #118 from SiaFoundation/nate/upgrade-core700b8bb update core to v0.6.2eb25872 build(deps): bump golang.org/x/crypto from 0.28.0 to 0.29.0- See full diff in compare view
Updates go.sia.tech/web/renterd from 0.66.0 to 0.67.0
Release notes
Sourced from go.sia.tech/web/renterd's releases.
Minor Changes
- fe888991: Invalid and not found routes now redirect to the home page.
Commits
5b4aafd chore: release packagesaeb3615 chore: upgrade clusterfe88899 fix(apps): add 404 page and redirect206fe8d test(explorer): add e2e tests for all routesd6e4c8a fix(explorer): strip addr from input and output hrefs6172484 fix(explorer): fix network request calls when navigating to block by heightb70880f chore: update changeset with missing closes0322114 fix(walletd): generate seed address no prefixd794e60 refactor: standardize syncer peers response datad2a2083 chore: export renterd/v0.66.0 hostd/v0.50.0 walletd/v0.23.2- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot merge will merge this PR after your CI passes on it@dependabot squash and merge will squash and merge this PR after your CI passes on it@dependabot cancel merge will cancel a previously requested merge and block automerging@dependabot reopen will reopen this PR if it is closed@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
