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

The deployed verifier and current clients share one artifact generation. The circuits source and key directory describe an unpublished successor generation. The ceremony must produce one coordinated artifact set before any consumer changes.

Multiple participants will contribute entropy in sequence and destroy it after use. The final artifacts will publish with a hash chain. The protocol will rebuild the verifier, web client, mobile client, and native prover against that one generation.

External security audit

An established Solana audit firm will review the three on-chain programs and proof flow. entros-registry currently handles fees, treasury state, and validator registration scaffolding. Validator selection, quorum, rewards, and slashing remain planned.

The audit precedes mainnet deployment. The final report and safe remediation summaries will become public after fixes land.

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, the three programs can deploy to mainnet. Devnet will remain the development surface. Mainnet program IDs will publish after deployment. Integrators must not assume they match devnet.

Standalone display primitives

The verification trigger shipped as @entros/verify. The React component opens the devnet flow in a popup and returns a result to the opener.

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 client exists for Android development. Representative-device testing, app integrity integration, release hardening, and store distribution remain open.

The planned Seeker release uses Mobile Wallet Adapter and device-protected key handling. A future notification path can remind users when an application requires a fresh result.

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 - work after the audit
• How to influence - the RFC process