Skip to main content

Pause Dashboard

Backoffice view for the ZKHub pause circuit breaker — the emergency stop that halts every user-facing operation (mints, burns, transfers) across all tokens on a network while leaving admin/recovery paths open. Network-scoped: pick a network first; every panel below reflects that network's Hub.

Two authority models meet here, matching the contract:

  • pause() is callable by any registered pauser — it is sent directly from the operator's connected wallet, not through a Safe. Fast by design (incident response). The button is gated on a live pausers(address) read of the connected wallet.
  • unpause() and setPauser() are owner-only, so they run through the owner Safe (OWNER multisig role) as ordinary propose → sign → execute proposals.

Protocol Status (required)​

Live paused() flag for the selected network's Hub, plus the Hub address.

  • State — Active or Paused (polled live)
  • ZKHub — the Hub contract address (also what the wallet targets for pause())
  • Pause — when active: a direct-wallet pause() button, enabled only if the connected wallet is a registered pauser and on the right chain
  • Unpause — when paused: Propose unpause stages an owner Safe proposal (requires PAUSE_PROPOSE); it takes effect once signed + executed below

Pausers (required)​

The current pauser set, reconstructed from the indexer's PauserUpdated feed (the owner is implicitly a pauser and is not listed). Each entry shows the pauser address, when it was granted, and the granting tx.

Holders of PAUSE_PROPOSE can grant or revoke pausing rights for an address — each stages an owner Safe proposal (setPauser), applied only once that proposal is signed + executed.

Pending Owner Actions (required)​

Owner Safe proposals awaiting signatures for this network (setPauser / unpause). Each shows a human summary of the action, signature progress, the Sign control (gated on-chain by the Safe's owner set), and an Execute button once threshold + nonce are reached. Pause proposals are generic (no owning request), so they are executed manually here rather than auto-broadcast.

History (required)​

Pause / unpause and pauser grant / revoke events for the network, most recent first, from the indexer's hubEvent feed.

  • Event — Paused, Unpaused, Pauser granted, Pauser revoked
  • Who — the transaction sender (resolved live, since the Paused/Unpaused events carry no address)
  • Pauser — the affected address (grant / revoke only)
  • Time — block timestamp
  • Tx — on-chain transaction hash

Access​

  • PAUSE_READ — view this dashboard (Compliance Officer, Compliance Signer, Internal Auditor).
  • PAUSE_PROPOSE — propose owner actions, i.e. grant/revoke pausers and unpause (Compliance Officer).
  • Sending pause() needs no backoffice permission beyond PAUSE_READ — the authority is on-chain (the connected wallet must be a registered pauser).