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_revise · Vee Finance
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464299477
- Off-chain at
- 2026-11-02T00:49:05.204Z
- Anchored at
- 2026-11-02T00:49:10.000Z
- Block time
- 2026-11-02T00:49:10.000Z
Independent verification
- 1. Database (off-chain)
- 7ecdceSr8FyvWx7GWkT4YdRomBjfvn3HAbvhk4dpVyDq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1595 chars)
{"actor":"judge","artifact_identity":"0fd15ddf05ff582c35813e15e7c815b6","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T00:49:04.943Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"446f9f73-4903-4ec3-95a6-792f2cd2531c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"vee-finance","prev_score":53,"reason":"The core exploit facts (about $35M lost, the ETH/BTC split, the Zabu Finance context, the VEE price drop) were confirmed against CoinDesk and Rekt, and no claim was disputed outright. However, 4 of the 12 checkable claims (33%) could not be verified: the FBI escalation depends on a dead fullycrypto link (claim_findings[3], [4]), and the mainnet launch date, the AVOID.NET ZachXBT flag and the 2025 price figures have no reachable source (claim_findings[6], [10], [12]). The audit-ignored framing also overstates Rekt, which attributes ignored recommendations to SlowMist only (claim_findings[7], [8]). The V2 relaunch is cited only to unarchivable project posts and is a high-priority coverage gap. One further claim was excluded from the percentage because its source blocked the reviewer. Because nothing was contradicted and the reviewer's confidence was moderate, the penalty is at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}