Dark Pool Order Matching
Private order book — orders hidden until matched. Key vectors: order front-running despite privacy, match manipulation, settlement ordering. Novel attack surface with no existing playbook.
MPC / Cryptographic Layer
Multi-party computation for order privacy. MPC protocol implementation bugs, key management errors, proof verification bypass. Rust cryptography is hard to audit — but implementation bugs are more common than people think.
Settlement Logic
When orders match, settlement must be atomic. Partial settlement exploits, settlement revert manipulation, asset accounting errors. Standard DeFi patterns apply at settlement layer even if order layer is novel.
OG · Technical
Novel architecture = novel bugs. The dark pool concept hasn't been battle-tested at scale. Read the whitepaper first — understand the privacy model — then find where it breaks.
RHONE · Floor
$100K for Rust with no existing playbook = low competition. Most hunters skip novel. We don't skip novel — novel is where the floor has an edge.
RICK · Dissect
Cryptographic implementation in Rust. The sorry isn't usually in the crypto math — it's in the plumbing around it. State management, key handling, error paths.
Next Action · Architecture Read
Read the Renegade whitepaper + protocol docs first. Understand the privacy model before touching code. The attack surface map comes from the architecture, not the code.