Entros_docs
Quickstart

Verify with an application policy

Request recent verification and wallet continuity through an Entros popup.

This integration uses Verify and the Entros popup. Pin the package version when adding the component:

npm install @entros/verify

EntrosVerify opens the wallet and capture flow in a popup. The popup checks your application requirements before sending a result. The consumer checks those requirements again before calling onVerified.

Request a recent verification

import { EntrosVerify } from "@entros/verify";

<EntrosVerify
  integratorKey="your-integrator-key"
  policy={{
    id: "claim-access",
    version: 1,
    minTrustScore: 0,
    maxVerificationAgeSeconds: 300,
    maxEvaluationAgeSeconds: 90,
    requiredAssurance: "browser_unattested",
    uniquenessRequirement: "allow_unmeasured",
    requireAttestation: false,
    cluster: "devnet",
  }}
  onVerified={(result) => setVerificationResult(result)}
  onError={(error) => setVerificationError(error.reason)}
/>

The callback supplies interface feedback. Your server or program must authorize the protected action where it executes. Authenticate the wallet's action request, reread current evidence, and evaluate your server-owned policy before granting access.

The React consumer requires React 19. The hosted popup owns wallet connection, capture, and Solana submission.

Read the result

The result contains the wallet, transaction signature, current Trust Score, and a versioned policy decision. result.policy.evaluatedAgeSeconds records verification age. result.policy.evidence records Anchor creation time, count, network identities, and attestation status.

attestationPda is null when the policy allows an absent or unavailable optional attestation. A nonnull address refers to an account that passed the strict reader at evaluation time. Read current state again before relying on that account for settlement.

The browser assurance status remains browser_unattested. Uniqueness remains unmeasured. Neither status establishes sensor provenance or population uniqueness.

See Verification flow for compatibility, error handling, and settlement requirements.

On this page