Anonymity Ring

The Anonymity Ring names the planned validator network. One team-operated private validation service performs the current off-chain checks.

What runs in the layer today

The current service applies or records these check groups:

• Tier 1: capture and distribution checks. The service applies phrase, acoustic, entropy, timing, and feature-distribution policies.
• Tier 2: cross-signal temporal analysis. The validator measures time-series relationships between submitted speech and motion. Entros is evaluating whether this signal adds reliable discrimination across human users, consumer devices, and adaptive synthesis.
• Tier 3: proof invariants. Re-verification checks commitment openings and bounded fingerprint distance inside the circuit.
• Tier 4: phrase and synthesis checks. The service compares the transcript with the issued phrase and applies the configured audio policy.

The public security report gives campaign definitions, denominators, and observed results for T1 through T4b. T5 remains open. Results apply only to their named attack classes and configurations.

What the layer sees and does not see

The service receives the 308-number summary, selected F0 and acceleration series, wallet address, phrase audio, sample rate, commitment data, receipt intent, client signals, capture timing, and a coarse curve outline.

Raw motion and full-resolution touch streams stay on the client. The service processes phrase audio in memory and does not persist audio waveforms.

What the proof attests, what the validator attests

The settlement path has two forms:

• First verification uses a validator-signed receipt bound to the new commitment.
• Re-verification also uses a Groth16 proof. The proof checks both openings and the circuit's fingerprint-distance bounds.
• The private service checks submitted evidence. It does not authenticate browser sensor origin.

The on-chain program verifies its required receipt or proof. The service supplies statistical evidence for the submitted capture. Neither mechanism alone proves sensor provenance.

What "decentralized" means here, and what comes next

The check stack runs behind one team-operated validation service today. The registry program contains SOL registration scaffolding. It does not select validators, assign requests, aggregate a quorum, distribute rewards, or slash stake.

The planned network adds validator admission, request assignment, signed outcomes, quorum settlement, rewards, and slashing. Each mechanism requires a specification, implementation, and audit before activation. See the program reference for current scaffolding.

The current sequence keeps the changing check engine behind one service. A multi-validator release follows after the engine, distribution model, and settlement rules stabilize.

Where to look next

• Threat model - current controls and open boundaries
• Roadmap: Medium-term - planned decentralization work
• Reference: Programs - current registry scaffolding