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_revise · Accumulate
View on Solana ↗
Sequence
#3
Score
52 → 51 (-1)
Cluster
mainnet-beta
Slot
462051198
Off-chain at
2026-10-27T11:19:30.120Z
Anchored at
2026-10-27T11:19:52.000Z
Block time
2026-10-27T11:19:52.000Z

Independent verification

1. Database (off-chain)
Dnc4jPqmA72bCfB1yy69QqafyjejwbRtVfo3DH28TpiK
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1508 chars)
{"actor":"judge","artifact_identity":"c8ce1e3c33917124ffe94f39190ce4d9","band_override":null,"decided_at":"2026-10-27T11:19:29.651Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"dfa94ad1-ba2a-49a8-a647-16bda09764cb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"accumulate","prev_score":52,"reason":"Of 10 claims checked, 2 were disputed and 1 could not be verified, giving 30% disputed or unverifiable (none were blocked sources). The disputed items are the mainnet activation date, which Inveniam reports as 31 October 2022 (Q4) rather than Q3 (claim_findings[4], [5]), and the 500M cap and 200M/300M supply figures, which the cited CoinGecko page does not state (claim_findings[6]). The Morningstar source for the Factom acquisition is dead and the 2021 acquisition date conflicts with Inveniam's own 2020 statement (claim_findings[2], [3]). The core Factom dissolution history is confirmed, no shutdown, exploit or sanction was found, and no omissions were reported, so the page is held to the minor band at its harsh end and no status change is applied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-1,"score_limit":{"applied":-1,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}