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_approve · NEAR Protocol
- Sequence
- #12
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 470685132
- Off-chain at
- 2026-11-17T21:30:55.678Z
- Anchored at
- 2026-11-17T21:31:23.000Z
- Block time
- 2026-11-17T21:31:23.000Z
Independent verification
- 1. Database (off-chain)
- 3AwBwcwjaCMwjKzodf5FTRpT9seewtkDddvFgt8gyYLU
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1459 chars)
{"actor":"judge","artifact_identity":"ebd05f959a01153076caa39940bcd741","band_override":null,"decided_at":"2026-11-17T21:30:55.414Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"5dfc3991-d810-433a-868c-cc8880f85b96","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":63,"page_slug":"near-protocol","prev_score":63,"reason":"Of 7 claim findings, none were disputed or unverifiable (0% disputed), so the page falls in the approve band. Five were confirmed against cited sources, including the SEC v. Coinbase dismissal date (claim_findings[0]), the NEAR Intents exploit amount and dates (claim_findings[2]) and the return-of-funds timeline (claim_findings[4]). Two were partially supported: the list of other dropped SEC matters is not in the cited Block article (claim_findings[1]), and the one-hour service resumption was not seen in the fetched text (claim_findings[3]). The only omission, a Nov 2026 NEAR AI data-exposure incident, is minor and low-confidence, and the subject is operating, so no override applies. The reviewer did not check the Rainbow Bridge or Bitwise ETF sections in depth, which limits coverage but is not a defect.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}