Self-hosted verification
A verdict is reproducible from chain state and the open spec alone. You never have to trust the issuer — or us.
The load-bearing property
Verification depends only on EAS on Base plus the published spec. If HumanReviewed disappeared tomorrow, every badge would still verify.
In code
import { verify } from "@humanreviewed/verifier";
import { EasReader } from "@humanreviewed/eas-reader";
// Read straight from Base — no HumanReviewed backend involved.
const reader = new EasReader({ rpcUrl: "https://mainnet.base.org", chainId: 8453 });
const verdict = await verify(uid, reader);
// verdict.status ∈ verified | rejected_review | revoked | tier_unmet |
// identity_missing | invalid | not_found@humanreviewed/verifier is dependency-free (spec only); @humanreviewed/eas-reader lazy-loads ethers + the EAS SDK. Both are MIT and installable from npm.
From the CLI
# Batch-verify from the terminal:
npx @humanreviewed/verify 0x<uid> 0x<uid> --chain base
# Check a file matches the attestation's committed hash:
npx @humanreviewed/verify 0x<uid> --artefact ./report.jsonExit code is 0 only if every attestation verifies (and, with --artefact, matches). --api <url> uses the hosted verify endpoint instead of an RPC; --json emits NDJSON.