Layered verification

One weak signal is easy to game. Define a policy that layers checks, so visitors must pass more than one.

Layer	Check	When
Social or work account	`ownership-social` or `ownership-org-oauth`	The linked identity most products need first
Human	`proof-of-human`	Bot resistance and fair access
Wallet risk	`wallet-risk`	Payment flows and high-value access

A social account plus proof of human covers most products.

Define the layered requirements

import { defineGate } from '@proofable/sdk';

const layered = defineGate([
  { verifierId: 'ownership-social' },
  { verifierId: 'proof-of-human' },
]);

defineGate builds the policy in your code and publishes nothing.

Add it to your app

<VerifyGate
  gate={layered}
  onVerified={(result) => {
    // Store result.qHash to prevent replay
  }}
>
  <button>Verify to continue</button>
</VerifyGate>

Check on your server

const result = await client.gateCheck({
  gate: layered,
  subject: { accountId: user.accountAddress },
});

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

Set maxAgeMs on a requirement for point-in-time checks, and store proof IDs where replay matters.

Sell access with a Listing covers publishing and commerce. Hosted verification covers the browser flow for missing checks.

Last modified on October 25, 2026

Overview

Use cases

Compare

Reference

Legal

Guides

Define the layered requirements

Add it to your app

Check on your server

​Define the layered requirements

​Add it to your app

​Check on your server

Define the layered requirements

Add it to your app

Check on your server