Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Create a market or add a vault

Create a market

Curator → Markets → Create new market. Four steps:

  1. Setup: choose the chain. The final governor is chosen later, when the vaults are unpaused.
  2. Assets: choose the assets that get a vault, in order.
  3. Pricing basis: choose the unit everything is priced in, for example US dollars.
  4. Review: check the contracts to create, the unit of account, the deployment, the initial settings and the factories.

You sign the deployment transactions. Vaults are created paused under your wallet, configured, then unpaused and handed to the chosen governor, so the market never trades half-configured. After each receipt, the new contracts are read back and compared with the review.

While you're creating a market, it has its own workspace in Recent, and its own Oracles and Risk tabs for routes and LTVs before launch.

Once the market is live, the Toolbox offers to claim the vaults for labels. Claim them all and put them in one product; see Markets and products. The Euler app doesn't list them until they're in a published product.

Add a vault

Overview → Add vault:

OptionWhat happens
Create new vaultOne transaction deploys a vault for an asset, applies its settings, unpauses it and hands it to the market's governor. Until the governor's changes land, the vault is supply-only: resolve it in the router, price its asset and accept it as collateral, all from Changes (through a timelock, they're scheduled first).
Add existing vaultRecords an existing vault as part of this market, in this browser. No transaction is sent. If another governor holds it, the market is under two governors until that governor hands it over.

Then add the vault to the market's product under Labels, so the Euler app lists it and Market Ops keeps counting it as a member.

Your deployments

Tools → Oracle adapters, Tools → Interest-rate models and Tools → Governance list what this browser has deployed on each chain (Governance also lists deployed stewards), with a status: sent, deployed, in use, failed, waiting for authorization, verifying, or imported but not verified.

The same deployments are offered where they're used, in Configuration sections and in Transfer governance.

You can export the list to a file to move it to another browser, import a file, or add an existing adapter, model or governor suite by its address.