Entros Developer Docs
Build with private human verification on Solana.
Entros is a Solana protocol designed to prove that a wallet is operated by a returning human. Raw motion and full-resolution touch remain on the device.
These docs cover the integration paths: drop-in React components, on-chain reads, SAS attestations, Realms voter-weight, and Agent Operator Permits. They also publish the technical reference for the SDK and on-chain programs, and the public roadmap for what comes next.
Three integration paths
Pick the path that matches your use case. Each integrator only needs one.
Tier 1, drop-in trigger. You want a button that takes a user from an unverified wallet to a completed Entros verification. The popup hosts the wallet connection, behavioral capture, proof, and on-chain transaction. Your app stays wallet-adapter-free until the callback arrives. Install @entros/verify.
Tier 2, programmatic SDK. You want to own the verification UX: custom capture canvas, branded loading states, inline rather than popup, mobile-native. The Pulse SDK exposes the lower-level primitives the popup is built on. Install: @entros/pulse-sdk. Same package powers Tier 1 internally.
Tier 3, read-only. You display an existing Anchor, or gate something where a live capture would be more friction than the action is worth. One function call, free reads, no API key. Install: @entros/pulse-sdk. For anything with real stakes, pair it with a Tier 1 trigger at the point of the action.
Where to start
- New to Entros? Begin with Concepts → Proof of Personhood.
- Most integrators (Tier 1)? Drop in
<EntrosVerify />— see the verification flow. - Custom UX (Tier 2)? See the Pulse SDK reference.
- Read-only (Tier 3)? Jump to the gate-a-route quickstart or read-on-chain.
- Gating something valuable? See what to gate on.
- Curious where this is going? See the Roadmap.
The shape of a Tier 3 read
A read pulls one piece of on-chain state: the Anchor PDA, or an attestation issued through SAS. There is no API key, no billing relationship, no off-chain dependency. The user pays a small protocol fee at verification time. Integrators read for free.
import { verifyEntrosAttestation } from "@entros/pulse-sdk";
const attestation = await verifyEntrosAttestation(walletAddress, connection);
if (attestation?.isHuman && attestation.trustScore >= 100 && !attestation.expired) {
// proceed
}Two numbers, two questions. The score says how consistently this wallet has verified. Recency says how long ago it last did.
For an airdrop claim, a governance vote, or another high-value action, run a verification at the action and read the Anchor afterward. The score describes verification history. The fresh result shows that the wallet passed the current Entros policy. See the verification flow.