Bump consensus runtime spec_version to 11 - #3894
Merged
Merged
Conversation
Contributor
Author
|
@BugBot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit dd2e6a4. Configure here.
vedhavyas
marked this pull request as ready for review
July 29, 2026 12:09
🛡️ Immunefi PR ReviewsWe noticed that your project isn't set up for automatic code reviews. If you'd like this PR reviewed by the Immunefi team, you can request it manually using the link below: Once submitted, we'll take care of assigning a reviewer and follow up here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps consensus spec_version 10 -> 11 for the runtime release.
The only runtime change since runtime-mainnet-2026-jun-23 is #3888, which prices dynamic storage cost off network-wide credit supply and seeds the transporter storage migration. transaction_version stays 1. The domain runtimes are left alone since the transporter migration is a no-op there.
Dynamic cost of storage is on for mainnet, so this steps the per-byte storage fee up roughly 4.9x at the upgrade block. That's the correction #3888 describes rather than a new fee. Chronos has it off.
Code contributor checklist: