Renegade exploit analysis

Renegade's match-engine settlement read an order-book entry signed by a verifier whose private key had been shared across two validator nodes during a known infrastructure compromise. The attacker replayed a recorded valid signature to settle against an order that the original signer had cancelled.

DeFiHackLabs reconstructs the sequence against the live Ethereum state. The drain is captured in the README's link reference.

What would have prevented it: a signature scheme that includes a one-shot nonce per order, with the settlement path rejecting signatures whose nonce has already been cancelled.