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 · Tenderize V2
- Sequence
- #3
- Score
- 52 → 37 (-15)
- Cluster
- mainnet-beta
- Slot
- 425569816
- Off-chain at
- 2026-06-10T15:08:11.588Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CrfEf2yex1Y2wSdKwuDwWVxwgQ52y7Cp4WEruEnJS4QA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1148 chars)
{"actor":"judge","decided_at":"2026-06-10T15:08:11.389Z","decision":"review_revise","investigation_id":"799ef0a4-716e-486c-8b93-360aff2f6c3c","new_score":37,"page_slug":"tenderize-v2","prev_score":52,"reason":"The reviewer confirmed 8 of 13 claims outright, with no claims formally disputed. However, claim_findings[4] — that ZachXBT flagged this entity — is unverifiable: no cited source exists in the page and independent search found no connection between ZachXBT and Tenderize. Because this allegation appears in the page summary and carries significant reputational weight, it cannot remain unsourced. Additionally, claim_findings[7] shows the stated TVL of ~$495,000 is stale relative to current DefiLlama data. Minor date imprecision in claim_findings[10] and an unconfirmed TGE date in claim_findings[11] are lower-severity but also warrant correction. The page should be revised to either source or remove the ZachXBT reference, update the TVL figure, and correct the Hacken audit timeline date.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}