STYX PROTOCOL // DEVELOPMENT ROADMAP
Building Private Finance
What runs on devnet today, what was built and then paused or retired, and what is being built next.
Devnet Only
Devnet only, test SOL, no real funds. Not externally audited: the only review so far is an internal, AI-assisted audit, with 79 confirmed findings, 1 of them critical (README).
Where things stand
- 22shipped, in use
- 15built, paused
- 7retired
- 4in progress
- 4planned
One square per item on this page, counted from the lists below. The shipped list keeps paused and retired work, each marked with its state, and neither is counted as in use.
Current focusStyx v2
Next
Actively building
Styx v2
Designed to fix the root cause of the two worst findings, with security profile R: the Poseidon2 hash, a fingerprint of four field elements, challenges drawn from a cubic extension field and a statement bound to the key that submits it. Poseidon2 and the extension-field transcript are written and tested (WP2, WP3) outside the published repository; the circuits, prover, verifier and clients come next (README, Security status).
External Security Audit
An external review by independent cryptographers and Solana auditors, starting from the internal AI-assisted audit (79 confirmed findings, 1 critical), before any mainnet deployment.
Mainnet Launch
Mainnet is for v2 only, after a new hash, a wider fingerprint, extension-field challenges, a new verifier and the external review. v1 never goes to mainnet.
Internal Network Mapping
Map internal transaction flows to improve privacy routing and reduce on-chain fingerprinting across the protocol.