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 · Tectonic
- Sequence
- #6
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 465107758
- Off-chain at
- 2026-11-04T00:54:46.784Z
- Anchored at
- 2026-11-04T00:55:10.000Z
- Block time
- 2026-11-04T00:55:10.000Z
Independent verification
- 1. Database (off-chain)
- E7wEfkfwevbKxqcEKvbedwZh1vfubLDe5BR8ATuZFgqD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1881 chars)
{"actor":"judge","artifact_identity":"dab25d39247a54fa96f3f3e057592278","band_override":null,"decided_at":"2026-11-04T00:54:46.509Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"35a7dd64-02de-402b-8b38-d0d44a9500b7","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":51,"page_slug":"tectonic","prev_score":51,"reason":"The page states that Tectonic remains operational (claim_findings[0], claim_findings[1], both stale), but two accepted sources document an August 30, 2026 price-manipulation exploit that halted the Cronos chain and led to a rollback, with about $9.2M unrecovered (omission_findings[0], critical). The 2024 reentrancy report was confirmed (claim_findings[2]). The token figures are internally inconsistent and differ from CoinGecko (claim_findings[3], claim_findings[4]). Because the central status claim is outdated and the most significant incident is missing, the page is flagged for significant issues and a revision. A full denial is not warranted since the verified historical material holds up and only five claims were checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":6,"severity_override":{"applied":true,"band":"significant","from_band":"approve","reason":"The review reports a critical omission (the August 30, 2026 exploit and Cronos chain halt/rollback) and subject_status.contradicts_page is true. The page says Tectonic remains operational. Counting the two stale findings as disputed gives 2 of 5 (40%), already the significant band. If stale findings are not counted, the percentage would be 0% and understate the problem, so the band is set to significant either way."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}