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 · Belt Finance
- Sequence
- #3
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 464448855
- Off-chain at
- 2026-11-02T09:41:53.337Z
- Anchored at
- 2026-11-02T09:42:21.000Z
- Block time
- 2026-11-02T09:42:21.000Z
Independent verification
- 1. Database (off-chain)
- AWVN4kB6FxUME9mPj8Ruf4LWwoMy8MZ6hmBNug7Eb7y4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1380 chars)
{"actor":"reviewer","artifact_identity":"3e6cf60937f17e6a3ab001720670ebd7","blocked_count":2,"decided_at":"2026-11-02T09:41:53.281Z","decision":"review","disputed_pct":0.3333,"findings_hash":"47o7U5fvM1o3HuYn2zwZqQ9S1DY9w6tyiCwAABi8U3XK","investigation_id":"ecbfa59c-37e4-4b2a-9561-4ce69c7eb561","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"omissions":{"material":0,"total":1},"page_content_hash":"31cc547bf24e4e4ff080b0c1013f7573346cbc6769f0bfb4e92baaab6aa8e629","page_slug":"belt-finance","prev_score":56,"reason":"The core exploit facts (date, $6.23M profit, eight runs, 50M BUSD combined cost, 21.36%/5.51% user losses, Halborn root-cause quote) are confirmed by CoinDesk and Decrypt. The 'total pool losses' framing overstates user loss, since most of the $50M was fees. The 54% BELT drop and the 67%/864 BELT-per-day figures are not in the cited sources. Halborn gives seven iterations rather than eight. The Ozys, KLAYswap and V4 launch claims could not be checked. The project appears still operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"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}