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 · Qubit Finance
- Sequence
- #3
- Score
- 10 → 0 (-18)
- Cluster
- mainnet-beta
- Slot
- 465096142
- Off-chain at
- 2026-11-04T00:13:15.493Z
- Anchored at
- 2026-11-04T00:13:41.000Z
- Block time
- 2026-11-04T00:13:41.000Z
Independent verification
- 1. Database (off-chain)
- FV7oV5L14ZFvTWGkovgSNkF3vgrqQsP97v4XNczU2tLs
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1726 chars)
{"actor":"judge","artifact_identity":"741c377b04696658e751a22b28c1c27a","band_override":null,"decided_at":"2026-11-04T00:13:15.078Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"d90e7a11-4928-45d2-87e7-45da166374d3","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"qubit","prev_score":10,"reason":"The core exploit facts (27 Jan 2022 date, 77,162 qXETH minted, about $80M lost, no recovery, $2M bounty) were confirmed against Tier 2 sources (claim_findings[0], [1]). Two of six checked claims, the statements that the protocol 'ceased operations' / is 'no longer operational' (claim_findings[3], [4]), have no supporting source, giving 33% unverifiable. The claim that compensation was never executed (claim_findings[2]) is only partly supported, because the project's own post says markets reopened and compensation would begin in Feb 2022, and the page omits this (omission_findings[0]). The penalty is kept at the lower end of the band because the reviewer's confidence is 0.5 and the key contrary source was seen only as a search snippet.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-18,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (the project's own markets-reopening and compensation post from Feb 2022 is not mentioned) and a high-priority gap on post-2022 status. This confirms the significant band that the percentage already implies."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}