Skip to main content
An end user’s account deployed by a neobank. Maps 1:1 to a Gnosis Safe on-chain. The Safe address is deterministically derived from the neobank ID, Account Type, and user wallet address.
A product offering created by a neobank (e.g., “Savings”, “Growth”, “BTC+”). Each Account Type is linked to exactly one Basket, which defines the strategy for all accounts under that type.
A set of HTTP endpoints exposed by Blend for querying vault data, strategies, TVL, and Safe operations. See the API reference for the interactive playground.
The system that manages all DeFi asset metadata in Blend. Neobanks and Risk Architects submit assets through the admin portal. Each asset goes through a review pipeline: PENDING, APPROVED, REJECTED, or ARCHIVED. Only approved assets can be used in Baskets.
A strategy template stored in the database. Created by neobanks or Risk Architects. Contains asset addresses, chain IDs, and target allocation percentages. Maps to one or more Vault V2 deployments on-chain. Starts in DRAFT state, then moves to PUBLISHED. Versioned with major/minor numbers and a full changelog. One Basket per asset class.
A standalone strategy provider that creates and publishes Baskets for neobanks to use. Risk Architects specialize in DeFi strategy and offer their expertise across multiple neobanks without operating a consumer app. In Morpho and other vault-based protocols, this role is called a “curator” or “risk manager.”
A strategy that aims for near-zero exposure to price movements of an underlying asset. Blend uses flash loans to create leveraged delta-neutral positions that capture yield spreads.
A standard for tokenized vaults that represent shares of a single underlying ERC-20 asset, providing a unified API for token vaults.
An uncollateralized loan that is taken out and paid back within the same blockchain transaction. Used in strategies to create leveraged positions safely - the entire transaction reverts if any step fails.
A signed, user-defined preference (e.g., risk profile) that guides automation.
The core automation component of Blend that orchestrates capital deployment and rebalancing based on user intents and market conditions.
A smart contract or algorithm that determines the interest rates for borrowing and lending in a DeFi protocol, typically based on utilization.
A token that represents a user’s staked assets in a proof-of-stake network (e.g., stETH). It allows users to gain liquidity on their staked funds.
The ratio of a loan to the value of the collateral securing it.
A DeFi protocol that enhances interest rates on other lending protocols like Aave or Compound. Blend integrates with Morpho for its delta-neutral strategies.
An organization (fintech, wallet provider) that integrates with Blend to offer DeFi products to their end users. Creates assets, Baskets, Account Types, and manages flow plans. Can build their own strategies or use ones from external Risk Architects. Also referred to as an “integrating product” or “integration partner.”
Users retain full control over their private keys and, therefore, their assets. Blend does not take custody of user funds.
A machine-readable specification used to document Blend’s REST API and power the interactive playground in the docs.
A user with administrative access to a Risk Architect or neobank organization. Roles: Owner (full control), Admin (manage resources), Member (read-only analytics).
A smart contract that pays for transaction gas fees on behalf of users, abstracting away the need for users to hold the native network token.
The process of transferring an asset from one blockchain (like Bitcoin) to a sidechain or layer-2 network (like Botanix).
A point-in-time record of how far each position has drifted from its target allocation. Included in every flow plan so the neobank can see the deviation before approving.
Created when a user’s positions drift from the target allocations defined by their Basket. Neobanks review and approve flow plans for their Account Types. States: PENDING_APPROVAL, QUEUED, SOLVING, EXECUTING, SETTLED, FAILED, CANCELLED. See Flow Plans.
A Gnosis Safe smart contract account that holds a user’s funds. In Blend, each user gets their own personal Safe where they are the sole signer. This is the foundation of Blend’s SMA (Separately Managed Account) model.
A deterministic value computed from keccak256(BLEND_SALT_NONCE + neobankId + accountTypeId) used to derive unique, predictable Safe addresses. Enables multi-account support where the same user can have separate Safes for different products.
Blend’s architecture where each user has their own isolated position (Gnosis Safe) rather than sharing a pooled vault. Enables individualized strategies, precise risk/return profiles, and per-user risk isolation.
Controls what data a neobank’s Account Type receives from its linked Basket. Three tiers: NONE (basic access), ALLOCATION_ONLY (see target allocations), FULL (full position data, returns, and yield breakdown).
The architecture separating Blend’s strategy configuration into three layers: (1) Strategy Intent (asset allocations via admin portal), (2) Asset Registry (asset metadata managed through the portal with a review pipeline), and (3) Blend Infrastructure (Vault V2 deployments). Neobanks interact with Layer 1 and Layer 2.
An individual asset movement within a flow plan. Contains source chain, destination chain, token address, and amount. A single flow plan can have multiple transfer nodes.
The total dollar value of assets deposited across strategies or integrations. Available via vault/tvl API endpoints.
Market conditions driven by MEV or manipulation that increase the risk of adverse selection, unstable borrow curves, or outsized price impact.
The amount of digital currency remaining after a cryptocurrency transaction completes. Blend’s indexer monitors for these on the Bitcoin network.
The on-chain deployment configuration for a Basket’s vault infrastructure. Moves through states: PENDING, PROVISIONING, READY, ACTIVE, CANCELLED. Managed by Blend operations staff.
The on-chain smart contract wrapper that Blend deploys to manage assets for a Basket. Some Vault V2s wrap a single asset (standalone positions); others wrap multiple assets for gas efficiency (composite positions). Risk Architects do not interact with Vault V2s directly.
What Blend is. Unlike a yield aggregator that routes money to the highest APY, a Yield Coordination Engine deploys isolated Safes per user and runs strategies individually. It coordinates across protocols rather than simply aggregating yield sources.
A Gnosis Safe module that enables fine-grained, role-based permissioning for what actions a delegated address (like Blend’s automation) can perform.
Last modified on March 20, 2026