Repository navigation
[Feature] Mainnet-specific deployment runbook #205
Description
Summary
docs/src/DEPLOYMENT.md already covers parameter selection (now backed by real analysis in V1_MAINNET_PARAMETERS.md, #190), the deploy sequence, and an admin runbook (key rotation, pausing, resolver rotation). All of it is written testnet-first: every CLI example uses --network testnet, the only worked example uses throwaway resolver1/resolver2/resolver3 test identities, and the doc's own opening line is "this is testnet-only until audited."
What's still missing is the mainnet-specific operational layer: how do you actually run this with real value at stake, not just how do the contract calls work.
Scope
- Key custody guidance for the admin and resolver roles specifically for a mainnet deployment: hardware wallet or multisig expectations, who holds keys, what happens if one is lost or compromised, cross-referencing
V1_MAINNET_PARAMETERS.md's existing "reachability and independence" resolver-composition guidance rather than duplicating it. - A concrete go/no-go launch sequence that ties the existing "Mainnet readiness checklist" items together into an actual procedure: what order to do things in, who signs off, what the rollback plan is if something goes wrong in the first hours/days after launch.
- Incident escalation specifics for a mainnet context: who gets paged, how fast, and what the decision tree looks like for choosing between
set_pausedand a resolver-committee rotation versus doing nothing and waiting for the normal dispute flow to work. - This should be additive to
DEPLOYMENT.md(a new section, or a linked mainnet-specific companion doc, the assignee's call), not a rewrite of the existing testnet-focused content, which stays correct and useful as-is.
Proposed approach
Not prescribed. This is explicitly prep work written ahead of the actual audit clearing (the hard blocker per SECURITY.md), the same way V1_MAINNET_PARAMETERS.md was written ahead of live testnet data being available: useful to have ready rather than written under time pressure once the audit finishes. It should say so explicitly wherever it lives, so nobody mistakes its existence for a signal that mainnet deployment is currently authorized.
Activity
Iker2522 commentedon Sep 7, 2026
I'd like to take this issue on!
I can author the production mainnet operational guide and go/no-go launch playbook in docs/src/MAINNET_OPERATIONS.md to complement our existing testnet DEPLOYMENT.md.
I will define hardware wallet and multi-sig custody standards for Admin and Resolver keys, craft an ordered go/no-go launch checklist with early-stage rollback contingencies, and establish a clear incident escalation decision tree for executing set_paused versus resolver rotations during live production incidents.
The doc will be fully additive, cross-referencing V1_MAINNET_PARAMETERS.md and explicitly framing the material as pre-audit preparation per SECURITY.md. PR ready in 1–2 days.
Fading-Dev commentedon Sep 7, 2026
Hello! I’d be glad to work on this. The issue presents a good opportunity to improve the project, and I’m confident I can deliver the requested functionality while keeping the existing behavior intact. I’ll validate everything before opening the PR.
Fading-Dev commentedon Sep 7, 2026
Hello! I’d be glad to work on this. The issue presents a good opportunity to improve the project, and I’m confident I can deliver the requested functionality while keeping the existing behavior intact. I’ll validate everything before opening the PR.
xtep103 commentedon Sep 7, 2026
Hi! I'd like to work on this issue.
After reviewing the description, my understanding is that
DEPLOYMENT.mdalready documents the on-chain deployment and governance mechanics, while the missing piece is the operational guidance required for a real mainnet deployment. My plan would be to add a mainnet-focused operational section (or companion document) covering:V1_MAINNET_PARAMETERS.md.I'll aim to keep the work additive and avoid duplicating existing deployment or parameter-selection documentation.
I'd be happy to put together a draft PR if this approach aligns with the maintainers' expectations.
Please assign issue to me.
grantfox-oss commentedon Sep 7, 2026
🦊 GrantFox — @Iker2522 has been assigned to this issue!
Next steps:
Closes #205)Good luck! Track your progress on GrantFox.
Add MAINNET_RUNBOOK.md: admin key custody, launch sequence, incident …
docs: mainnet operational runbook (admin custody, launch sequence, in…
grantfox-oss commentedon Sep 11, 2026
🎉 This issue has been marked as completed on GrantFox!
@Iker2522's PR #208 was approved and merged by @collinsezedike.
🏆 @Iker2522: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (328 total points). Track your full progress on GrantFox.
👏 Great work, @Iker2522! Keep contributing to drydocs.