Cowrie Research

renegade-primary-sources-2026-04-28

4 min read

Renegade primary-source snapshot

Fetched: 2026-04-28 UTC

1) Official homepage

Source: https://renegade.fi/

Selected excerpts from the official site:

Crypto’s First Dark Pool

Trade any token in size with zero price impact with crypto’s first decentralized crossing network. Live today on Arbitrum and Base.

Renegade is an on-chain dark pool, a new type of decentralized exchange, bringing hidden-size midpoint-pegs to DeFi.

Additional signals from the source:

  • The homepage is unusually clear that Renegade wants to be understood as private execution infrastructure, not just another swap UI
  • The midpoint-pegged and “decentralized crossing network” language is a strong clue that the protocol sits closer to dark-pool / crossing-network market structure than to typical AMM framing

2) Docs introduction

Source: https://docs.renegade.fi/

Selected excerpts from the official docs:

Renegade is a new type of decentralized exchange, an on-chain dark pool, live on Arbitrum.

Current DEXes are completely transparent: Anyone can see your balances and trade history. In contrast, Renegade gives you universal trade privacy.

Midpoint execution. All trades clear at the real-time Binance midpoint price.

Zero MEV. Since validators only ever see zero-knowledge proofs of valid trades, there is no ability for block producers to front-run, back-run, or sandwich your trades.

Additional signals from the source:

  • The docs make privacy, midpoint execution, and zero-MEV properties first-class architecture goals rather than secondary product copy
  • This page is also a useful reminder that the docs and homepage are slightly out of sync on rollout language: docs say live on Arbitrum, homepage says live on Arbitrum and Base

3) MPC-ZKP architecture docs

Source: https://docs.renegade.fi/core-concepts/mpc-zkp

Selected excerpts from the official docs:

The core difference between Renegade and all other exchanges (both centralized and decentralized) is that state is kept locally.

A wallet is a list of orders and balances for a trader. Each trader’s wallet is kept private to each trader, and only wallet hashes … are posted on-chain.

A relayer is a node in the Renegade network.

A cluster … is a logical group of relayers that all manage the same wallets.

Additional signals from the source:

  • This page is the clearest high-level architecture source because it explains the private-state model, relayer roles, cluster replication, and commit-reveal design
  • Renegade appears to be preserving privacy by making local state and collaborative proof systems the center of the protocol, not just by obscuring a frontend or mempool path

4) Whitepaper landing page in docs

Source: https://docs.renegade.fi/getting-started/whitepaper

Selected excerpts from the official docs:

The whitepaper is the best resource to learn the technical details.

It includes a precise specification of all state (both on-chain and off-chain), a full walkthrough of the trade lifecycle from wallet creation to match settlement, and formalizations of all NP statements that are proven within the protocol.

Additional signals from the source:

  • This is the clearest official confirmation that Renegade maintains a formal technical whitepaper rather than only product/docs material
  • The linked whitepaper should matter for deeper future research because the docs point to it for protocol precision rather than to the homepage or repos

5) GitHub organization

Source: https://github.com/renegade-fi

Selected excerpts/signals from the public org page:

The on-chain dark pool.

On-chain dark pool. MPC for anonymous crosses at midpoint prices.

Solidity implementation of the Renegade darkpool

A framework for SPDZ-style maliciously-secure MPC.

Additional signals from the source:

  • The org inventory shows Renegade publishing far more than a trading interface: contracts, relayers, docs, SDKs, relayer extensions, and MPC tooling are all visible
  • The public repo structure reinforces that this is protocol and cryptographic infrastructure, not only a branded app

6) Core relayer README

Source: https://raw.githubusercontent.com/renegade-fi/renegade/main/README.md

Selected excerpts from the official repo:

Renegade is an on-chain dark pool, an MPC-based DEX for anonymous crosses at midpoint prices.

This repository contains the core networking and cryptographic logic for each relayer node in the Renegade p2p network.

Relayers gossip about encrypted order state, and perform 2-party MPCs to run CLOB matching engine execution.

By proving VALID MATCH MPC inside of a MPC, Renegade maintains complete privacy, both pre- and post-trade.

Additional signals from the source:

  • The README is especially high-signal because it makes clear that relayer behavior, encrypted order gossip, and collaborative proving are the heart of the system
  • The fail-stop cluster note is useful because it reveals a more nuanced trust/replication model than the homepage alone communicates

Notes

  • Renegade appears best cataloged as privacy-preserving trading infrastructure / onchain dark pool / MPC-based order-matching network / zero-knowledge settlement protocol.
  • Official whitepaper exists at https://whitepaper.renegade.fi/, though this fetch pass captured the docs landing page more cleanly than the PDF itself.
  • The most useful triangulation clue is that homepage, docs, and repos all independently point to relayers, MPC matching, and ZK settlement as the actual center of gravity.

Graph View