Verify a seal

A sealed dossier's manifest is canonically hashed, EIP-712-signed, and anchored on X Layer as a salted commitment — keccak256(manifestHash ‖ salt) — in the AssayRegistry contract at 0x96f8b5f0bfa06e065a861ac220bd86f5722b8ef4 (chain eip155:196). No personal data goes on-chain. Ever.

In the browser

Use assayed.xyz/verify: paste a dossier ID (DSR-…) or a raw leaf (0x…, 32 bytes) and read what the chain says — sealed, pending, or not found.

The featured fictional demonstration is a real mainnet exhibit:

• dossier DSR-WC0Q7NZ7
• leaf 0xf838233e08922df8238f2fea3f22d98bbb1a1f32d08b8dd1b6f17d880ae64b29
• seal batch on the X Layer explorer

Over MCP

asy_verify is free forever and never payment-gated:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "asy_verify", "arguments": { "dossierId": "DSR-WC0Q7NZ7" } }
}

The result carries found, sealStatus, anchoredAt, and an explorerLink for independent checking. A version-qualified reference such as DSR-…@v2 selects one immutable version and returns its available lineage. With a raw leaf, any X Layer RPC can independently read anchoredAt(leaf) on the registry.

What a seal means — and what it does not

A seal proves the artifact is unchanged — not that a claim is objectively true. We say exactly which tier each claim earned, and we never imply more than that.

Each claim inside a dossier carries its own evidence tier — Attested, Documented, Linked, or Sealed — and the recruiter share view shows tiers per claim. Honest scope, stated out loud.