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 · GoldPesa
View on Solana ↗
Sequence
#3
Score
32 → 26 (-6)
Cluster
mainnet-beta
Slot
461979006
Off-chain at
2026-10-27T07:03:32.896Z
Anchored at
2026-10-27T07:04:01.000Z
Block time
2026-10-27T07:04:01.000Z

Independent verification

1. Database (off-chain)
HkssSs2FPErzkQFWMwzgnM5sNc6dtDjmZgxB4qPByG1p
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1593 chars)
{"actor":"judge","artifact_identity":"b8a2ad3dcbb0ecfe4c6173ffec9fa507","band_override":null,"decided_at":"2026-10-27T07:03:32.482Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2308,"investigation_id":"a1739ade-02c2-4d3c-8080-0ebe7b72b112","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"goldpesa","prev_score":32,"reason":"The core account of the October 2026 GPXHooks exploit on Base (about $114.9K, logic error, trading volume at zero afterward) is confirmed by several outlets (claim_findings[0], [11]). However, 3 of 13 claims (about 23%) could not be verified: the October 2025 Base launch date and its timeline entry (claim_findings[4], [5]) and the CertiK audit statement (claim_findings[6]). The background sources cited are a 2021 release about a different token (GPO), the 1 gram peg and the 2013 'established' timeline entry are only partly supported (claim_findings[3], [8]), and the 'no official response' line is dated and should be rechecked (claim_findings[12]). Two high-priority coverage gaps remain: on-chain verification of the transaction details and proof of the gold backing. These keep the page in the minor-issues band rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-6,"score_limit":{"applied":-6,"limited":true,"proposed":-10,"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}