Skip to content
Styx Protocol · Formerly Protocol 01 · Building in public
Nine weeks, logged.
A record of what was built, what broke, and which claims did not survive being measured. Where an entry once carried a number this page could not stand behind, the number is gone and the correction is in the entry.
Weeks 01 to 09 · April 6 to June 7, 2026
Devnet onlyStyx has had no external audit, and there is no mainnet deployment.
The log stops at week 9
The last entry covers June 1 to 7, 2026, and nothing has been added since. Read this as a record of nine weeks in spring 2026, not as the current state of the software, and not as a promise of a weekly cadence. The standing facts have not changed: devnet only, no external audit, no mainnet deployment.
- Week 01April 6 - 12, 2026Shipped
Superteam Ireland & Dublin
- Listed as a Superteam Ireland project
- Entered the Colosseum Frontier hackathon, an entry and not an outcome. The event has since closed
- Booked five days at Dogpatch Labs in Dublin to build in person
- Week 02April 13 - 19, 2026Shipped
Hash-Based STARK Migration
- Moved the six circuits off Groth16 onto hash-based STARKs: Poseidon and Merkle trees, with no elliptic curves anywhere in the proof. Wallets and transaction signatures stayed Ed25519
- A FRI verifier running as a Solana program, with no trusted setup
- DEEP-ALI composition wired across the circuits. The soundness figure published here at the time was wrong: the FRI rate was later measured at one half rather than one sixteenth, and the verifier had no DEEP binding yet. The number is withdrawn, not restated
- Merkle-Update AIR verifying on-chain inside Solana's compute limit. The compute-unit figure once quoted here is stale and is not repeated
- p01_liquidity deployed on devnet as the unshield liquidity pool. It was found drainable later (audit F27), and its pool was set inactive on 2026-09-22
- The WASM prover, the extension and SDK v2 all ported to the new circuits. No test count is quoted here; run the suite in the repository. The only on-device proving figure ever measured is circuit 3 at 1,482 ms on 2026-08-03 (docs/HISTORY.md), and a withdrawal still does not complete on a phone with the installed build, so on-device proving is unfinished rather than shipped
- Week 03April 20 - 26, 2026Shipped
Colosseum Submitted & v0.9.9 Shipped
- Submitted to the Colosseum Frontier hackathon, accelerator track. A submission, not a result, and the event has since closed
- Pitch deck and economic charter published as PDFs on the marketing site
- Service registry deployed on devnet with four demo service entries. Those entries were placeholders; no streaming provider is or was involved
- useServiceRegistry hook wired in, release APK demoed on an Android handset
- v0.9.9 tagged internally, denominated_pool_v2 seed bump, 13 fresh pools
- Merkle proof rebuild from chain events. Note recovery ran end to end on the cases tested
- abandonNote action added, and the destructive walletStore init wipe fixed
- Marketing refresh on the web app, plus a Hermes Buffer compatibility fix in specter-sdk
- Week 04April 27 - May 3, 2026Shipped
Five Days in Dublin & Proofs End-to-End
- Five days in Dublin with Superteam Ireland, face to face with builders, founders and investors
- Met Diarmuid (Superteam IE) and Alejandro Gutierrez (Lead Superteam IE / Blockchain Ireland)
- Pete Townsend's talk on finding product-market fit in Web3 at Buildstation re-shaped the roadmap
- Merkle root divergence fixed via replayMerkleProofFromEvents. The notes that had gone unrecoverable came back in the cases tested
- Unshield lifecycle: 5 cascading bugs closed, per-pool counter via findSafeShieldCounter
- V3 STARK pools deployed on devnet, v1.0.0 tagged internally
- Applied to CastleDAO Ireland (August 2026)
- Week 05May 4 - May 10, 2026Shipped
V3 End-to-End, Opacity Sprint & Multi-Relayer
- V3 STARK transfer ran end to end on devnet: send, encode, import, mature, unshield. The net SOL figure once quoted here had no signature published beside it, so it is gone
- The transaction-opacity sprint landed its parts: p01_relayer wired into V3 (Phase A), event scrubbing on chain (Phase B), a uniform proof size (Phase C), fee_escrow PDAs (Phase E). None of that broke the link between a deposit and its withdrawal at the time: the withdrawal republished the deposit commitment. Since then a web withdrawal runs on circuit 7 and publishes no commitment, while a phone withdrawal still republishes it. On the web path this deployment hands you an older note, so it still knows which note is yours
- Multi-relayer sprint: auto-rotation, a liveness filter, chunked submit_job, and lazy reputation decay against Sybils. The hosted relayer nodes were retired on 2026-08-28
- V4 pool seed bump (denominated_pool_v4), 13 fresh pools, leaving the un-decodable legacy events behind
- subscribe_private V3 fixes: Rust structs moved from V2 to V3, mobile instruction-builder placeholders, stark_proof_buffer made writable, 4 cascading bugs closed
- Mobile UI gained two modes (Classique and Privé) with V3 routing in subscribe.tsx and (streams)/[id].tsx, an explicit note picker, and withKeepAwake
- subscribe_private vault creation validated on chain. The PDA is shown truncated here (FG3DPX6SN…), so it is not something a reader can resolve from this page
- Quantum Wallet UX design document written as the specification for the months after judging
- Week 06May 11 - May 17, 2026Shipped
Dev3pack Placing & Demo Day
- Ranked second on the Solana track at the Dev3pack Global Hackathon, per the organizers' leaderboard snapshot of 11 May 2026 (hack.dev3pack.xyz)
- Went live on X during the Demo Day window, with a streaming-subscription demo flow as the headline. The service in that demo was ours
- Marketing site and pitch materials refreshed off the back of both
- Week 07May 18 - May 24, 2026Shipped
Device Builds & Hardening
- Android release build pipeline stabilized on Windows: worklets, then the app. That build produced an internal release APK of roughly 96 MB
- Device smoke-test workflow via the bundled release APK over adb
- Roadmap re-shaped after Pete Townsend's talk on finding product-market fit in Web3
- Week 08May 25 - May 31, 2026Shipped
Stabilization · STARK Unshield & Relayers
- C3 merkle_path verifier fixed on devnet. The non-trivial paths that had been failing unshielded in the cases tested
- Fixed a Noble shim regression that had broken transaction serialization
- Second relayer brought online on Fly (Frankfurt) with the dormant-node self-heal. Both hosted nodes were retired on 2026-08-28
- Privy recovery seed persisted offline, which killed the boot-time signing hang
- Week 09June 1 - June 7, 2026Shipped
Privy Removal & Extension Parity
- Removed Privy. The local wallet became the default signer, with no remote-signing dependency
- Extension caught up with mobile: denominated note transfer, relayer-routed private unshield, license keys that carry no account, Standard and ZK modes, scan-import device pairing, and phone-to-extension connect
- Shipped relayer RPC bad-slot self-healing and the live health indicator. The relayer nodes were retired on 2026-08-28, and the indicator went with them
- v1.0.2 and Chrome extension v0.5.0 tagged. Both are internal tags; this page does not link a download. The mobile app and the extension are paused since: the current verifier rejects their proofs
10Follow along
The next entry gets written the same way.
Where a number could not be checked, it was removed or marked as internal, and where the old version guessed, the entry now says so. Several entries above still rest on records only the founder or the event organizers hold, and they are labelled that way.
That X account is the founder's personal one, which is where these updates were posted. The project account is linked in the footer.