Block Helix
|
Non-custodial ERC-4626 vaults on Base. Any program — quant script, webhook, AI agent — can run an on-chain fund through a REST API, bounded by merkle-authorized policies depositors can read.
Three steps
Pick. Fund.
Trade.
Your vault is a non-custodial ERC-4626 contract on Base. The operator trades through an API but can only execute what the policy allows. Depositors stay in control.
How it works
Pick a policy template
Bluechip, All Yield, Balanced, Momentum. The merkle root is set in the creation transaction. Takes 60 seconds.
Depositors fund the vault
USDC in, ERC-4626 shares out. The operator never holds funds — capital lives in the contract, bounded by the policy.
Trade through the API
One REST call per action. The executor verifies every trade against the policy on-chain — no leaf, no trade.
What the policy guarantees
Bounded execution
Token pairs, venues, slippage, and per-tx caps are merkle-leaf constraints, enforced by the contract — not promises.
24h warning on changes
Policy changes go through a timelock. Depositors see the exact diff and can exit before it activates.
Withdrawals never gated
Exit paths are guaranteed by construction — every position the policy can open, it can unwind.
The insight
Trust the policy,
not the manager.
Every on-chain fund asks you to trust a human. We replaced that with a machine-checkable policy: a merkle tree of exactly what the operator may do, enforced by the contract on every trade.
Leaves, not vibes
The vault's policy IS the strategy boundary. The operator literally can't trade outside it. Every action goes through quote → simulate → prove → execute.
The trust stack
- 1. Vault launches with a known policy template.
- 2. Every trade needs a merkle proof on-chain.
- 3. Policy changes wait 24h in a timelock.
- 4. Depositors see the diff, exit if they want.
- 5. Settle → logged, indexed, auditable.
Without vs with BlockHelix
Wire money to a fund manager
Non-custodial vault, your shares
Strategy changes behind your back
24h timelock + human-readable diff
No idea what the fund actually holds
Live positions + NAV, on-chain
Under the hood
Built on rails
DeFi already trusts.
Base for settlement. ERC-4626 for vault accounting. CoW Protocol for MEV-protected execution. No new standards to learn — if your program speaks HTTP, it can run a fund.
Vault
Standard ERC-4626 over USDC. Deposit, get shares, withdraw any time. Synchronous exits served from an enforced idle buffer.
Policy
A merkle root of authorized actions — pairs, venues, slippage, caps. Updatable only through a 24h timelock depositors can see.
API
POST /trade/swap from any program. MCP tools for AI agents. Wallet signature auth — no signup.
Policy templates
Pick a risk profile.
We maintain the tree.
Nobody hand-builds merkle trees. Operators choose a curated template; we version the leaf sets and publish vetted updates they can adopt through the timelock.
Bluechip
USDC ↔ WETH/cbBTC on top-liquidity pools only. Slippage capped at 50 bps per trade.
All Yield
Morpho, Aave v3, and Moonwell whitelisted markets. No directional swaps.
Balanced
Bluechip pairs plus yield sources, with per-transaction notional caps.
Midcap Momentum
Curated, liquidity-screened midcap list. Tighter caps, wider slippage band.
Perps Midcap
Midcap perp markets, max 3× leverage, mandatory exit leaves. Ships in v2.
Custom
Propose your own leaf set post-launch. Validated by the config service, activated via timelock.
3rd place ($15k) at the Colosseum Solana Agent Hackathon out of 454 projects. Now building on Base.
READ THE API DRAFT→Pre-launch · Base mainnet beta
Get early access.
Guarded launch: $25k TVL cap per vault, allowlisted operators, protocol guardian active. Audit before real TVL.
Legacy Solana devnet runtime is frozen — existing vaults are archived.