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 · TMX TRIBE
- Sequence
- #3
- Score
- 40 → 40 (0)
- Cluster
- mainnet-beta
- Slot
- 465088197
- Off-chain at
- 2026-11-03T23:45:09.393Z
- Anchored at
- 2026-11-03T23:45:13.000Z
- Block time
- 2026-11-03T23:45:13.000Z
Independent verification
- 1. Database (off-chain)
- 6ZMWdqirL6ueJjoxeedbuDqT39SRPX5pjPhqbgyMj68M
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1375 chars)
{"actor":"reviewer","artifact_identity":"ec40707f52a124861b0131ed88d46242","decided_at":"2026-11-03T23:45:09.327Z","decision":"review","disputed_pct":0.5556,"findings_hash":"79Vipd6izhamYD9fhwvCBcPHAVBh7FkTETMuhkc5izGD","investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"omissions":{"material":1,"total":2},"page_content_hash":"c1273e6869c626a90df3b75445412827417728848c9cc5af8f8614209bfacd84","page_slug":"tmx-tribe","prev_score":40,"reason":"The core exploit narrative is supported by the Rekt News article: a $1.4M loss, the mint-and-stake loop, two attacker addresses, about $1.2M bridged and sent to Tornado Cash, no pause, a 20/80 bounty offer, unverified contracts, no audit and no statement. Two timeline dates are off (bounty message Jan 5, not Jan 6; Rekt article Jan 8, not Jan 10). The ZachXBT flag is unsupported, and the market figures are undated. The page omits the phishing link posted from the TMXTribe account. I did not fetch the pre-exploit sources.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}