Skip to main content
COMING SOON A Basket is a Risk Architect-created investment strategy that defines how user capital is allocated across yield opportunities. Each Basket maps to one or more Vault V2 deployments on-chain.

​
Key Concepts

  • One Basket per asset class per Risk Architect: If you manage USDC strategies, you have one USDC Basket. If you also manage ETH strategies, that is a separate Basket.
  • Baskets define intent, not infrastructure: You specify assets and allocation percentages. Blend handles the Vault V2 deployment and grouping.
  • Neobanks select Baskets: When a neobank creates a product (Account Type), they link it to one of your Baskets.

​
Creating a Basket

The admin portal guides you through a 4-step process:
1

Basic details

Provide the Basket name, asset class (e.g., USDC, ETH, BTC), and an optional description.
Name: "USDC Conservative"
Symbol: USDC
Description: "Low-risk stablecoin strategy targeting 8-12% APY via
diversified money markets and short-duration Pendle PTs."
2

Select assets

Choose which assets to include from the asset registry. Each asset has a verified address, chain ID, and metadata (name, category, price feeds, yield sources).
Only assets registered in @blend/assets can be included in a Basket. If you need a new asset, submit a PR to add it to the registry.
3

Set allocations

Assign a target allocation percentage to each asset. Allocations must sum to 100%.
AssetChainTarget Allocation
Pendle PT thBILLArbitrum10%
Pendle PT sUSDaiArbitrum25%
Euler Earn USDCArbitrum12.5%
Steakhouse USDCArbitrum12.5%
Gauntlet USDCArbitrum12.5%
Aave V3 USDCArbitrum12.5%
Clearstar USDCArbitrum12.5%
Allocation changes trigger rebalance requests for all accounts using this Basket. Consider the impact before adjusting weights.
4

Review and publish

Review the full Basket configuration. Once published:
  1. Blend validates the configuration (addresses exist in registry, allocations sum to 100%)
  2. Blend deploys Vault V2 infrastructure on the target chain(s)
  3. The Basket becomes available for neobanks to select
After deployment, your Basket is live and neobanks can begin linking Account Types to it.

​
How Blend Deploys Your Basket

When you publish a Basket, Blend’s infrastructure layer takes over:
  1. Asset grouping: Blend analyzes your selected assets and decides how to group them into Vault V2 contracts for gas efficiency
  2. Vault V2 deployment: One or more Vault V2 contracts are deployed per chain (~$1 deployment cost per chain)
  3. Configuration linking: The Vault V2 addresses are stored and linked to your Basket
For example, a 7-asset Basket might be deployed as: 
Vault V2 #1: wraps Pendle PT thBILL (single asset, 10%)
Vault V2 #2: wraps Pendle PT sUSDai (single asset, 25%)
Vault V2 #3: wraps 5 money markets (multi-asset, 62.5%)
You do not control how assets are grouped into Vault V2s. Blend optimizes this for gas efficiency and risk management. You only control which assets and what percentages.

​
Updating a Basket

To modify an existing Basket:
  1. Navigate to the Basket in the admin portal
  2. Update asset allocations or add/remove assets
  3. Review and publish the changes
  4. Blend will generate rebalance requests for all affected accounts
Allocation changes affect all neobank Account Types linked to your Basket. Rebalance requests will be created for every user account in those Account Types.

​
Basket States

StateDescription
ActiveAvailable for neobanks to select. User accounts are actively managed.
InactivePaused. No new Account Types can be linked. Existing accounts continue to hold positions but no new rebalances are triggered.

​
Next Steps

Rebalancing

How to manage the rebalance queue for your Baskets.

Asset Registry

How to submit new assets to the @blend/assets registry.

Fees

Understand the per-rebalance fee structure.

Monitoring

Track TVL, integrations, and performance.
Last modified on February 6, 2026