Skip to main content
AVOID.NET
← 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.

Sequence
#1
Score
Cluster
mainnet-beta
Slot
446704396
Off-chain at
2026-09-13T12:35:33.309Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
296kQ1bz8KEViuYsh8zxzpjCD2KWgomoRrb6buKi5ubs
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (3597 chars)
{"actor":"system:backfill","investigation_id":"0dde5f6b-7caa-49c7-91ca-34a8bb058409","kind":"publish","page_slug":"0xb636ac58efbcad378ae834f27646ad16761f5bf6","published_at":"2026-09-13T12:35:33.185Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"0xb636ac58efbcad378ae834f27646ad16761f5bf6","sections":[{"content":"The address 0xb636AC58EFBCaD378ae834f27646ad16761F5BF6 was checked on Etherscan and identified as an externally owned account (EOA), not a smart contract. It shows a balance of 0 ETH and a transaction count of 0, with no first or latest transaction recorded and no token holdings across the chains tracked by Etherscan's multichain portfolio view. This indicates the address has either never been used to send or receive funds on Ethereum mainnet, or was queried before any activity occurred. No private or public name tags have been applied to it on Etherscan.","heading":"On-Chain Profile","severity":"low","sources":[{"credibility":1,"name":"Etherscan address lookup for 0xb636AC58EFBCaD378ae834f27646ad16761F5BF6","type":"on_chain","url":"https://etherscan.io/address/0xb636ac58efbcad378ae834f27646ad16761f5bf6"}]},{"content":"Searches of Chainabuse and general web search engines did not surface any reports, complaints, or discussion threads referencing this specific address. No listing was found tying it to phishing, rug pulls, exploits, sanctioned entities, or any other form of alleged malicious activity. The absence of results is not proof of legitimacy; it may simply reflect that the address has not been used in any publicly reported activity, on any chain, or has not yet been indexed by these community-driven databases.","heading":"Abuse and Scam Database Checks","severity":"low","sources":[{"credibility":2,"name":"Chainabuse - Report and Combat Crypto Scams (platform, no matching report found)","type":"community_report","url":"https://chainabuse.com/en"}]},{"content":"Attempts to check the same address on other EVM-compatible chain explorers (BscScan, PolygonScan, Arbiscan) were inconclusive; direct access to BscScan was blocked (HTTP 403) and web search returned no indexed pages confirming activity on those chains. Broader web searches for the raw address string, with and without common fraud-related keywords such as 'scam,' 'hack,' or 'lawsuit,' returned no relevant results — only unrelated hash strings and generic explorer landing pages. No news articles, blog posts, social media discussion, or regulatory mentions referencing this address were located.","heading":"Cross-Chain and General Web Presence","severity":"low","sources":[{"credibility":1,"name":"Etherscan address lookup","type":"on_chain","url":"https://etherscan.io/address/0xb636ac58efbcad378ae834f27646ad16761f5bf6"}]}],"sources_used":[{"credibility":1,"name":"Etherscan address lookup for 0xb636AC58EFBCaD378ae834f27646ad16761F5BF6","type":"on_chain","url":"https://etherscan.io/address/0xb636ac58efbcad378ae834f27646ad16761f5bf6"},{"credibility":2,"name":"Chainabuse - Report and Combat Crypto Scams","type":"community_report","url":"https://chainabuse.com/en"}],"summary":"0xb636AC58EFBCaD378ae834f27646ad16761F5BF6 is an Ethereum externally-owned account (wallet address, not a smart contract) with zero ETH balance and zero recorded transactions on Etherscan. No name tags, warning labels, scam/phishing flags, or abuse reports were found for this address on Etherscan, Chainabuse, or in general web search. There is no public evidence associating this address with any named entity, project, exploit, or fraud allegation.","timeline":[]},"v":1}