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 · Hundred Finance
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 465088641
- Off-chain at
- 2026-11-03T23:46:24.721Z
- Anchored at
- 2026-11-03T23:46:47.000Z
- Block time
- 2026-11-03T23:46:47.000Z
Independent verification
- 1. Database (off-chain)
- 2akzaBYYs8qhHZJkXBVVjJY2VKCpDiAAmQn9ZuVRZ2Vs
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1322 chars)
{"actor":"reviewer","artifact_identity":"eb4453f0a93abef9d225d2314545d5c1","decided_at":"2026-11-03T23:46:24.659Z","decision":"review","disputed_pct":0.1667,"findings_hash":"D8LNyM9XLCXqD9YZmddsAiMfHQw1GMUz1hCTjurZdbZJ","investigation_id":"af09701f-259c-4f20-9652-cbb81aeffcb5","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_content_hash":"01a0a9ed165f39036df543fea3ba657dda198fa02c544b9837d4366a372dd914","page_slug":"hundred-finance","prev_score":50,"reason":"The core narrative (two exploits of about $6.2M and $7.4M, the August 2023 shutdown vote at 99%, the 2024 fund movement through Curve and Uniswap) is supported by the sources I read. One unsupported speculative motive, that the attacker avoided Tornado Cash because of regulatory scrutiny, should be removed. The claim of victim distributions overstates the source, which describes only intended compensation. The March 2022 attack date is reported as March 15 by most outlets and March 16 by BeInCrypto.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}