Layered verification

One weak signal is easy to game. Define a local 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
Signed account	`ownership-basic`	A signed account check alongside the others
Wallet risk	`wallet-risk`	Payment flows and high-value access

A common pair is a social account plus proof of human. Add ownership-basic or wallet-risk when the threat model needs them.

Define the layered requirements

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

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

This is local configuration. It does not publish or persist a Gate.

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 recency on the gate for point-in-time checks, and store proof IDs where replay matters.

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

Last modified on September 14, 2026

Overview

Use cases

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