Creator UI

The Creator UI is a guided interface for deploying and managing EVK vaults. For repeatable clusters, custom governance, or scripted changes, use Deployment and management instead.

Deploy a vault

1. Plan the underlying asset, collateral relationships, oracle routes, unit of account, IRM, caps, LTVs, hooks, and governance.
2. Deploy or select the required oracle router and adapters.
3. Open Creator UI, choose Vault (/vault), select the underlying asset, router, and unit of account, then review the deployment transaction.
4. Open the deployed vault at /manage-vault/$vaultAddress and configure its remaining parameters and roles.
5. Verify every address, parameter, permission, and event from deployed state.

The landing page exposes Vault, Oracle Router, Oracle Adapter, and IRM. Address Book is in the top navigation. Existing routers use /oracle/$routerAddress; IRM deployment uses /configure-irm. Prefer UI navigation over constructing undocumented routes.

Manage an existing vault

The management dashboard groups immutable vault identity, configurable settings, collateral relationships, oracle routes, rewards, and hooks. Before signing a change, review the network, vault, asset, router, unit of account, governor, caps, LTVs, hooks, rewards, metadata, and governance process.

Vault info

This section displays immutable details about the vault, such as the vault symbol, address, underlying asset, oracle router, and unit of account. These parameters are set at creation and cannot be changed later. They provide essential context for the vault's operation and risk profile.

Settings

• Governor: The address with governance rights over the vault. Common practice is to transfer this role to a multisig or governance contract after initial setup. Revoking governance by setting it to address(0) makes the vault immutable; do this only if no further parameter changes should be possible.
• Fee receiver: The address that receives the vault-receiver portion of converted interest-fee shares after the applicable protocol split. This can be a treasury, DAO, curator, or other beneficiary. Review control of this address before launch.
• Interest Rate Model: The contract that supplies the vault's borrow-rate input. Choose a model that matches the risk and utilization profile of your vault.
• Supply Cap / Borrow Cap: These parameters limit the total amount of assets that can be supplied to or borrowed from the vault. Caps can be used to bound exposure while a market is new or changing.
• Interest Fee: The fraction of accrued borrower interest allocated as fee shares. The applicable protocol fee share splits those shares between the vault fee receiver and protocol fee receiver; it is not an additional fee on top. Verify all deployed settings and recipients rather than inferring them from a proposal or global claim.
• Maximum Liquidation Discount: Sets the upper bound on the discount offered to liquidators. Too high a discount can penalize borrowers; too low may fail to incentivize liquidations.
• Liquidation Cool Off Time: The minimum time that must pass after the account's last successful status check before it can be liquidated. It is not measured from when the position first becomes unhealthy. This delay helps mitigate self-liquidation attacks, but setting it too high can delay necessary liquidations.
• Debt Socialization: When enabled, a liquidation can socialize debt that remains after the violator's collateral has been exhausted. This occurs only when debt remains after the liquidation, the account has no collateral left, and the pre-liquidation liability value meets the protocol's minimum threshold. The remaining debt is removed without assets entering the vault, causing a loss to depositors through a reduction in share value.

Supply and borrow caps

Supply and borrow caps are denominated in the vault's underlying asset. The Creator UI handles EVK's compact onchain encoding, but scripts and integrations should use the current AmountCap implementation rather than treating the displayed amount as the raw stored value.

An encoded value of 0 represents an unlimited cap. Use the EVK library when reading or writing caps onchain:

import {AmountCap, AmountCapLib} from "evk/EVault/shared/types/AmountCap.sol";
 
uint256 decoded = AmountCapLib.resolve(AmountCap.wrap(encoded));

Reference: AmountCap.sol

Collaterals

Add Collateral: Here you can configure which other vaults' shares can be used as collateral, and set their Loan-to-Value (LTV) ratios. Review collateral liquidity, volatility, oracle route, governance, caps, and liquidation behavior before adding collateral.

Adding and configuring collateral assets

When you add a new collateral to your vault, the UI will prompt you to set two key risk parameters:

• Liquidation LTV: The collateral-adjustment ratio used for liquidation health. A position becomes eligible when its liability is not less than collateral value after applying the configured liquidation LTV.
• Borrow LTV: The maximum loan-to-value ratio at which new borrowing is permitted. This is typically set lower than the liquidation LTV to provide a safety buffer and reduce the risk of immediate liquidations after borrowing.

Oracle router configuration

When adding a new collateral, the oracle router configured for this vault must be able to price the underlying asset of the collateral vault in terms of the vault's unit of account, such as USD. This is managed through the Set Oracle Configuration option. If the oracle router cannot provide this price, borrowing against the collateral will not be possible.

Choose the route deliberately. A configured direct share-token pair oracle takes precedence and short-circuits resolved-vault routing. Configure that direct route only when it is intended; if the route should call the ERC-4626 vault's convertToAssets() and then price its underlying asset, use Add Resolved Vault to Oracle and ensure no direct pair route overrides it. Review precedence, donation/inflation behavior, decimals, redeemability, liquidity, restrictions, recursive dependencies, and whether the conversion represents realizable value.

See Oracle router deployment for precedence and safety checks. The router must produce the required collateral-share quote for risk checks, LTV calculations, and liquidations; the same two-step path is not mandatory for every collateral.

Oracle configuration

Deploy your own oracle adapters for the routes the vault needs — the Oracle Deployer supports the available adapter types — rather than reusing adapters found onchain. If you do reuse one, verify its configuration and provenance first.

Underlying asset oracle config

The Oracle Config section allows you to configure the oracle for the underlying asset of your vault. The router must be able to price the vault's underlying asset in terms of the unit of account, such as USD. This pricing route is used for risk checks and debt valuation. If the oracle router cannot provide this price, borrowing against collateral in that liability vault will not be possible.

Rewards

Use Merkl for reward campaigns. It supports campaign scheduling, eligibility criteria, and analytics. Review campaign terms and how rewards are displayed before using rewards in public vault materials.

Hook settings

Hook Target & Operations: Install a hook contract to add custom checks or restrictions to selected vault operations. You can selectively enable or disable hooks for operations such as deposit, withdraw, mint, redeem, borrow, repay, transfer, liquidate, and more. Poorly designed hooks can break vault functionality or introduce risk, so custom hooks should be reviewed and tested before use.

Managing existing vaults and escrow

• Manage Existing Vault: Enter a vault address to manage its configuration or view details.
• Deploy/Search Escrow: Escrow Vaults are ungoverned vaults designed to act as simple, reusable collateral buckets (see Vault Types). There's usually no need to create new Escrow Vaults unless you need one for a new asset. Existing Escrow Vaults can be reused by anyone in the ecosystem.