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
- 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. - 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.
- 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 · DoinGud NFT Diamond Bidding Contract Exploit
- Sequence
- #2
- Score
- 42 → 34 (-8)
- Cluster
- mainnet-beta
- Slot
- 462045274
- Off-chain at
- 2026-10-27T10:58:33.994Z
- Anchored at
- 2026-10-27T10:58:53.000Z
- Block time
- 2026-10-27T10:58:53.000Z
Independent verification
- 1. Database (off-chain)
- 64jbocvG26sJpJYaVQtVKX6P6b2CadAafmvmTQNg8XJn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1554 chars)
{"actor":"judge","artifact_identity":"4a31def647819ae75d03683285fbe3d4","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T10:58:33.656Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":42,"reason":"Of 5 claims reviewed, 1 was blocked by the source (claim_findings[3], the exploit post returned HTTP 402) and is excluded from the percentage; of the remaining 4, 1 could not be verified (claim_findings[4], the dormancy claim has no cited source), giving 25%. The funding total, most named investors and the Zug location are not in the cited press release (claim_findings[1]), and the Cleo acquisition rests on aggregator data only (claim_findings[2]), though the page already hedges it. The exploit is presented as an unverified allegation, which matches the reviewer's findings, and no omissions or contradicting subject status were found. A high-priority gap remains: no on-chain transaction or primary source for the central exploit claim. Reviewer confidence is moderate (0.5), so the penalty is set in the lower part of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":4,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}