Governance
Timelock operations
Changed onOperations scheduled on suite timelocks and on the EVault factory timelock, newest scheduling first. Each operation carries its latest scheduling and the calls of that scheduling, ordered by index, with calldata as scheduled (not decoded).
- chainId is required.
- At most one of timelock, governor and vault; more than one answers 400. governor selects both timelocks of that governor's suite; vault selects the timelocks of the suite of the vault's current governor.
- status is computed at request time: a scheduled operation is pending until readyAt and ready from readyAt on, as TimelockController.isOperationReady. An executed operation is executed and a cancelled one cancelled.
- Block numbers, readyAt (Unix seconds), delays (seconds) and call values (wei) are decimal strings; event timestamps are ISO 8601.
get/v3/governance/timelock-operations
Request
- Base URLhttps://v3.euler.finance
- URLhttps://v3.euler.finance/v3/governance/timelock-operations
- Authnone required
Query parameters
chainIdinteger required
timelockstring
governorstring
vaultstring
statusstring
Comma-separated statuses to include: pending, ready, executed, cancelled. Every status when omitted; unknown values answer 400.
offsetinteger
Page offset, capped at 10000 to bound query cost.
limitinteger
Requested page size. Values above the endpoint cap are clamped; the default shared cap is 100.
Response
Timelock operations
Changes
- info
endpoint added
- info