Skip to main content
Sign in
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Decision
review · XDC Network
View on Solana ↗
Sequence
#2
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
424483235
Off-chain at
2026-06-05T15:00:33.733Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
3SoKRZrCMWMXj1ZNHXfxZ2eTf6DBWmeTy5QckmR2Ai1c
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (919 chars)
{"actor":"reviewer","decided_at":"2026-06-05T15:00:33.605Z","decision":"review","investigation_id":"fc145b64-1335-4b3c-aafe-fffa9096e641","new_score":62,"page_slug":"xdc-network","prev_score":62,"reason":"The XDC Network investigation page is largely accurate and supported by independent sources, with one factual error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not 'Q4 2024' as stated. The co-founder listing is partially misleading, as Karan Bhardwaj departed the company in 2018 and is no longer listed on official channels. The page's heavy reliance on official XDC/XinFin sources limits independent verification, and coverage gaps around token distribution, validator centralization, and audit history are notable given the enterprise-focused positioning.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}