Skip to main content
AVOID.NET
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Bond Protocol
View on Solana ↗
Sequence
#4
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
443512596
Off-chain at
2026-08-25T07:51:36.111Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
EVY478hnHeQ3avnkgxMg7rjtZ397dL4taB669zptUKsy
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1034 chars)
{"actor":"reviewer","decided_at":"2026-08-25T07:51:35.864Z","decision":"review","investigation_id":"d9137293-15db-46cf-b00d-94ca66903d90","new_score":62,"page_slug":"bond-protocol","prev_score":62,"reason":"The page's central narrative — the October 2022 Fixed-Expiry Teller exploit, its white-hat resolution, the $2.5M seed round, and the three-firm audit history — is well corroborated by independent news, security-research, and auditor-published sources. The main issues found are a likely misattribution of the $3.3M Immunefi bug bounty to 'Bond Protocol' specifically (evidence points to it being OlympusDAO's own program), reliance on the protocol's own self-reported Q1 2023 metrics without independent corroboration, and an understated 'difficult to confirm' framing of current TVL/activity when a concrete current TVL figure was readily discoverable via the page's own cited source.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}