Skip to main content

Verification

Verify a snapshot ID

Use the verification box to query the public endpoint contract and review the returned verification status.

Verify snapshot ID

Query the backend verify contract directly and inspect the exact status fields returned by SignalX.

Submit a SNAP ID exactly as published. The backend accepts 1-128 characters, including letters, numbers, underscore (_), hyphen (-), and colon (:).

Contract reference: /api/openapi

How verification works

  1. Submit a `snap_id` to query the backend verify contract through the same-origin site proxy.
  2. `VERIFIED` means the archived canonical SNAP payload hash matches the stored expected hash.
  3. `MISMATCH`, `PAYLOAD_MISSING`, `NOT_FOUND`, and `INVALID_REQUEST` are distinct backend outcomes and should not be treated as equivalent.
  4. `payload_present` and `evidence_present` tell you whether payload and publish-archive data exist, but this page does not compare exact Telegram message bytes directly.

API contract details are published in /api/openapi. For the current proof boundary, read /trust.

Verification notes

Verification proves stored SNAP payload integrity when a canonical payload is archived. It does not, on this page, prove exact Telegram message text parity. Use the trust surface for the current proof boundary.

Read the authoritative trust page at /trust.