Skip to main content
COMING SOON The asset registry (@blend/assets) is a public GitHub repository that serves as the single source of truth for all DeFi asset metadata in Blend. It follows a community-driven model similar to DeFi Llama: anyone can submit new assets via pull request.

What the Registry Contains

Each asset entry in the registry includes:
FieldDescription
addressThe on-chain contract address of the asset
chainIdThe chain where the asset is deployed
nameHuman-readable name (e.g., “Euler Earn USDC”)
categoryProtocol category (EULER, AAVE, PENDLE, MORPHO, etc.)
priceComponentsHow to price this asset (Chainlink feeds, ERC-4626 share price, etc.)
yieldComponentsWhere yield comes from (protocol-specific yield sources)
hrefLink to the protocol’s UI for this asset

Example Asset Definition

# assets/arbitrum/euler-earn-usdc.yaml
address: "0xe4783824593a50Bfe9dc873204CEc171ebC62dE0"
chainId: 42161
name: "Euler Earn USDC"
category: "EULER"
href: "https://app.euler.finance/earn/0xe478..."
priceComponents:
  - type: chainlink
    feed: "0x50834F..."
  - type: erc4626
    vault: "0xe478..."
yieldComponents:
  - - type: euler-earn
      vault: "0xe478..."

What the Registry Does NOT Contain

The registry is strictly for underlying asset definitions. It does not contain:
  • Vault V2 infrastructure (addresses, leverage settings, collateral configs) - that lives in Blend’s database
  • Risk Architect allocations or strategy configurations - those are in the Basket’s config
  • Deployment or operational configuration
This separation is intentional. See The Three-Layer Model for how these pieces fit together.

Submitting a New Asset

1

Check if the asset exists

Search the @blend/assets repository to see if the asset is already registered. Assets are organized by chain (e.g., assets/arbitrum/, assets/base/).
2

Create the asset definition

Create a new YAML file following the naming convention: assets/{chain}/{protocol}-{asset}.yaml.Include all required fields: address, chainId, name, category, priceComponents, and yieldComponents.
3

Submit a pull request

Open a PR against the @blend/assets repository with your new asset definition. Include:
  • A description of the asset and its protocol
  • Links to the protocol documentation
  • Any relevant audit reports
4

Review and merge

The Blend team reviews the PR to verify:
  • Contract address is correct and verified on the block explorer
  • Price components are accurate and reliable
  • Yield components correctly describe the yield source
  • The protocol has been audited
Once merged, the asset becomes available for Risk Architects to include in their Baskets.
If you are a Risk Architect and need a specific asset for your Basket, submit the PR yourself or request it in the Blend Discord. The Blend team can also help prepare asset definitions for complex protocols.

Supported Asset Categories

CategoryExamples
MORPHOMorpho Blue markets, Morpho Vault V2 positions
AAVEAave V3 supply positions
EULEREuler vaults, Euler Earn aggregated positions
PENDLEPendle Principal Tokens (PTs) with various maturities
ERC4626Any tokenized vault following the ERC-4626 standard
SPOTSpot assets with price feeds
RECEIPTProtocol receipt tokens (staking, restaking)
Last modified on February 6, 2026