Transparency dashboard · pool #001
Check your anonymity before you exit.
Live · epoch 4,192
Deposits · N
12,904
+18 this epoch
Effective anonymity · a
6,120
≈ 12.6 bits of cover
Inclusion rate · α
71%
certified into 𝒜
Spent fraction · σ
33%
of associated notes
01 · Anonymity floor
What a withdrawal hides in right now
Effective anonymity is the count of unspent, associated notes:
a = α(1−σ)N. Wait until it clears your target before you exit.
6,120
unspent · associated notes → 12.58 bits
0 bits81216 bits
Recommended floor for this pool: 12 bits — currently
cleared ✓.
anonymity · last 48 epochsa
dashed line = 12-bit floor
02 · Pool composition
Where the deposits sit
Every deposit is public. This is the split between associated-and-unspent
(your cover), already-spent, and excluded-by-policy.
associated · unspent 6,120
spent 3,016
excluded 3,768
epoch throughput
deposits / epoch +18
withdrawals / epoch −11
net note growth +7
steady-state a ≈ αλd/λw
03 · Current roots
Prove against these
The global root and the current association root. A withdrawal is valid against
any global root in the rolling window of 64.
global root · rt0x7a3f9c…e4d1c4a1
association root · rt𝒜0x91be02…88f37d04
root window64 most-recent global roots accepted
association epoch#4,192 · updated 40s ago
policy versionv1.4 · reproducible ✓
04 · Live activity
The ledger, as it happens
Public events only: a commitment entering, or a nullifier leaving. Neither
reveals which note — that’s the point.
▲ Illustrative data for demonstration · figures are modeled, not a live deployment · anonymity = α(1−σ)N