Roadmap

This is a plan, not a prediction.

Gates are binary conditions. Dates are targets that move when conditions say so.

← Back to home

Phases

Phase 0 — Foundation + Vault Build · Active

Target window: Q2 2026

  • ☑ Bot operating on AWS infrastructure (HL Main + Hibachi accounts)
  • ☑ ERC4626 vault v4.1 deployed on HyperEVM (proxy 0xe67c82…ED75)
  • ☐ v5 redeploy with corrected admin architecture, ERC-7540 compliance, fee governance caps, slippage overloads
  • ☐ Self-audit v2.0 clean (SEC-004 v2.0, commit e923006 — see /audit/)
  • ☑ STRAT-001 strategy overview approved
  • ☑ Strategy v2 live in vault with operator capital

Phase 1 — Growth · Planned

Target window: Q3 2026 – Q1 2027

  • 3+ months on-chain track record in the vault (Strategy v2)
  • Safe multisig 2-of-3 active as admin (replaces solo HW wallet)
  • Legal entity constituted (progression: SL → BVI Foundation → Cayman)
  • TVL cap set to $500K with public disclaimer
  • L2 formal third-party audit completes during this phase (target 2027-Q1; may move earlier if revenue or grant covers it sooner)
  • Incident disclosure playbook (OPS-012) active

Phase 2 — Scale · Planned

Target window: Q1 2027 – Q3 2027

  • $1M+ TVL sustained
  • Full legal structure (BVI Foundation + Cayman SubCo or equivalent)
  • Composability integrations active (Morpho MetaMorpho curator-style partnerships, Aave/Fluid collateral listings where applicable)
  • Multi-denomination active (BTC / EUR / HYPE / USDH sub-funds)
  • Periodic re-audit protocol in place post-upgrade

Phase 3 — Institutional · Planned

Target window: Q3 2027+

  • $2M+ AUM
  • Regulated fund structure if applicable (BVI SIBA or Cayman mutual fund license)
  • Institutional risk mandates (benchmark tracking, constraints)
  • Multi-chain evaluation: yield exposure to other chains (e.g. JLP on Solana), not vault core migration — HyperEVM remains the vault's home

Active initiatives (Phase 0)

Current focus of the team, in no particular order:

Pivots registered

When the plan changes, we publish why. Every pivot that affects what users see is recorded here.