At a glance
How each protocol is structured
XOXNO uses one central liquidity pool for every listed asset. Your wallet owns a lending account that holds all your supplies and borrows. You interact through XOXNO. Designated role holders can update risk settings on a delay. Pausing is immediate; unpausing is not — it waits out the full timelock like any other change. Blend is built around isolated pools. Anyone can deploy a pool with its own assets, oracle, and risk parameters. Positions in one pool do not affect another. Each pool has a backstop module that earns part of borrower interest and is designed to absorb bad debt before lenders in that pool take a loss. Blend also supports non-collateral supply: you can lend assets without posting collateral on the same account. On XOXNO, supplied assets count as collateral unless you withdraw them.Risk and liquidations
XOXNO checks two things on your whole account: a borrowing limit (LTV) when you borrow or withdraw, and a health factor that decides if you can be liquidated. Below 1 is liquidatable. Blend tracks borrow capacity per pool using collateral and liability factors. Liquidations use a Dutch auction rather than a fixed bonus. Bad debt hits the pool backstop first, then may be shared among lenders in that pool. Oracles: XOXNO uses Reflector and RedStone, usually two sources whose midpoint becomes the price. If they disagree too much, or either is stale, XOXNO refuses to price the asset and the action reverts — for every action that needs a price, not just risky ones. Blend lets each pool creator pick an oracle at deployment. Neither model guarantees price correctness.Migrating from Blend to XOXNO
XOXNO offers a one-transaction migration from approved Blend pools. In a single step it may repay your Blend debt, withdraw your collateral, and open a corresponding XOXNO position, subject to health and borrowing checks. If anything fails, the whole transaction rolls back. Non-collateral Blend supply has no direct counterpart on XOXNO and is deposited as collateral during migration. See the Blend migration guide for the user walkthrough.How the designs differ
Blend-oriented design traits
- Isolated pools with custom assets, oracle, and risk settings per deployment
- Permissionless pool creation without a protocol-wide admin delay for new listings
- Receipt tokens (bTokens) you can hold, transfer, or plug into other integrations
- Backstop module funded by BLND:USDC deposits (not an insurance policy)
- Non-collateral supply (lend without posting collateral on the same account)
- Existing pool parameters, backstop depth, and rewards that fit a given use case
XOXNO-oriented design traits
- Shared liquidity across listed assets instead of fragmented pools
- Admin controls with a timelock before many risk or oracle changes go live
- Account balances without separate supply or debt tokens
- Cross-asset positions: borrow and supply multiple assets from one account, with spoke-based risk configuration
- Migration path from approved Blend pools in a single atomic transaction
- XOXNO strategies (multiply, swap debt or collateral, repay with collateral)
Migration notes
Shared liquidity, risk parameters, or the migration path may or may not fit a given Blend position. Isolated pools, receipt tokens, backstop economics, or an existing pool’s emissions may be the main draw for staying on Blend. This is descriptive, not advice. Positions do not migrate automatically. You start migration explicitly or exit Blend on your own.Related docs
Blend migration
User guide for moving a Blend position to XOXNO.
Accounts and risk
How your XOXNO account works after migration.
Health factor
Reading health factor after you migrate.
Overview
What XOXNO does and how it works.