Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

BNB Chain Mainnet

Fixed Term Vaults Contracts

Deployed vaults

  • Vault, position token ID 1: 0x7D80A10bEdD13638888e7A946B82878E21fbB820 — USDT supplied against XAUM collateral over a 30-day term, at a 6% fixed borrow rate; after the 10% reserve factor, suppliers earn 5.4% net.

Liquidation whitelist

Liquidation entry points on each vault are reachable only through the LiquidationAdapter, which keeps two independent, governance-managed lists: one for health-based liquidators and one for overdue settlers (set via setLiquidatorWhitelist and setSettlerWhitelist). As currently configured on BNB Chain mainnet, both lists contain a single entry — the Venus Critical Guardian multisig 0x7B1AE5Ea599bC56734624b95589e7E8E64C351c9 — so it is the only address that can currently perform either a health-based or an overdue liquidation. Governance can add or remove entries on either list at any time. The permissionless repayBadDebt path on each vault is independent of these lists and remains open to any address.

BNB Chain Testnet

Fixed Term Vaults Contracts

Last updated