Performances
RD Popularity Index
RD Growth Index
Comparison
Team
Follow Updates
Follow Lists
People
About Renegade
Renegade is an on-chain dark pool built on zero-knowledge proofs and multi-party computation (MPC). Unlike traditional DEXs where all orders are publicly visible, Renegade keeps order books encrypted. Order matching happens off-chain through a peer-to-peer network of relayers using MPC, while settlement occurs on-chain via zero-knowledge proofs. Prices are pegged to the Binance midpoint, aiming for best execution.
Its core value proposition is privacy: no third party—including block proposers—can see pending orders, balances, or trade history. This directly addresses the pain points of large traders: front-running, MEV extraction, slippage on big orders, and address discrimination. By hiding order details until settlement, Renegade reduces market impact and prevents copy-trading.
The target users are institutional traders, market makers, solvers, and vault managers who need to move large sizes without leaking information. The protocol is live on Arbitrum and Base, with plans for Ethereum mainnet.
Regarding development in the past six months (2026-03-03 to 2026-09-03), no reliable public information is available. The whitepaper and docs describe the architecture but do not provide a timeline of recent updates. No major negative events were found in the available sources.
Over the past six months (2026-03-02 to 2026-09-02), Renegade's most significant development was a security incident on May 10, 2026. A white-hat hacker exploited an unprotected initializer in the V1 dark pool proxy contract on Arbitrum, draining approximately $209,000 across 27 ERC-20 tokens. The vulnerability stemmed from a faulty migration during an April 2025 software update that left the contract owner unassigned. Within 45 minutes of Renegade's on-chain message offering a 10% bounty and threatening legal action, the hacker returned over 90% of the funds (~$190,000). Renegade confirmed only ~7% of trading volume ran through the affected V1 Arbitrum pool, committed to fully compensating affected users, and stated other deployments (V1 Base, V2 Arbitrum/Base) remained unaffected. The protocol promised a full post-mortem with root-cause analysis. No official roadmap or future development priorities were published during this period beyond the incident response and continued operation of V2.
Christopher Bender (Co-founder) - UC Berkeley pure math & CS background; ex-Tesla Autopilot, Nuro, and ML at Berkeley president; authored ICLR/ICML papers.
Joseph Kraut (Co-founder) - UC Berkeley CS; ex-Renegade core contributor, focus on ZK/MPC.
Maryam Beria (COO) - ex-COO at Renegade; prior roles at Euler Labs (Head of Strategy & Ops), Ridgeline (Product Manager), BlackRock (Portfolio Manager).
Renegade (zk dark pool protocol) recently saw a key team change: Maryam Beria officially joined in May 2026 as Chief Operating Officer (COO). She previously served as Head of Strategy & Operations at Euler Labs and Senior Product Manager at Ridgeline, bringing extensive experience in DeFi and traditional finance. This appointment is expected to accelerate Renegade's growth in dark pool trading, privacy protection, and market expansion.