Four agents. One consensus gate.
Each agent reasons independently over the same market. A decision executes only when all four agree and the risk layer approves — otherwise nothing fires.
Multi-agent intelligence
Technicals, market structure, liquidity and venue order-book state across monitored assets (BTC, ETH, BNB and others). Produces directional hypotheses with confidence — never orders.
Exposure caps, cross-asset correlation, volatility-scaled sizing, drawdown guards and stop-loss enforcement. Holds veto power over every decision, including consensus-approved ones.
Venue selection, spread and slippage modeling, fill planning and idempotent order submission with reconciliation. Plans fills; never self-authorizes them.
Funding rates, social activity, whale flows and market mood as an independent contrarian check on technical signals.
System layers
LONG, SHORT or PASS per agent with confidence. Execution requires agreement across all four — disagreement means no trade. Decisions are typed records (agent, decision, confidence), not vibes.
Approved decisions flow to risk validation, balance checks and the execution engine. Every order is reconciled against exchange state; frontend requests can never execute orders directly.
Position limits, volatility scaling, correlation monitoring and drawdown guards gate sizing continuously — including shrinking or halting deployment during losing periods.
Positions, P&L, settlements and protocol activity surface on the dashboard and protocol statistics from recorded data. Losses are shown, not hidden.
Deployment confirmation re-quotes server-side; rates snapshot per deployment and per referral reward so history never re-prices. Statistics pages show audited snapshots or honest empty states.
Supabase Auth with email verification, HTTP-only cookie sessions, auth.uid()-scoped row-level security on all private tables, and security headers. Full honest accounting on the Security page.
Next.js on Cloudflare Workers via OpenNext, Supabase Postgres/Auth/Realtime as the data plane, Resend for email. No second database, no duplicated financial state.
No external security audit, no certifications, no TOTP two-factor yet, no guaranteed yields. The Security page lists exactly what is implemented versus planned.
Read the protocol overview
The Protocol page walks through convergence architecture stage by stage.