Skip to content

docs: use go-live task in deployment runbook - #147

Open
dlkakbs wants to merge 1 commit into
FhenixProtocol:masterfrom
dlkakbs:docs/use-go-live-task
Open

dlkakbs wants to merge 1 commit into
FhenixProtocol:masterfrom
dlkakbs:docs/use-go-live-task

Conversation

@dlkakbs

@dlkakbs dlkakbs commented Oct 14, 2026 •

Copy link
Copy Markdown

Summary

Aligns the main deployment runbook with the go-live workflow introduced in #145.

The runbook still instructed operators to call addToAccessList() and enable() manually, while the current tooling provides task:goLiveAsSafe to validate readiness and perform both operations through the configured Safe flow.

What changed

  • Replaces the manual addToAccessList() and enable() instructions with npx hardhat task:goLiveAsSafe --accounts <addr>[,<addr>...] --network <net>.
  • Documents the task's preflight checks for production signers, ACL, PlaintextsStorage, share-registry wiring and access-list enforcement.
  • Clarifies SAFE_OWNER_KEY execution versus Transaction Builder batch generation.
  • Documents re-running the task to verify execution.
  • Adds the follow-up access-list and emergency-stop commands.

Why

task:goLiveAsSafe was added specifically to make the mainnet activation sequence safer and repeatable. It checks the required deployment state before opening intake and keeps addToAccessList() and enable() in the intended Safe-controlled flow.

The mainnet deployment guide and quickstart already use this task, but docs/deployment-runbook.md was not updated in #145. This change removes that documentation drift and prevents the primary runbook from directing operators around the existing readiness checks.

Validation

  • Confirmed task:goLiveAsSafe, task:addToAccessList and task:disableTaskManager are registered by the host-chain task package.
  • Confirmed the referenced signer documentation exists.
  • git diff --check passes.

Documentation-only change; no runtime or contract behavior is modified.

@dlkakbs
dlkakbs requested a review from a team as a code owner October 14, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant