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 · Aethir
- Sequence
- #3
- Score
- 48 → 36 (-12)
- Cluster
- mainnet-beta
- Slot
- 423942103
- Off-chain at
- 2026-06-03T03:07:16.485Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EdaewBJAfFZL2bhpkJVzLboXgXLxDUEBr48UvcPp6Mmf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1324 chars)
{"actor":"judge","decided_at":"2026-06-03T03:07:16.220Z","decision":"review_revise","investigation_id":"70eb8857-f552-4eca-9b7a-e322535ed60d","new_score":36,"page_slug":"aethir","prev_score":48,"reason":"The review confirmed 7 of 16 claims outright, with 6 partially supported and no critical structural failures. However, two findings warrant correction before the page is considered accurate. First, claim_findings[14] shows the ATH all-time low date is wrong — the page states April 7, 2025, but both CoinGecko and CoinMarketCap (Tier 1 sources) record the actual all-time low on February 24, 2026. Second, and more significantly, claim_findings[8] found the ZachXBT flag listed as a risk factor is unverifiable: the cited ZachXBT investigations relate to a different project (Memenetic), and no credible source was found naming Aethir directly as a ZachXBT investigation subject. Citing an unsubstantiated third-party flag as a confirmed risk factor is a meaningful accuracy concern. Three high-priority coverage gaps — independent revenue verification, on-chain tokenomics analysis, and sourcing for the ZachXBT claim — further support revision. Reviewer confidence was 0.78.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}