Near-term

Near-term work runs through three gates before mainnet, in order: the trusted setup ceremony, an external security audit, and the operational lift. The integrator-facing surface area fills out alongside them.

Trusted setup ceremony

Groth16 Phase 2 currently has a single contributor. Multiple participants run the ceremony in sequence, each contributing random entropy and destroying it afterwards, and entros-verifier is recompiled against the resulting verifying key. The structured reference string is compromised only if every contributor colludes, so one honest participant is enough for the math to hold. Ecosystem builders and integrators take the open slots. The public log and hash chain publish at entros.io/ceremony.

External security audit

A full audit of the three on-chain programs and the on-chain proof flow by an established Solana audit firm. entros-verifier carries the highest stakes, entros-registry handles fees and validator staking, and entros-anchor mints the non-transferable token. The audit precedes mainnet deployment, and the firm publishes its report on completion with findings remediated in public. Expected engagement: 6–10 weeks plus remediation.

The pre-audit hardening work is captured in the protocol's internal AUDIT.md and the public security program. Findings discovered during internal red-teaming are remediated and re-tested before the external engagement begins.

Operational lift

The third gate is a sequence of small items rather than one large one: paid RPC capacity, a hardware-wallet upgrade authority, treasury backup and recovery procedures, monitoring, an incident-response runbook, and a partner integrator on standby for the first live mainnet verification.

Mainnet deployment

After all three gates clear and audit remediations are in place, the three programs deploy to mainnet. Devnet remains live for development; mainnet is the production surface. Program IDs are immutable across the deployment—devnet IDs and mainnet IDs match where the deployment authority chooses, with documented exceptions for any program-id-derived PDA surface.

Standalone display primitives

The verification trigger shipped as @entros/verify — a popup-pattern React component that opens a window to entros.io, runs the 12-second capture, and posts the verified payload back. Five lines of JSX, runs against the canonical flow, no redirect.

The remaining packaging work is on the read primitives. EntrosGate (route guard, reading score and recency) and EntrosBadge (Trust Score pill) are still copy-source single-file components. The near-term plan is a standalone @entros/react package that consolidates them as drop-ins, composing with @entros/verify so a gate can run a verification in its own fallback. Until then, the canonical sources live in the entros.io repo and stay in sync with the on-chain layout.

Native Solana Mobile build

A React Native package and platform-specific native builds for iOS and Android. The capture quality on mobile is materially higher than desktop—IMU at higher sampling rates, native microphone access, authentic touch dynamics.

The Solana Mobile (Seeker) integration is the central piece: Mobile Wallet Adapter for the wallet connection, Seed Vault for keypair handling, and a notifications path for re-verification reminders aligned to the score decay curve.

Integrator pilots

Three production integrator pilots, one each across the three composability surfaces:

• A Realms DAO using the voter-weight plugin
• An airdrop or referral protocol using SAS attestations
• An AI-agent platform gating registrations on operator Trust Score

These pilots inform the threshold-setting documentation and surface real-world edge cases that internal testing misses.

Where to look next

• Medium-term—what lands after the audit
• How to influence—the RFC process and where feedback lands