Repository navigation
docs: record the mainnet events 1.8.0 and profile 1.2.1 upgrade - #169
Merged
Merged
Conversation
Mainnet went to events 1.8.0 (tag events-v1.8.0) and profile 1.2.1 on 17 October 2026. Runbook section 8 now lists every transaction, section 1 says the 17,280-ledger timelock is live, and section 6 no longer says the events migration marker trails its version. README shows the new versions, the backlog moves the upgrade to Done, and the threat model, multisig guide and storage doc describe mainnet as upgraded. The storage replay fixtures are still 1.7.0 and 1.2.0; refreshing them stays on the backlog.
Plan expiredYour subscription has expired. Please renew your subscription to continue using CI/CD integration and other features. |
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.
Mainnet now runs events 1.8.0 (the 2.0.0 code, tag
events-v1.8.0) and profile 1.2.1. The upgrade ran on 17 October 2026 between 23:09 and 23:43 UTC. This PR updates the docs to match. Docs only.docs/upgrade-runbook.md:README.md: the deployments table shows events 1.8.0 and profile 1.2.1.BACKLOG.md: the upgrade moves from P0 to Done. The 2.1.0 item now says to refresh the storage replay from 1.8.0 first.docs/threat-model.md: section 4.4 records the upgrade as done, and the timelock rows (EoP.10, Tamp.10, the admin table) describe mainnet as upgraded.docs/multisig-guide.mdanddocs/storage-compatibility.mdare updated to match. The storage doc says the fixtures are still the 1.7.0 and 1.2.0 builds.What I checked on mainnet after the unpause:
upgrade-statusshows events 1.8.0 (wasmacf70ca0…) and profile 1.2.1 (wasm8a8a1208…), both migrated to their new version, nothing pending, unpaused, and the multisig as admin.get_eventreads all eight events, including the two records that were in the old layout.