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

Labels and metadata

The euler-labels repository provides human-readable names, descriptions, logos, and product groupings used by Euler applications. This metadata helps users identify entities, products, lending vaults, Earn vaults, points programs, and asset restrictions.

Choose the metadata file

The repository uses these files for each supported chain:

  • entities.json for organization identity and display information;
  • products.json for EVK lending products and per-vault display overrides;
  • points.json for points programs;
  • optional earn-vaults.json for Earn vault discovery; and
  • optional assets.json for chain-specific asset rules.

Cross-chain asset rules can also live in all/assets.json. Lending-vault overrides belong in products.json.vaultOverrides; there is no standalone vaults.json.

Submit metadata

  1. Fork the euler-labels repository.
  2. Read the current README and schemas.
  3. Add or update the relevant files under the numeric chain ID.
  4. Add any referenced logo files.
  5. Run npm run verify against the proposed files.
  6. Open a pull request and resolve verifier and reviewer feedback.

Use checksummed addresses and examples that pass the current verifier.

Add entities and products

Use entities.json for factual information about an organization. Use products.json to group EVK lending vaults and define product-level display metadata.

Markers use the tags schema, for example:

{
  "tags": ["governance limited"]
}

Tags can be set on a product, a vault entry, or in vaultOverrides; other examples in use include "keyring" and "suppress high utilisation warning".

Add Earn vaults

Use earn-vaults.json for Earn discovery and supported entry metadata. Earn vaults are separate from EVK lending-product groupings.

Follow the current repository schema for exact fields and file shape.

Add asset rules

Use chain-specific assets.json for address-scoped rules and all/assets.json for supported cross-chain matches. Exact symbol and name match keys use the arrays symbols and names.

Fields such as block, restricted, labels, and group aliases are metadata consumed by applications. Each integration decides how to apply and update them.

Write descriptions

Keep descriptions factual and maintainable. Identify the object and the party that configures it without implying endorsement. For example:

An EVK lending product for selected assets, configured by Example DAO.

Labels describe the object shown in an interface. Verify onchain role holders, vault configuration, and asset details from the deployed contracts when those facts affect an integration or transaction.

Read next