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
- #4
- Score
- 34 → 32 (-2)
- Cluster
- mainnet-beta
- Slot
- 464788586
- Off-chain at
- 2026-11-03T05:54:57.971Z
- Anchored at
- 2026-11-03T05:55:17.000Z
- Block time
- 2026-11-03T05:55:17.000Z
Independent verification
- 1. Database (off-chain)
- FpT2W2qRnTLwbPmXDvkk7VeQQqqrtGGrCyAWCZPsH65S
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1376 chars)
{"actor":"judge","artifact_identity":"96270391a5312c4094af8fb0b7adbc17","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T05:54:57.707Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":32,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"Of five claims checked, one could not be read because the source blocked the reviewer and was left out of the count. Of the remaining four, none were disputed and one (claim_findings[1], the founder names and 5%-95% share range) could not be supported by the cited Newswire release, giving 25% unverified. The page's central exploit allegation is framed as unverified, which matches the reviewer's own search (claim_findings[2]), but the page is titled as an exploit with no primary source, a high-priority coverage gap. A modest penalty is applied, softened by the reviewer's moderate confidence.","replaces_fact_checks":{"score_before_fact_checks":42,"undone":1},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-2,"scored_claims":4,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}