Verify patterns

Default strategy: reuse-or-create.

Privacy

client.verify() is an advanced server or controlled-signing path. VerifyGate opens Hosted Verify for checks that cannot finish inside your app. Full matrix: Security

Option	When
`privacyLevel: 'private'`	Default; owner or authorized access for private reads
`privacyLevel: 'public'`	Public reuse without owner auth; pair with `publicDisplay`
`publicDisplay: false`	Unlisted - still public to anyone with id
`publicDisplay: true`	Listed / discoverable (needs `public`)

storeOriginalContent and explicit visibility options are advanced client.verify() storage controls, not the default VerifyGate path.

Reuse-first

<VerifyGate
  gate={[{ verifierId: 'proof-of-human' }]}
  strategy="reuse-or-create"
>
  <Protected />
</VerifyGate>

Fresh

High-stakes actions - force new proof:

<VerifyGate strategy="fresh" gate={[{ verifierId: 'proof-of-human' }]}>
  <Protected />
</VerifyGate>

Read-only gate

<VerifyGate strategy="reuse" gate={[{ verifierId: 'proof-of-human' }]}>
  <Protected />
</VerifyGate>

Hosted interactive

Hand off to /verify for the missing verifier:

<VerifyGate
  gate={[{ verifierId: 'proof-of-human' }]}
  hostedCheckoutUrl="https://proofable.me/verify"
/>

Hosted Verify

Server check

Prefer gateCheck over pulling full proofs for every decision:

const result = await client.gateCheck({
  gate: [{ verifierId: 'proof-of-human' }],
  subject: { accountId: user.accountAddress },
});

if (!result.satisfied) throw new Error('Verification required');

VerifyGate

Props.

Start

Loop.

Overview

MCP

JavaScript SDK

HTTP API

Verifier catalog

Standards

Privacy

Reuse-first

Fresh

Read-only gate

Hosted interactive

Server check

Next

VerifyGate

Start

​Privacy

​Reuse-first

​Fresh

​Read-only gate

​Hosted interactive

​Server check

​Next

VerifyGate

Start

Privacy

Reuse-first

Fresh

Read-only gate

Hosted interactive

Server check

Next