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 · Goose Finance
- Sequence
- #3
- Score
- 57 → 57 (0)
- Cluster
- mainnet-beta
- Slot
- 464344504
- Off-chain at
- 2026-11-02T03:29:31.869Z
- Anchored at
- 2026-11-02T03:29:55.000Z
- Block time
- 2026-11-02T03:29:55.000Z
Independent verification
- 1. Database (off-chain)
- H2AQVHwUhDJacg6m4X19txTB5wBVXsPKuzb3saKkGqPm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1367 chars)
{"actor":"reviewer","artifact_identity":"b712a26641c6e7cf48b81ad30aad3af8","blocked_count":1,"decided_at":"2026-11-02T03:29:31.809Z","decision":"review","disputed_pct":0.4,"findings_hash":"3G4B5zDQmquyXAyu8hxwDFLDKd2Mgawd1Rt7rrkQwDRj","investigation_id":"951e2e55-f6cd-42e8-bad9-294b110ea4c3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":57,"omissions":{"material":0,"total":1},"page_content_hash":"bb0988c0bf234f00cf8cff1d70d788bc4bb213afbc88cec6368d01dc9664ed1a","page_slug":"goose-finance","prev_score":57,"reason":"The core facts hold: the March 2026 exploit date, amount and cause, and the CertiK audit counts all match the cited sources, and the project is still operating. Unsupported items include the 'Low' severity label, the #1,911 rank and the 46% coverage figure, none of which appear in the cited pages. Two figures are slightly off: the ATH date, which should be one day earlier, and the TVL, which is outdated. Several cited sources were not fetched, so many claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}