The MPC-ZKP Architecture | Renegade
docs.renegade.fi · 916 words · saved by 3 readers
On-chain dark pool. MPC-based DEX for anonymous crosses at midpoint prices.
On this page The core difference between Renegade and all other exchanges (both centralized and decentralized) is that state is kept locally . Instead of balances and orders being maintained by a centralized server (e.g. Binance) or on many thousands of distributed servers (e.g. Uniswap), all Renegade state is maintained by individual traders. Some terminology: 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 (technically, "hiding and binding commitments") are posted on-chain. A relayer is a node in the Renegade
saved by
related reading
- GitHub - stealthdrop/stealthdrop: Anonymous Airdrops using ZK-SNARKsgithub.com
- 0xPARC0xparc.org
- Collaborative zkSNARKseprint.iacr.org
- Secure multi-party computation - Wikipediaen.wikipedia.org
- Midstate | Protocol Architecturemidstate.cash
- The CLOB Wars — Monolithic vs. Modular in Next-Gen On-Chain Exchanges - Dare to Knowthogiti.github.io
- The Basics of Blockchain Privacy: How to Remain Anonymous on the… — Everythingblockchainmirror.xyz
- Trilemmas in Decentralized Computing — zerummirror.xyz
- Intern Breakdown #4: Zero-Knowledge Proofsinternbreakdowns.substack.com
- How the Sovereign SDK works — Sovereignmirror.xyz
- Shared Sequencing: Defragmenting the L2 Rollup Ecosystem - HackMDhackmd.io
- Collaborative zkSNARKsusenix.org