Skip to main content
Governance is the production owner of the controller. The controller owns the central pool. 
governance owner -> governance contract -> controller -> pool

​
Timelock Flow

  1. A proposer builds an AdminOperation.
  2. Governance validates the operation and schedules it with propose.
  3. The operation waits until get_min_delay() ledgers pass.
  4. A valid executor, or anyone for open execution, calls execute.
  5. Governance calls the controller or applies a governance-self operation.

​
Roles

Governance roles are:
  • PROPOSER
  • EXECUTOR
  • CANCELLER
  • ORACLE
Delegated EXECUTOR and CANCELLER authority should be separated for launch.

​
Operation Scope

Governance controls:
  • hub, spoke, and spoke-asset configuration;
  • market creation and token approval;
  • pool deployment, pool params, and pool upgrades;
  • oracle config, disable, tolerance, and sanity configuration;
  • aggregator and accumulator addresses;
  • Blend pool allow-list;
  • controller upgrade, migration, and ownership;
  • governance roles, delay, ownership, and upgrade.

​
Emergency Controls

Pause and unpause remain immediate owner actions. They are emergency controls, not the normal path for protocol configuration.

​
Next

Governance ABI

Entry points and AdminOperation groups.

Configuration

Controller configuration surface.