You can build your own Baskets or use one from an external Risk Architect.
Key concepts
- One Basket per asset class: If you manage USDC strategies, you have one USDC Basket. ETH and BTC strategies are separate Baskets.
- Baskets define intent, not infrastructure: You specify assets and allocation percentages. Blend handles vault deployment and grouping.
- Account Types link to Baskets: Each product you offer links to exactly one Basket.
Creating a Basket
The admin portal guides you through a 4-step process:Basic details
Provide the Basket name, asset class (e.g., USDC, ETH, BTC), and an optional description.Your Basket starts in
DRAFT status. You can edit it freely until you publish.Select assets
Choose which assets to include from your approved assets.
Set allocations
Assign a target allocation percentage to each asset. Allocations must sum to 100%.
| Asset | Chain | Target Allocation |
|---|---|---|
| Pendle PT thBILL | Arbitrum | 10% |
| Pendle PT sUSDai | Arbitrum | 25% |
| Euler Earn USDC | Arbitrum | 12.5% |
| Morpho Vault A USDC | Arbitrum | 12.5% |
| Morpho Vault B USDC | Arbitrum | 12.5% |
| Aave V3 USDC | Arbitrum | 12.5% |
| Money Market USDC | Arbitrum | 12.5% |
Review and publish
Review the full Basket configuration. Once published:
- Blend validates the configuration (addresses exist in registry, allocations sum to 100%)
- Blend deploys vault infrastructure on the target chain(s)
- The Basket becomes available for your Account Types
After publishing, your Basket is live and you can link Account Types to it.
Basket states
| State | Description |
|---|---|
| DRAFT | Being configured. You can edit asset allocations and settings freely. |
| PUBLISHED | Live and ready for Account Types. Cannot revert to DRAFT. |
Publishing a Basket is permanent. Once published, the Basket is locked and Account Types can link to it. You can still create new versions with updated allocations.
How Blend deploys your Basket
When you publish a Basket, Blend’s infrastructure layer takes over:- Asset grouping: Blend analyzes your selected assets and decides how to group them into Vault V2 contracts for gas efficiency
- Vault V2 deployment: One or more Vault V2 contracts are deployed per chain
- Configuration linking: The Vault V2 addresses are stored and linked to your Basket
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.
Position mapping
When Blend deploys infrastructure for your Basket, each asset maps to a vault position in one of two ways:| Type | How it works | Used for |
|---|---|---|
| Standalone | One asset maps to one vault position | Pendle PTs, cash reserves |
| Composite | Multiple assets share one vault position | Morpho, Euler, Aave markets |
Vault configuration lifecycle
After you publish a Basket, Blend provisions the on-chain vault infrastructure. The configuration moves through these states:| State | Description |
|---|---|
| PENDING | Vault configuration created, waiting for provisioning |
| PROVISIONING | On-chain deployment in progress |
| READY | Deployed, awaiting activation |
| ACTIVE | Live and managing positions |
| CANCELLED | Deployment was cancelled |
Updating a Basket
To modify an existing Basket:- Navigate to the Basket in the admin portal
- Update asset allocations or add/remove assets
- Review and publish the changes
- A new version is recorded in the changelog
- Blend creates flow plans for all affected accounts
Basket versioning
Every Basket has a version number with two parts:| Version part | Increments when |
|---|---|
| Major | You add or remove assets from the Basket |
| Minor | You change allocation weights for existing assets |
Next steps
Account Types
Create products that link to your Baskets.
Flow Plans
Manage rebalancing when positions drift.
Assets
Submit new assets for your Baskets.
Fees
Understand the fee structure.