Label file format (forks)
Euler curators do not use these files. Labels are set in the Toolbox and published through the Euler Data API (Labels and metadata). A fork of the Euler app can instead read labels from static files in this format, with no label service.
Files
One directory per chain, named by chain ID:
| File | Holds |
|---|---|
entities.json | Organisations: name, description, links, logo, on-chain addresses |
products.json | EVK products, their vaults, per-vault overrides under vaultOverrides (no standalone vaults.json) |
points.json | Points programmes |
earn-vaults.json (optional) | Earn vault discovery and entry metadata. Separate from products. |
assets.json (optional) | Chain-specific asset rules by address. Cross-chain rules go in all/assets.json, matched by symbols and names. |
Tags
On a product, a vault, or in vaultOverrides:
{ "tags": ["governance limited"] }Also in use: "keyring", "suppress high utilisation warning".
Asset rules
block, restricted, labels and group aliases are applied by the app at display time. Each fork decides how.
Descriptions
Keep descriptions factual, with no endorsement: An EVK lending product for selected assets, configured by Example DAO. Labels describe what an interface shows. Verify roles and configuration on chain.