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 · B² Network
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 443521332
- Off-chain at
- 2026-08-26T15:05:47.600Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6x2BdBWfYx7eUbYwgTMP5V8423e9M4Uq3A8qpt8bSk5c
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1441 chars)
{"actor":"reviewer","decided_at":"2026-08-26T15:05:47.321Z","decision":"review","investigation_id":"a74775a0-4393-49f0-941c-daae5e6e1518","new_score":28,"page_slug":"b2-network","prev_score":28,"reason":"The core exploit narrative (8.59M B2 tokens / ~$3.86M drained via upgrade-authority compromise on July 22-23, 2026, laundering path, bounty offer, and 'Hackers' Day' cluster context) is well-supported by multiple independent tier-1/tier-2 sources and is internally arithmetically consistent, and it matches the figure and date recorded on an independently-verified external cluster page. The clearest defect is a funding-round conflation: the page attributes Animoca Brands to the January 2024 seed round when primary sourcing shows Animoca Brands actually joined a separate October 2024 strategic round (though the investor's name itself, unlike the sibling duplicate page's 'Animoca Ventures,' is correct). A secondary citation-integrity gap exists around an uncited Coin68 price-drop claim, and one orphan source (nftplazas.com) appears in the source list without ever being cited. The page shares a same-entity duplicate, 'b-squared-network,' with which it is inconsistent on investor naming, founding-date precision, and level of exploit detail, and neither page cross-references the other.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}