Verify Official GMIIE Outputs

Only trust intelligence attributed to official domains and verifiable anchors. GMIIE does not publish primary intelligence on personal workers.dev URLs or unofficial mirrors.

Official domains

• Primary hub: https://xxxiii.io
• Fraud checker: https://blockchainfraud.org
• NIL hub: https://nil33.com

Editorial Pulse and extended network properties may link from xxxiii.io but are not substitutes for engine/API verification unless listed here after review.

Not official for GMIIE engine data: kevanbtc.workers.dev, unofficial *.workers.dev mirrors, or screenshots without CID/fingerprint match.

IPFS snapshot verification

GMIIE pins intelligence snapshots to IPFS approximately every 8 hours via Pinata. The latest CID is exposed at /api/ipfs/latest and should match content retrieved from the gateway.

Steps:

1. Fetch GET https://xxxiii.io/api/ipfs/latest — note cid and pinned_at.
2. Resolve https://gateway.pinata.cloud/ipfs/{cid} (or your preferred IPFS gateway).
3. Compare JSON fields (NIG, rings, digest date) to the live engine endpoint for the same cycle.

Engine API fingerprint

Live engine responses include a canonical engine_fingerprint (SHA-256 of normalized NIG, PCS, and ring scores). Compare any third-party copy to the official API.

Fallback static seed (when KV not warmed): /data/gmiie-engine-snapshot.json — label source as editorial-seed in UI.

Article and report integrity

• Editorial pages: SHA-256 in byline where published; LPS-1 anchoring described on XXXIII Protocol.
• Fraud desk reports: X-Fraud-Fingerprint header on API responses — semantic fingerprint for typology consistency.

Report impersonation

If you encounter fake GMIIE sites, forged PDFs, or mislabeled API endpoints, report with URL, screenshot, and claimed NIG/PCS values to intelligence@xxxiii.io with subject GMIIE Impersonation.

Terms · Methodology · Not investment advice