RootStock has released the mandatory Vetiver 9.0.0 network upgrade, requiring all node operators to update to remain compatible with the network and enable future features like the Union Bridge and Account Abstraction.
> impact
["RootStock has shipped the Vetiver 9.0.0 network upgrade, a mandatory update for all Mainnet and Testnet node operators. This release introduces consensus-breaking changes, making it critical for the entire network to upgrade in unison. The activation is scheduled for block 8,804,200 on Mainnet and block 7,604,200 on Testnet. Any node that is not updated by these block heights will fall out of sync with the canonical chain.","The Vetiver upgrade is foundational for RootStock's future, introducing preparatory work for two major upcoming features: the Union Bridge and Account Abstraction. By laying the groundwork now, the network ensures a smoother transition and integration for these complex functionalities. Additionally, this release refines the peg-out cost estimation process for improved efficiency and updates the default behavior of several JSON-RPC API methods to align with modern standards and developer expectations.","For node operators, the immediate impact is the requirement to update their software to version 9.0.0 to maintain network compatibility. Failure to do so will result in the node being unable to process new blocks and transactions post-fork. For developers, the JSON-RPC changes may require adjustments to application backends, while the groundwork for Account Abstraction and the Union Bridge signals a clear roadmap for building more sophisticated and user-friendly dApps on RootStock in the near future."]
> Try this now
try this
# This is a mandatory consensus upgrade for all node operators.
# The following steps outline a typical upgrade process for an RSK node.
# Always consult the official release notes and backup your configuration.
# 1. Stop the current RSK node service to prevent data corruption.
# Use the appropriate command for your system (e.g., systemd, docker).
sudo systemctl stop rsknode
# 2. Download the new Vetiver 9.0.0 client from the official GitHub releases.
# Ensure you download the correct binary for your environment.
wget https://github.com/rsksmart/rskj/releases/download/VETIVER-9.0.0/rskj-core-9.0.0-VETIVER-all.jar
# 3. (Optional but recommended) Backup your existing node binary.
mv /usr/share/rsk/rsk.jar /usr/share/rsk/rsk.jar.bak
# 4. Replace the old binary with the new Vetiver 9.0.0 version.
mv rskj-core-9.0.0-VETIVER-all.jar /usr/share/rsk/rsk.jar
# 5. Restart the RSK node service.
sudo systemctl start rsknode
# 6. Verify the upgrade by checking the client version via RPC.
# The response should indicate the new Vetiver version.
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":1}' http://localhost:4444
# Expected response snippet: "result":"RskJ/VETIVER/9.0.0/..."
# 7. Monitor your node logs to ensure it syncs correctly after the fork block.
tail -f /var/log/rsk/rsk.log