RSKIPs
Network Upgrade: Vetiver
| RSKIP | 553 |
|---|---|
| Title | Network Upgrade: Vetiver |
| Created | 23-MAR-2026 |
| Author | AE |
| Purpose | Usa, Sca, Sec |
| Layer | Core |
| Complexity | 2 |
| Status | Draft |
Abstract
This RSKIP outlines the consensus changes proposed for inclusion in Rootstockâs upcoming network upgrade, codenamed Vetiver. Some of the proposed RSKIPs, if ultimately approved, are intended to activate initially only on the Rootstock Testnet as part of an incremental rollout strategy. This approach allows them to be validated in a less critical environment before deployment on Mainnet. These RSKIPs are marked below as (Testnet only). Additionally, some RSKIPs that were already activated on Testnet in previous network upgrades are now being proposed for activation on Mainnet. These RSKIPs are marked below as (Mainnet only).
Specification
- Codename: Vetiver
- Block activations for Vetiver 9.0.0:
- Rootstock Mainnet block: TBD
- Rootstock Testnet block: TBD
Included RSKIPs
No included RSKIPs
Accepted RSKIPs
No accepted RSKIPs
Rejected RSKIPs
No rejected RSKIPs
Proposed RSKIPs
- RSKIP-535: (Testnet-only) Add the baseEvent field to the Block header extension
- RSKIP-536: (Mainnet-only) Additional methods for the BlockHeader precompiled contract
- RSKIP-540: Bridge method
getEstimatedFeesForNextPegOutEventimprovements and new parameterized method - RSKIP-544: Reject new contract code starting with the
0xEFbyte - RSKIP-551: Deprecate RSKIP-459
- RSKIP-552: Improve Blake2F input validation
Timeline
- MAR-23-26: RSKIP created with an initial list of proposed RSKIPs
References
Copyright
Copyright and related rights waived via CC0.