Skip to content

docs: Add deployment checklist for mainnet contract deployment #656

Description

@FaveTeamz

Summary

The existing contract upgrade runbook covers the technical steps but there is no pre-deployment checklist ensuring all safety gates are passed before a mainnet deployment. A missed step could result in an uninitialized contract or a broken admin key.

Problem

Without a formal deployment checklist, a rushed deployment could skip steps like mutation score verification, testnet smoke tests, or admin key backup — any of which could result in an unrecoverable contract state on mainnet.

Acceptance Criteria

  • Create docs/runbooks/mainnet-deployment-checklist.md with the following sections:
    • Pre-deployment: mutation score >= 90%, all E2E tests passing on testnet, admin key backup confirmed
    • Deployment steps: build → optimize → verify binary size < 20KB → upload WASM → call upgrade → call initialize (or verify already initialized)
    • Post-deployment: smoke test on mainnet, verify event emission, update contract ID in backend config
    • Rollback: steps for reverting to previous WASM hash
  • Add a GitHub Issue template for mainnet deployment that links to this checklist
  • Review with at least 2 team members before merging

Metadata

Metadata

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions