Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · TMX TRIBE
View on Solana ↗
Sequence
#4
Score
40 → 40 (0)
Cluster
mainnet-beta
Slot
465088203
Off-chain at
2026-11-03T23:45:09.556Z
Anchored at
2026-11-03T23:45:14.000Z
Block time
2026-11-03T23:45:14.000Z

Independent verification

1. Database (off-chain)
ATwnTzUpw9t7PquBQ66fpc5yMYRkNGcSyhwLLQG6cEtt
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1693 chars)
{"actor":"judge","artifact_identity":"ec40707f52a124861b0131ed88d46242","band_override":null,"decided_at":"2026-11-03T23:45:09.327Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5556,"investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"page_slug":"tmx-tribe","prev_score":40,"reason":"Of 9 checked claims, 2 were disputed (claim_findings[0] bounty date is Jan 5 not Jan 6; claim_findings[1] Rekt article is dated Jan 8 not Jan 10) and 3 could not be verified (claim_findings[5] the ZachXBT flag, [7] the 'some analysts' attribution, [8] an undated live price), giving 55.6% disputed or unverifiable. The core exploit account (about $1.4M loss, attacker addresses, no pause, no audit) is confirmed by Rekt News and CertiK coverage (claim_findings[4]), so the penalty sits in the lower half of the significant band. The ZachXBT claim in the summary has no supporting source, and the page omits the phishing link posted from the project's own account.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (claim_findings do not cover it): the TMXTribe X account posted a link to a site flagged as phishing on 2026-01-07 and the page does not mention it. This confirms the significant band rather than lowering it; the percentage band is already significant."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}