RSKIPs
Rootstock changes its consensus rules through RSKIPs — Rootstock Improvement Proposals. This page lists the 94 that have actually activated, which network each activated on, at which block, and in which client release. The other 110 are not listed here on purpose.
Proposal and activation data collected 8 Nov 2026 · how
What an RSKIP is
An RSKIP is the unit in which a change to Rootstock gets specified, argued over and adopted. The process is itself an RSKIP — RSKIP0, RSKIP Purpose and Guidelines, dated May 2018 — and it works much like Bitcoin's BIPs or Ethereum's EIPs: anyone may propose one, it carries a number for life, and it moves through a status as it is accepted or declined.
What makes the Rootstock version unusually easy to follow is that upgrades are themselves RSKIPs. Each network upgrade has a "Network Upgrade: <name>" proposal that names its codename, states its activation block on mainnet and on testnet, and lists exactly which other RSKIPs it ships. That one document is the authoritative link between "this rule changed" and "it changed at this height" — and it is what this page is built from.
A proposal's status is the quickest way to read its standing:
| Status | Meaning |
|---|---|
| Adopted | Activated on mainnet. These are consensus rules in force today. |
| Adopted (Testnet) | Activated on testnet only, usually as a staged rollout before mainnet. |
| Accepted | Approved for a future upgrade but not yet activated. |
| Draft | Proposed and under discussion. Most RSKIPs are here. |
| Deferred | Set aside; may return. |
| Rejected | Considered and declined. |
| Withdrawn | Pulled by its author. |
| Superseded | Replaced by a later proposal. |
Where to find them
All of them live in one repository:
- github.com/rsksmart/RSKIPs — the repository. Each
proposal is a markdown file at
IPs/RSKIP<number>.md. - The index table in the README — every RSKIP with its number, title, author, creation date, layer and status. This is the fastest place to look something up, and the only place that records status.
The index currently lists 232 proposals. Note that the index gives a status but not an activation height — for that you have to open the network-upgrade RSKIP that shipped it, which is the join this page does for you.
Proposals that have not activated are deliberately not listed on this page. 110 of the 232 RSKIPs in the index are Draft, Accepted, Deferred, Rejected, Withdrawn or Superseded. Their status changes as discussion moves, and a copy here would be wrong within weeks. Read them at the source, where they are current: the RSKIP repository.
Activations by release
Every release that changed consensus, in mainnet order. "Shipped" counts the proposals the release activated, not counting the upgrade's own RSKIP. Dates are the timestamp of the mainnet activation block, read from a node — not the release date, which is typically weeks earlier.
| Upgrade | Release | Upgrade RSKIP | Mainnet block | Activated | Testnet block | Shipped |
|---|---|---|---|---|---|---|
| Orchid | 0.5.0 | RSKIP99 | 729,000 | 8 Sep 2018 | 802,000 | 11 |
| Papyrus | 2.0.0 | RSKIP141 | 2,392,700 | 27 May 2020 | 863,000 | 8 |
| Iris | 3.0.0 | RSKIP187 | 3,614,800 | 19 Aug 2021 | 2,060,500 | 18 |
| Hop | 4.0.0 | RSKIP291 | 4,598,500 | 31 Aug 2022 | 3,103,000 | 6 |
| Hop patch | 4.0.1 | RSKIP358 | 4,976,300 | 17 Jan 2023 | 3,362,200 | 2 |
| Fingerroot | 5.0.0 | RSKIP388 | 5,468,000 | 13 Jul 2023 | 4,015,800 | 7 |
| Arrowhead | 6.0.0 | RSKIP414 | 6,223,700 | 3 Apr 2024 | 4,927,100 | 8 |
| Arrowhead patch | 6.3.1 | RSKIP436 | 6,549,300 | 24 Jul 2024 | — | 1 |
| Lovell | 7.0.0 | RSKIP435 | 7,338,024 | 13 Mar 2025 | 6,110,487 | 10 |
| Reed | 8.0.0 | RSKIP518 | 8,052,200 | 30 Sep 2025 | 6,835,700 | 2 |
| Vetiver | 9.0.0 | RSKIP553 | 8,804,200 | 5 May 2026 | 7,604,200 | 6 |
| Reed | 8.1.0 | RSKIP518 | — | testnet only | 7,139,600 | 5 |
Three features of that table deserve attention.
- Orchid is dated here and nowhere else. Its activation height (729,000) appears in RSKIP99 but in no rskj release note, so the history page — which reads release notes — cannot date it. Joining the two sources fills the gap.
- Patches are upgrades too. Hop 4.0.1 and Arrowhead 6.3.1 each have their own RSKIP, their own activation height and their own small payload. Arrowhead 6.3.1 is the only release in Rootstock's history to activate on mainnet only — it was the fix for the June 2024 PowPeg outage, which testnet did not have.
- Reed shipped twice. 8.0.0 activated two proposals on both networks; 8.1.0 activated five more on testnet alone. That staged pattern — prove it on testnet, then bring it to mainnet later — is why RSKIP536 appears twice in the table below, once per network.
Every activated RSKIP
Grouped by the release that activated it, newest first. Rows marked upgrade are the network-upgrade proposals themselves.
Reed 8.1.0
Activated on testnet only, at block 7,139,600. Specified by RSKIP518, released as rskj Reed 8.1.0. Shipped in two releases: 8.0.0 activated on both networks, 8.1.0 on testnet only.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 144 | Parallel Transaction Execution for Unitrie | testnet | Adopted (Testnet) | release notes |
| 351 | Miniheader - block header compression | testnet | Adopted (Testnet) | release notes |
| 502 | PowPeg and Union Bridge integration | testnet | Adopted (Testnet) | release notes |
| 529 | New storage cells in Bridge native contract for base and super events info | testnet | Adopted (Testnet) | release notes |
| 536 | Additional methods for BlockHeader precompiled contract | testnet | Adopted | release notes |
Vetiver 9.0.0
Activated on mainnet at block 8,804,200 on 5 May 2026, and on testnet at block 7,604,200. Specified by RSKIP553, released as rskj Vetiver 9.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 535 | Add the `baseEvent` field to the Block header extension | testnet | Adopted (Testnet) | RSKIP |
| 536 | Additional methods for BlockHeader precompiled contract | mainnet | Adopted | RSKIP |
| 540 | Bridge method `getEstimatedFeesForNextPegOutEvent` improvements and new parameterized method | testnet mainnet | Adopted | RSKIP |
| 544 | Reject new contract code starting with the `0xEF` byte | testnet mainnet | Adopted | RSKIP |
| 551 | Deprecate RSKIP459 | testnet mainnet | Adopted | RSKIP |
| 552 | Improve Blake2F Input Validation | testnet mainnet | Adopted | RSKIP |
| 553 | Network Upgrade: Vetiver upgrade | testnet mainnet | Adopted | RSKIP |
Reed 8.0.0
Activated on mainnet at block 8,052,200 on 30 Sep 2025, and on testnet at block 6,835,700. Specified by RSKIP518, released as rskj Reed 8.0.0. Shipped in two releases: 8.0.0 activated on both networks, 8.1.0 on testnet only.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 305 | Peg-out efficiency improvement (Segwit) | testnet mainnet | Adopted | RSKIP |
| 516 | Precompiled contracts for +/* on Secp256k1 | testnet mainnet | Adopted | RSKIP |
| 518 | Network Upgrade: Reed upgrade | testnet mainnet | Adopted | RSKIP |
Lovell 7.0.0
Activated on mainnet at block 7,338,024 on 13 Mar 2025, and on testnet at block 6,110,487. Specified by RSKIP435, released as rskj Lovell 7.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 419 | Powpeg Spendability Validation Protocol | testnet mainnet | Adopted | RSKIP |
| 427 | Express the amount value in wei for peg-out related events | testnet mainnet | Adopted | RSKIP |
| 428 | New pegout creation event including UTXO outpoint values | testnet mainnet | Adopted | RSKIP |
| 435 | Network Upgrade: Lovell upgrade | testnet mainnet | Adopted | RSKIP |
| 438 | Limit the maximum size of initcode and apply extra gas cost for every 32-byte chunk of initcode | testnet mainnet | Adopted | RSKIP |
| 445 | MCOPY instruction | testnet mainnet | Adopted | RSKIP |
| 446 | Transient storage opcodes (TLOAD/TSTORE) | testnet mainnet | Adopted | RSKIP |
| 453 | Prevent address creation on failed CREATE/CREATE2 operations | testnet mainnet | Adopted | RSKIP |
| 454 | Support bitcoin blocks with chain work up to 32 unsigned bytes | testnet mainnet | Adopted | RSKIP |
| 459 | Mark rejected peg-ins as processed | testnet mainnet | Adopted | RSKIP |
| 460 | Ignore non-standard outputs when searching for the witness commitment hash | testnet mainnet | Adopted | RSKIP |
Arrowhead 6.3.1 patch
Activated on mainnet at block 6,549,300 on 24 Jul 2024, and never on testnet. Specified by RSKIP436, released as rskj Arrowhead 6.3.1. A patch upgrade (RSKIP436) remediating the PowPeg service outage of June 2024. Mainnet only.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 434 | Bridge Bitcoin block chainwork up to 12 unsigned bytes | mainnet | Adopted | RSKIP |
| 436 | Network Upgrade (patch): Arrowhead 6.3.1 upgrade | mainnet | Adopted | RSKIP |
Arrowhead 6.0.0
Activated on mainnet at block 6,223,700 on 3 Apr 2024, and on testnet at block 4,927,100. Specified by RSKIP414, released as rskj Arrowhead 6.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 203 | getCallStackDepth Precompile method | testnet mainnet | Adopted | RSKIP |
| 376 | Set version 2 to PowPeg migration transactions | testnet mainnet | Adopted | RSKIP |
| 379 | Bridge peg-out and migration transactions index | testnet mainnet | Adopted | RSKIP |
| 398 | PUSH0 instruction | testnet mainnet | Adopted | RSKIP |
| 400 | Calldata gas cost reduction | testnet mainnet | Adopted | RSKIP |
| 412 | BASEFEE instruction | testnet mainnet | Adopted | RSKIP |
| 414 | Network Upgrade: Arrowhead upgrade | testnet mainnet | Adopted | RSKIP |
| 415 | Fix pegnatories address derivation from public keys | testnet mainnet | Adopted | RSKIP |
| 417 | Avoid transactions to be reverted when Bridge method calls from smart contracts return an empty response | testnet mainnet | Adopted | RSKIP |
Fingerroot 5.0.0
Activated on mainnet at block 5,468,000 on 13 Jul 2023, and on testnet at block 4,015,800. Specified by RSKIP388, released as rskj Fingerroot 5.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 252 | Transaction Gas Price Cap | testnet mainnet | Adopted | RSKIP |
| 326 | Pegout events improvements | testnet mainnet | Adopted | RSKIP |
| 374 | Reestablish the number of block confirmations for a PowPeg migration period | testnet mainnet | Adopted | RSKIP |
| 375 | Use the pegout creation transaction hash as the key in the map structure that stores the pegout transactions waiting for signatures | testnet mainnet | Adopted | RSKIP |
| 377 | Store the last retired federation **standard** P2SH script | testnet mainnet | Adopted | RSKIP |
| 383 | Increase POWpeg activation age | testnet mainnet | Adopted | RSKIP |
| 385 | Bridge method `getEstimatedFeesForNextPegOutEvent` improvement | testnet mainnet | Adopted | RSKIP |
| 388 | Network Upgrade: Fingerroot upgrade | testnet mainnet | Adopted | RSKIP |
Hop 4.0.1 patch
Activated on mainnet at block 4,976,300 on 17 Jan 2023, and on testnet at block 3,362,200. Specified by RSKIP358, released as rskj Hop 4.0.1. A patch upgrade (RSKIP358) remediating the peg-out service outage of 2022.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 353 | Align RSK P2SH redeem script with Bitcoin Core standard transactions checks | testnet mainnet | Adopted | RSKIP |
| 357 | Adjust the number of block confirmations for a PowPeg migration period | testnet mainnet | Adopted | RSKIP |
| 358 | Network Upgrade (patch): Hop 4.0.1 upgrade | testnet mainnet | Adopted | RSKIP |
Hop 4.0.0
Activated on mainnet at block 4,598,500 on 31 Aug 2022, and on testnet at block 3,103,000. Specified by RSKIP291, released as rskj Hop 4.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 271 | Bridge peg-out Batching | testnet mainnet | Adopted | RSKIP |
| 284 | New deserialization method for Flyover refund addresses | testnet mainnet | Adopted | RSKIP |
| 290 | Adjust Testnet block minimum difficulty | testnet mainnet | Adopted | RSKIP |
| 291 | Network Upgrade: Hop upgrade | testnet mainnet | Adopted | RSKIP |
| 293 | Add method `getActivePowpegRedeemScript` to the Bridge contract and perform additional Flyover peg-in validations | testnet mainnet | Adopted | RSKIP |
| 294 | Limit the number of inputs to include in a migration transaction | testnet mainnet | Adopted | RSKIP |
| 297 | Increase max timestamp difference between btc and rsk blocks for Testnet | testnet mainnet | Adopted | RSKIP |
Iris 3.0.0
Activated on mainnet at block 3,614,800 on 19 Aug 2021, and on testnet at block 2,060,500. Specified by RSKIP187, released as rskj Iris 3.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 153 | Add BLAKE2 Compression Function `F` Precompile | testnet mainnet | Adopted | RSKIP |
| 169 | Rectify EXTCODEHASH implementation | testnet mainnet | Adopted | RSKIP |
| 170 | Peg-in to any address | testnet mainnet | Adopted | RSKIP |
| 171 | Clean EVM Internal Buffer in Call-like Opcodes | testnet mainnet | Adopted | RSKIP |
| 174 | Preserve balance in contract creation | testnet mainnet | Adopted | RSKIP |
| 176 | Programmable Peg-in Addresses for faster peg-ins | testnet mainnet | Adopted | RSKIP |
| 179 | BTC-RSK timestamp linking | testnet mainnet | Adopted | RSKIP |
| 181 | Peg-in rejection events | testnet mainnet | Adopted | RSKIP |
| 185 | Peg-out refund and events | testnet mainnet | Adopted | RSKIP |
| 186 | Active Federation creation block height registration | testnet mainnet | Adopted | RSKIP |
| 187 | Network Upgrade: Iris upgrade | testnet mainnet | Adopted | RSKIP |
| 191 | Remove opcodes incompatible with Ethereum | testnet mainnet | Adopted | RSKIP |
| 197 | Fix Precompile Calls Not Conforming With CALL Semantics | testnet mainnet | Adopted | RSKIP |
| 199 | registerBtcTransaction Is Public | testnet mainnet | Adopted | RSKIP |
| 200 | Receive headers limits | testnet mainnet | Adopted | RSKIP |
| 201 | Time-locked Emergency Multisignature | testnet mainnet | Adopted | RSKIP |
| 218 | New Fee Rewards Address for the RSK Core Developers Fund | testnet mainnet | Adopted | RSKIP |
| 219 | New minimum values for peg-in and peg-outs | testnet mainnet | Adopted | RSKIP |
| 220 | Obtain Bitcoin Block information from bridge methods | testnet mainnet | Adopted | RSKIP |
Papyrus 2.0.0
Activated on mainnet at block 2,392,700 on 27 May 2020, and on testnet at block 863,000. Specified by RSKIP141, released as rskj Papyrus 2.0.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 134 | Locking cap | testnet mainnet | Draft | RSKIP |
| 137 | ECADD, ECMUL and PairingCheck precompiled contracts no document | testnet mainnet | — | RSKIP |
| 140 | EXTCODEHASH opcode | testnet mainnet | Adopted | RSKIP |
| 141 | Network Upgrade: Papyrus upgrade | testnet mainnet | Adopted | RSKIP |
| 143 | 2WP segwit compatibility(P2SH-P2WPKH) no document | testnet mainnet | — | RSKIP |
| 146 | Encode bridge events in Solidity format | testnet mainnet | Adopted | RSKIP |
| 151 | SELFBALANCE opcode no document | testnet mainnet | — | RSKIP |
| 152 | CHAINID Opcode | testnet mainnet | Adopted | RSKIP |
| 156 | Reduce difficulty adjustement coefficient between blocks no document | testnet mainnet | — | RSKIP |
Orchid 0.5.0
Activated on mainnet at block 729,000 on 8 Sep 2018, and on testnet at block 802,000. Specified by RSKIP99, released as rskj Orchid 0.5.0.
| RSKIP | Title | Network | Status | Source |
|---|---|---|---|---|
| 85 | Improvements to REMASC contract | mainnet testnet | Adopted | RSKIP |
| 87 | Whitelisting unlimited mode | mainnet testnet | Adopted | RSKIP |
| 88 | Bridge methods local calls restrictions no document | mainnet testnet | — | RSKIP |
| 89 | Add Bitcoin block query methods to the bridge contract | mainnet testnet | Adopted | RSKIP |
| 90 | EXTCODESIZE support for native contracts no document | mainnet testnet | — | RSKIP |
| 91 | STATIC_CALL opcode | mainnet testnet | Adopted | RSKIP |
| 92 | Merkle Proof serialization | mainnet testnet | Adopted | RSKIP |
| 93 | Deprecated native contract no document | mainnet testnet | — | RSKIP |
| 94 | Disable code replace no document | mainnet testnet | — | RSKIP |
| 97 | Remove difficulty drop no document | mainnet testnet | — | RSKIP |
| 98 | Deactivation of the federated fallback system for block production | mainnet testnet | Adopted | RSKIP |
| 99 | Orchid Network Upgrade upgrade | mainnet testnet | Adopted | RSKIP |
Adopted, but no release on record
A further 28 RSKIPs are marked Adopted in the index — meaning they are in force — but no network-upgrade RSKIP claims them, so there is nothing to say which release activated them. They are listed here rather than omitted, because leaving them out would imply that REMASC, the Bridge and CREATE2 are not part of Rootstock.
Almost all of them date from before the convention of writing an upgrade RSKIP took hold: the 2016–2018 proposals went into Bamboo and Orchid, and the 2019 batch — RSKIP120 (shifting opcodes), RSKIP125 (CREATE2), RSKIP119 (the block-header precompile) — matches what the Wasabi release notes describe in prose. That is corroboration, not proof, so they are left unassigned.
| RSKIP | Title | Created | Layer | Status |
|---|---|---|---|---|
| 0 | RSKIP Purpose and Guidelines | 07-MAY-18 | — | Adopted |
| 6 | Block Size Limit | 22-JUN-16 | Core | Adopted |
| 9 | Negotiated Minimum Gas Price | 21-OCT-16 | Core | Adopted |
| 11 | TXINDEX Opcode | 07-AUG-16 | Core | Adopted |
| 15 | Simplified Reward Manager Smart Contract (REMASC) | 14-NOV-16 | Core | Adopted |
| 26 | DUPN and SWAPN opcodes | 27-DIC-16 | Core | Adopted |
| 33 | CODEREPLACE opcode | 17-JAN-17 | Core | Adopted |
| 40 | Basic Bridge for two-way-peg to Bitcoin | 25-APR-17 | Core | Adopted |
| 42 | Remove world midstates from receipts | 22-JUN-17 | Core | Adopted |
| 46 | Block Mining Fees Information Mechanism | 04-OCT-17 | Node | Adopted |
| 50 | Script Versions using HEADER pesuo-opcode | 07-DIC-17 | Core | Adopted |
| 51 | Memory-Mapped configuration register | 10-DIC-17 | Core | Adopted |
| 57 | Derivation Path for Hierarchical Deterministic Wallets | 05-ABR-18 | Net | Adopted |
| 60 | Checksum Address Encoding | 25-JUN-18 | Net | Adopted |
| 106 | Precompiled contract for HDWallet utility functions | 2019 | Core | Adopted |
| 119 | Precompiled contract for inspecting block headers | 2019 | Core | Adopted |
| 120 | Shifting opcodes | 2019 | Core | Adopted |
| 123 | Multikey federation members | 2019 | Core | Adopted |
| 125 | Create2 | 2019 | Core | Adopted |
| 131 | Preventing CREATE2-after-SUICIDE in the same block | 2019 | Core | Adopted |
| 132 | Bridge ReceiveHeaders Gas Cost increase | 2019 | Core | Adopted |
| 148 | ERC1820 Pseudo-introspection Registry Contract | 6-NOV-19 | DApp | Adopted |
| 157 | Cumulative Difficulty in JSON-RPC block responses | 11-FEB-20 | Node | Adopted |
| 159 | Minimal Proxy Contract | 19-FEB-20 | DApp | Adopted |
| 177 | Universal Merged Mining Extension | APR-2020 | Node | Adopted |
| 180 | Limit the RSK merged mining merkle proof size | 15-JUL-21 | Core | Adopted |
| 225 | Emergency Multisig public keys | 1-APR-21 | Core | Adopted |
| 712 | RSK typed structured data hashing and signing | 02-NOV-2020 | UI | Adopted |
RSKIP0 appears in this table because it is Adopted, but it defines the proposal process rather than a consensus rule — there was never a block at which it "activated". It is the one row here that is not a protocol change.
Nine proposals that shipped but were never written up
9 of the RSKIPs above have no document in the repository and no row in the index. They exist only as line items inside the upgrade that activated them — Orchid and Papyrus each name a handful of proposals by number and title that were never filed.
They are consensus rules in force today. Someone wanting to know exactly what RSKIP143 did to peg-in handling has only its one-line title, the rskj source, and the chain itself.
| RSKIP | Title, as the upgrade names it | Shipped in |
|---|---|---|
| 88 | Bridge methods local calls restrictions | Orchid |
| 90 | EXTCODESIZE support for native contracts | Orchid |
| 93 | Deprecated native contract | Orchid |
| 94 | Disable code replace | Orchid |
| 97 | Remove difficulty drop | Orchid |
| 137 | ECADD, ECMUL and PairingCheck precompiled contracts | Papyrus |
| 143 | 2WP segwit compatibility(P2SH-P2WPKH) | Papyrus |
| 151 | SELFBALANCE opcode | Papyrus |
| 156 | Reduce difficulty adjustement coefficient between blocks | Papyrus |
The numbers above are not links because there is nothing to link to. A proposal's
filename cannot be derived from its number in any case: low numbers are zero-padded
(RSKIP06.md, not RSKIP6.md), and these nine have no file under any
spelling. The collector reads the repository's own file list and links only what exists,
rather than constructing a URL and hoping.
How this table is built
By a script, re-run weekly, that reads the RSKIP repository rather than copying from it by hand. It:
- parses the index table for every proposal's number, title, author, date and status;
- finds the 12 network-upgrade RSKIPs and fetches each one;
- parses each for its codename, its mainnet and testnet activation heights, and its
"Included RSKIPs" list — keeping the
(Testnet-only)and(Mainnet-only)tags, which are what make a proposal's two activations on two networks distinguishable; - dates every mainnet height against a Rootstock node;
- drops everything that never activated.
Five different document formats have to be read, because the convention changed as it
went — RSKIP99 writes Mainnet activation block number: and links
[RSKIP 85](RSKIP85.md); RSKIP141 writes RSK Mainnet block: and
plain RSKIP134:; RSKIP518 nests heights under a per-release heading. Parsing
only the newest shape would silently lose the first decade.
What the repository does not record, and how that is handled
Some activations are simply not in the RSKIP documents. 5 on this
page come from a hand-maintained file, data/rskip-overlay.json, which the
collector reads and never writes — so re-running it preserves everything
entered by hand. Every entry in that file must carry a source URL or the collector refuses
to publish it.
Those 5 are marked release notes in the tables above. They are the Reed 8.1.0 set: RSKIP518 lists only the 8.0.0 payload under "Included RSKIPs", so the five proposals that activated on testnet in the second release are knowable only from the REED-8.1.0 release notes.
Hand-entered data is cross-checked, not trusted. Where the upgrade RSKIP does state a height for a release and network, the collector compares it against the hand-entered one and fails the run if they disagree, rather than publishing either. The overlay can add facts the documents lack; it cannot quietly contradict them.
What is missing
Two upgrades ship no RSKIPs on this page, because no primary source says which they were:
| Missing | Why |
|---|---|
| Which RSKIPs shipped in Wasabi | Wasabi has no network-upgrade RSKIP — the first one is RSKIP99 for Orchid, and the convention of writing one per upgrade only becomes consistent from Papyrus (RSKIP141) onward. The WASABI-1.0.0 release notes describe the consensus changes in prose and cite no RSKIP numbers. Nothing in this file fills that in, because no primary source was found that states it. |
| Which RSKIPs shipped in Bamboo and Ginger | Both predate the RSKIP process being used to scope upgrades (RSKIP0, which defines the process, is dated 07-MAY-18; Bamboo 0.3.0 was released 04-DEC-17). Their release notes cite no RSKIP numbers and the index contains no entry for either codename. |
Both predate the convention. RSKIP0, which defines the process, is dated May 2018; Bamboo shipped in December 2017, and Wasabi's release notes describe its consensus changes in prose without citing a single RSKIP number. The first upgrade with its own proposal is Orchid.