Renegade

• Name: Renegade
• URL: https://renegade.fi/
• Category: privacy-preserving execution venue / MPC matching network / zk settlement protocol
• Tags: ethereum-ecosystem
• Summary: Renegade is private trading infrastructure, not a generic DEX and not a magic dark pool label. The useful cut is simple: hidden wallet state, relayer-run MPC matching, zero-knowledge settlement, and optional identity gating for counterparties.
• What it does:
  • Lets traders hold balances as commitments and place orders without exposing normal public orderflow before execution
  • Uses relayers and relay clusters to manage private wallet state, replicate encrypted data, and coordinate pairwise MPC matching
  • Settles matches with zero-knowledge proofs so the trade can clear onchain without revealing the full underlying state
  • Uses midpoint-style private matching against offchain reference pricing rather than a transparent order book or public mempool path
  • Supports optional compliance-style identity restriction according to the docs, so privacy and counterparty gating are both part of the design
• Key claims:
  • Official materials present Renegade as a private trading venue with pre-trade and post-trade privacy rather than a standard public DEX
  • The MPC-ZKP architecture docs are the high-signal source: wallet state stays local/private, relayers handle private coordination, and only commitments plus proof-verified settlement touch the chain
  • The whitepaper/docs make the split between onchain settlement and offchain relayer coordination explicit, which is where most of the real control and failure surface lives
  • The current rollout language stays Ethereum-stack local: the homepage says Arbitrum and Base, while parts of the docs still speak in narrower Arbitrum terms
  • The repo surface shows a real protocol stack — relayers, contracts, SDKs, and MPC infrastructure — not just a frontend shell
• 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.
• Sources:
  • https://renegade.fi/
  • https://docs.renegade.fi/
  • https://docs.renegade.fi/core-concepts/mpc-zkp
  • https://docs.renegade.fi/getting-started/whitepaper
  • https://whitepaper.renegade.fi/
  • https://github.com/renegade-fi
  • https://raw.githubusercontent.com/renegade-fi/renegade/main/README.md

Internal linkages

• Strongest privacy-trading and privacy-middleware contrasts: penumbra and railgun.

Control surface

• The leverage sits in relayer admission and cluster design, reference-pricing inputs, identity-gating policy, client defaults, and whatever governance or operator path can change the matching and settlement stack.

• That is why the note should stay on private execution mechanics, not dissolve into vague privacy DEX language.

• Read Renegade as a private execution venue with explicit operator middleware, not as a generic exchange wrapper.

• Last reviewed: 2026-06-18 UTC