Category: privacy-preserving trading infrastructure / onchain dark pool / MPC-based order-matching network / zero-knowledge settlement protocol
Summary: Renegade is a privacy-first trading protocol that combines local private wallet state, peer-to-peer relayers, multi-party-computation order matching, and zero-knowledge settlement. Its current primary-source surface jointly exposes midpoint-pegged private matching, relayer-cluster architecture, commit-reveal wallet privacy, optional compliance gating, and open-source cryptographic/networking code, so it is better cataloged as privacy-preserving execution infrastructure rather than as a generic DEX or “dark pool” marketing label.
What it does:
Lets traders place private orders whose details are not publicly visible before execution, with wallets and balances represented onchain as commitments rather than plaintext state
Uses relayers and relay clusters to manage wallet state privately, gossip encrypted order state, and perform pairwise MPC matching across the network
Settles successful matches with zero-knowledge proofs so validators and other third parties do not learn the underlying trade details
Targets midpoint execution and zero-MEV-style privacy guarantees by matching against real-time offchain reference pricing rather than exposing public orderflow to a transparent mempool/order book
Supports optional identity-restricted matching according to official materials, positioning the network as a privacy-preserving but compliance-aware trading venue
Key claims:
The homepage frames Renegade as “Crypto’s First Dark Pool,” says it offers “zero price impact,” “zero MEV,” confidential indications of interest, and opt-in compliance, and says the product is live on Arbitrum and Base
The docs introduction says Renegade is an “on-chain dark pool” where balances and trade history are hidden from third parties, with midpoint execution, pre-trade privacy, post-trade privacy, and optional identity-based counterparty restriction
The MPC-ZKP architecture docs are especially high-signal because they explain that wallet state is kept locally, only commitments are posted onchain, relayers perform private MPC matching, and clusters provide replication/failover while preserving trader privacy
The whitepaper page says the protocol has a precise specification covering onchain and offchain state, the full trade lifecycle, and the NP statements proven within the protocol
The GitHub org and core README show Renegade maintaining not just a frontend but a deeper protocol stack spanning relayers, contracts, SDKs, docs, token mappings, and MPC infrastructure
One useful research note is that the homepage and docs are not perfectly synchronized on network rollout language: the homepage says Arbitrum and Base, while the docs introduction still says live on Arbitrum
Whitepaper: Official whitepaper exists and is linked from the docs at https://whitepaper.renegade.fi/; current primary-source notes are saved locally in ../whitepapers/renegade-primary-sources-2026-04-28.md.