Long-term

The long-term aim is for proof of personhood to be a Solana primitive that any program can read, the way every program can read SOL balances or SPL token holdings. Not a vendor; not a brand; an on-chain layer.

Identity as public infrastructure

The protocol's success is not measured in revenue. It is measured in the number of integrators building against the on-chain Anchor. When an Entros gate is as routine as a token-balance check, the protocol has done its job.

This is also the reason the protocol's economics route fees to validators and to a deflationary token rather than to a corporate treasury indefinitely. The infrastructure should be sustainable without a centralized operator.

Cross-chain as a default

A wallet's verification status today is a Solana account. Tomorrow it should be a value any chain can read with the same confidence as a Solana program reads it. The medium-term relay work matures into a cross-chain-default model: any chain that gates on personhood reads the Solana attestation, with finality, without trusting any centralized bridge.

Behavioral as a moving target

The threat surface evolves. Generative models for voice, motion, and touch will improve. The check stack the Anonymity Ring runs will need to evolve in step. The long-term shape is a community of researchers, validators, and integrators who jointly maintain the check stack—not a single team holding the secret recipe.

What stays constant

• Privacy by architecture. Raw biometric data does not leave the device. This is not a feature of the current implementation; it is a property the protocol makes hard to violate. Every future version is built on the same constraint.
• The bounded question. The protocol answers "is this the same human, returning, over time" and nothing more. It does not turn into a KYC service, a credit-scoring service, or a real-world-identity directory. The scope is the load-bearing claim.
• Open programs, open SDK, open research. The on-chain primitives, client SDK, circuits, and research paper are auditable in source. The server-side validation pipeline is closed-source per responsible-disclosure convention; its threat model and aggregate red-team results are public. Every adversarial result is published. Every reference number in this documentation can be traced to a public artefact.

Where to look next

• Concepts: Proof of Personhood—the bounded question
• How to influence—the RFC process for shaping what comes next