Skip to main content
Blend is modular, non-custodial DeFi infrastructure. Wallets, fintechs, and neobanks integrate Blend to offer competitive, risk-managed DeFi products to their users without taking on custodial risk or operational complexity.

Why Integrate Blend?

SMA model, not pooled vaults

Unlike vault-based yield products, Blend gives every end user their own isolated Gnosis Safe. This means:
  • No custodial risk for your platform: you never hold user funds
  • No shared pool risk: one user’s issue cannot affect others
  • Regulatory clarity: self-custodial architecture simplifies compliance

Structured products, not just APY

Because each user has their own Safe, Blend can offer more than simple lending. Through Risk Architect Baskets, your users get access to:
  • Delta-neutral strategies
  • Basis trades
  • Bitcoin+ products
  • FX structured products
  • Customized risk/return profiles per product

Everything you need to build

Architecture Overview

Blend’s integration model has four key entities:
EntityWhat it isWho manages it
Risk ArchitectOrganization of investment experts that create strategies (Baskets). Known as a curator/risk manager in Morpho and traditional vault models.Risk Architect organization
BasketA strategy template defining asset allocations and target percentagesRisk Architect (via admin portal)
Account TypeA product offering you create (e.g., “Savings”, “Growth”, “BTC Yield”) linked to one BasketYou (the integrating neobank)
AccountAn end user’s account that maps 1:1 to an on-chain Gnosis SafeCreated by you when a user signs up

The flow

  1. Risk Architects create Baskets with specific strategies
  2. You create Account Types for your products, each linked to a Risk Architect Basket
  3. Your users open accounts. Blend deploys a personal Safe for each user, deterministically derived from your neobank ID + account type + user address
  4. Users deposit and their capital is managed according to the Basket’s strategy in their isolated Safe
The same user can have multiple Safes within your platform, one per Account Type. For example, a user could have both a “Savings” account (conservative Basket) and a “Growth” account (aggressive Basket).

Dynamic Safe Resolution

Each user’s Safe address is deterministically computed:
saltNonce = keccak256(BLEND_SALT_NONCE + neobankId + accountTypeId)
safeAddress = CREATE2(userAddress, saltNonce)
This means:
  • Predictable: You can compute the Safe address before deployment
  • Collision-free: Different neobanks and account types always produce unique addresses
  • Multi-account: Same user, multiple products, each with their own isolated Safe
  • Cross-chain consistent: Same Safe address on every supported chain

Integration Example

import { BlendClientWithActions } from "@blend-money/sdk-actions";
import { Integrations } from "@blend-money/sdk-types";

// Initialize with your integrator ID
const client = new BlendClientWithActions({
  baseUrl: "https://api.blend.money",
  userAddress: userWalletAddress,
  integratorId: "your-neobank-v1.0",
}, { gardenAppId: "YOUR_GARDEN_APP_ID" });

// Get available strategies
const strategies = await client.strategy.getAvailableStrategies(Integrations.USX);

// Create a deposit plan
const plan = await client.actions.deposit(
  { address: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", symbol: "USDC", decimals: 6, chainId: 8453 },
  strategies[0],
  1_000_000n, // 1 USDC
  50, // 0.5% slippage
);

console.log("Required approvals:", plan.requiredApprovals.length);
console.log("Required transactions:", plan.requiredTxns.length);

Who Can Integrate

Blend is designed for:

Wallets

Add a native “Earn” feature. Users keep self-custody in their own Safes while accessing DeFi strategies.

Fintechs & Neobanks

Offer competitive DeFi products without building or managing infrastructure.

DAOs & Treasuries

Deploy treasury assets into conservative, liquid strategies with Gnosis Safe multi-sig support.

L1/L2 Ecosystems

Drive sticky liquidity to your chain by offering best-in-class, cross-chain DeFi opportunities.

Next Steps

Last modified on February 6, 2026