Practical overview
When it fits
Use the repository when you need the relayer infrastructure behind Renegade's private dark-pool matching, or when you want to start a local instance for development.
Who it is for
- OTC desks considering an in-house relayer to manage trading intentions.
- Rust developers working on private order matching, relayer networking, or the project's MPC and zero-knowledge circuits.
Documented uses
- Run a local relayer instance with a specified inbound port.
- Manage an OTC desk's trading intentions through an in-house relayer.
- Inspect CLI configuration options and work with the repository's unit or integration tests.
- Build or study systems for encrypted order-state gossip and MPC-based matching.
Requirements & limits
- The repository contains relayer infrastructure and cryptographic logic; its README's local-run instructions do not document an end-to-end trading workflow.
- Relayers maintain plaintext orders locally while gossiping encrypted order state, so the role of the relayer matters when evaluating an in-house desk setup.
- Matching execution is replicated within fail-stop fault-tolerant clusters; the project describes inter-cluster semantics separately as Byzantine fault-arbitrary.
- The README documents Cargo commands for local startup, CLI help, workspace unit tests, and crate integration tests.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start a local Renegade relayer
Run a local instance of the relayer with a specified inbound port.
Before you start
- A checkout of the Renegade repository.
- Rust Cargo, as required by the documented cargo commands.
Steps
From the repository's top-level directory, run the command below to start the relayer with inbound port 8000.
cargo run -- -p 8000Run the command below to view the CLI configuration options.
cargo run -- --help
Expected outcome
A locally run relayer configured with the specified inbound port, with CLI options available for inspection.
Guide limitations
- The README documents local startup and CLI help, not production deployment or order submission steps.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- renegade-fi/renegade · Official homepage title · retained in its source language

