docs(genesis-writer): add the post-cutover follow-ons to the rollout runbook - #573
Open
rickyrombo wants to merge 3 commits into
Open
docs(genesis-writer): add the post-cutover follow-ons to the rollout runbook#573rickyrombo wants to merge 3 commits into
rickyrombo wants to merge 3 commits into
Conversation
…runbook Two pieces of work were designed around the migration but the runbook did not carry them: the upgrade schedule for audius-mainnet-beta (#572), which must merge before the bootstrap build or the new chain runs with no enforcement and no cid attestation, and the legacy reward wire-compat removal (#232), which must not merge until every node has left the old chain. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… enforcement at step 10 Review fixes. The placeholder substitution had mangled OPENAUDIO_DELEGATE_PRIVATE_KEY in Appendix J; restored. Step 17 had bundled a pre-bootstrap prerequisite (#572) with a post-cutover cleanup (#232) under an "after 15" label; #572 now lives in step 3 with a rebase instruction, and step 17 is #232 alone. The enforcement checks move to the first migrated node in step 10 and name the real submission path and the real skew symptom (a commit timeout, not the pre-gate error text). Appendix C gains the claim-coverage check. Step 11 records, as unresolved, that the flusher stalls on the first post-snapshot track create under content auth. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…the bootstrap build Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
The runbook ended at step 16 and did not carry the work designed around the migration. This adds it in the places an operator will actually read:
audius-mainnet-betaupgrade-schedule entry from feat(core): schedule auth and content-auth enforcement on audius-mainnet-beta #572, so build(core): point the prod build at audius-mainnet-beta — *DO NOT MERGE* #553 has to be rebased after feat(core): schedule auth and content-auth enforcement on audius-mainnet-beta #572 merges. Explains why both heights and why block 1. feat(core): schedule auth and content-auth enforcement on audius-mainnet-beta #572 is also in the "merge these first" table.tx waiting timeouton attestation.🤖 Generated with Claude Code