Skip to content

NETWORK EXPLORER

reconnecting· devnet

Check the network yourself.

A snapshot of the shielded pool’s public state on Solana devnet, taken at most once a minute and read by this page every 30 seconds. Every number below is public. None of them names a sender or a recipient.

Devnet onlyStyx v2 has run on Solana devnet since 2026-10-07. Test SOL, no real funds. Not externally audited. v1 stays on devnet as the fallback and will not go to mainnet.The figures below count the v1 pools. Styx v2 has run on devnet since 2026-10-07; its own counter comes next.

Total Value Shielded
n/a
across all denomination pools
Shielded Notes
n/a
deposited across all denomination pools
Active Pools
n/a
denominations with deposits
STARK Circuits
8
hash-based, no trusted setup

Source: /api/metrics. Waiting for a snapshot.

What a transparent chain publishes for one payment, next to what the chain shows for the same payment made through this web app: two transactions instead of one.

DEMO

Standard chain

From7xKQ…3fUw
To9mPa…Rt2c
Amount1 SOL
Memo“monthly-plan”

Styx · your payment

From7xKQ…3fUw
To5tLL…aR9k
Amount1 SOL + fees
Memo

Styx · the spend, later

From8hRz…Wq3N
To4vTn…8qLd
Amount0.995 SOL
Memo
ProofC7 · spend
Commitment

A standard explorer prints the sender, the recipient, the amount and the memo of one transfer. Through this web app the chain shows two: your public payment to this deployment, and later a spend from a key that is not your wallet to a payout address made for that note, with a circuit-7 proof and no commitment. A chain reader cannot match the spend to your payment by its fingerprint. This deployment can: it handed you that note. On a quiet pool the minutes between the two can pair them, and every note is 1 SOL, so the amount stays public.

Each square is one note deposited in a pool of identical notes. A web withdrawal carries no commitment, so to a chain reader it could be any note of its pool still unspent: a smaller crowd than this count, which includes spent notes. Against this deployment, for a note it handed you, the crowd is one; against the clock on a quiet pool, it can be one too.

Reading the network…

Hash-based, with no trusted setup and no elliptic curve inside the proof. The deployed verifier accepts all eight; the web app proves on three of them (README.md, Architecture).

p01_stark_verifierDGY37k…fWQvs
C0Subscriber Ownershipweb app
C1Pool Commitmentpaused clients
C2Balance Proofno caller since 2026-09-23
C3Merkle Pathpaused clients
C4Confidential Balanceno caller since 2026-09-23
C5Transferno caller since 2026-09-23
C6Merkle Updateweb app
C7Spendweb app
Snapshotn/a
Shielded programexplorer.solana.com

GbVM5yvetrSD194Hnn1BXnR56F8ZWNKnij7DoVP9j27c