Skip to content

Fixed Term Vaults

Core contracts for the Fixed Term Vaults system. Each institution’s vault is deployed as an EIP-1167 clone by governance via createVault(...) on InstitutionalVaultController. The canonical, always-current list of deployed vaults lives on-chain — query the controller’s allVaults array (or the VaultCreated event log). The vaults known at the time of writing are listed below for convenience.

The stable implementation and deployment baseline is fixed-rate-vaults v1.0.0. Proxy implementations, vault state, terms, balances, pause levels, owners, permissions, and liquidation whitelists can change. Verify the live controller, vault, and adapter before interacting.

Liquidation entry points on each vault are reachable only through the LiquidationAdapter, which keeps two independent, governance-managed mappings: one for health-based liquidators and one for overdue settlers (set via setLiquidatorWhitelist and setSettlerWhitelist). At the checkpoint, the Venus Critical Guardian multisig 0x7B1AE5Ea599bC56734624b95589e7E8E64C351c9 returned true in both mappings. The mappings are not enumerable, so this does not prove it is the only authorized address; reconstruct the update events and re-read the selected caller. The permissionless repayBadDebt path on each vault is independent of these mappings.