Skip to main content
AVOID.NET
← 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_approve · Verus Protocol (VRSC)
View on Solana ↗
Sequence
#3
Score
21 → 21 (0)
Cluster
mainnet-beta
Slot
443518880
Off-chain at
2026-08-26T00:03:57.385Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
EnPgLPXBDhHZtaW4HXmTVb9qN4gAh1rk6vTjo8fikBuv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1521 chars)
{"actor":"judge","decided_at":"2026-08-26T00:03:57.177Z","decision":"review_approve","investigation_id":"8b05afa2-b3b1-4812-a3c2-2b69513839e8","new_score":21,"page_slug":"verus-protocol-vrsc","prev_score":21,"reason":"Of 21 factual claims checked, 19 were independently confirmed and none were disputed or found unverifiable, putting disputed_pct at 0% under the reviewer's own methodology (claim_findings[9] and claim_findings[14] are the only non-confirmed items, and both are 'partially_supported' citation mismatches rather than factual errors). claim_findings[9] found that a Wormhole/Nomad comparison was correctly attributed to Merkle Science but overstated in also crediting Halborn; claim_findings[14] found a TVL decline figure that is true and independently verifiable but not present in the specific sources the page cited for it. Neither defect makes any statement on the page inaccurate, and the reviewer confirmed the page's hedged language and its deliberate avoidance of an unsupported 'inactive team' claim. The one high-priority coverage gap (present-day status of the bridge after July 23) is a completeness issue, not an accuracy one: the page never asserts the bridge is currently open, closed, or safe, so the gap does not make any existing claim misleading — it flags an opportunity for a follow-up update rather than a defect in what's already published.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}