From zero to a listed market
The launch steps come in the order they depend on each other; the rest apply once the market runs. Every step links to a page that explains it.
Launch
- Get set up. Euler creates your organisation, registers the addresses you govern vaults with, and adds your first admin. Register the address you'll deploy and govern with: every vault claim is checked against it. Get access
- Check your profile. Labels → Profile: name, logo, description, links, and your verified addresses. If a product has no website or logo of its own, it uses these. Labels and metadata
- Decide who governs. A wallet is enough for a test market. A live market usually needs a Safe, or a governor contract with timelocks. You can deploy a governor with its timelocks from a preset under Tools → Governance. Governance
- Prepare prices and rates, if needed. The market creation flow offers known feeds and rate models. For anything else, deploy oracle adapters and interest-rate models under Tools first. Oracle adapters and routes, Interest-rate models
- Create the market. Markets → Create new market: the chain, the assets, the pricing basis, a review, then your signatures. Vaults are created paused, configured, then handed to your governor, so the market never trades half-configured. Create a market or add a vault
- Give it a product. Claim all the new vaults into one product; the creation flow offers to do this for you. Name the product, describe it and add a logo. Labels and metadata
- Wait for publication. Euler publishes your labels. Until then, the Euler app shows your vaults as unknown and hides them by default. Afterwards, each vault's Discovery status says whether it's listed, and why. Publishing and versions
Run the market
- Operate. Change caps, LTVs, rate models, routes and fees. Every change goes through the same steps: stage, review, simulate, sign, verify. Share staged changes with a co-signer when someone else signs. Change settings
- Grow. Add a vault from the market's Overview, then add it to the same product. Create a market or add a vault
- Respond to an emergency. Lower caps or borrow LTVs first. Pause as the last step. Emergency pause
- Wind down. Deprecate the product or its vaults under Labels. They leave the app's tables with your reason. The market itself stays on chain. Labels and metadata
Keep in mind
- A market is on chain; a product is a label. The Toolbox uses your product to know which vaults form your market, so every vault in a market belongs in its product. See Markets and products.
- Nothing is sent until you sign. Staged changes stay in your browser, and the Toolbox reads the chain again right before you're asked to sign.
- A label is not a safety verdict. Euler's assessment of each vault runs on its own and is shown beside it.