Skip to main content

Governance Roles

Current Phase: Shadow Mainnet Testing

Multyr contracts are deployed on Arbitrum One. The system is currently in validation phase. Deposits are not open to the public. Behavior described on this page reflects the protocol's designed behavior; some mechanisms are active in shadow testing, others become active at public launch. See the Status page for details.

Multyr governance is structured across distinct roles with separate responsibilities.

This separation is intended to reduce control concentration and improve safety.


SAFE_GOV

  • Type: 3/5 multisig
  • Role: governance execution

SAFE_GOV is responsible for:

  • scheduling governance actions
  • executing approved transactions
  • managing protocol-level configuration through the timelock process

SAFE_GOV cannot bypass the timelock.


SAFE_GUARDIAN

  • Type: 1/1 multisig
  • Role: emergency response

SAFE_GUARDIAN is responsible for urgent protective actions, including:

  • pausing the system
  • degrading or disabling strategies

SAFE_GUARDIAN cannot modify governance parameters.


SAFE_VETO

  • Type: 1/1 multisig
  • Role: governance safety control

SAFE_VETO may:

  • cancel pending timelock transactions
  • block queued governance actions before execution

SAFE_VETO cannot propose or execute changes.


Separation of Powers

The governance model separates:

  • governance execution → SAFE_GOV
  • emergency intervention → SAFE_GUARDIAN
  • protective cancellation → SAFE_VETO

No single role is intended to hold full control over the system.


Why This Matters

This structure helps ensure that:

  • no parameter changes can be applied immediately
  • emergency responses remain limited in scope
  • governance actions are reviewable before execution
  • unsafe queued changes can be stopped