← 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE3 decisions on this page
Audit log
Every state-changing event for 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-08-07 23:28:14ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 443,504,868
- sig
5bRzhDTMT2pC…PZg16PHoexplorer ↗- hash
9B8Ggq1EKkrf…44Cwj6Rzsha256 → base58
verifying row…full verify ↗canonical bytes (8327 B) ▸
{"actor":"system:backfill","investigation_id":"af4b83b2-f0cf-4a10-835e-9210b2b08166","kind":"publish","page_slug":"0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe","published_at":"2026-08-07T23:28:14.354Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE","sections":[{"content":"According to Etherscan, the address holds a balance of 0 ETH and has recorded no incoming or outgoing transactions. The account type is an externally owned account (EOA), meaning it is not a smart contract. Ethplorer similarly returns no transaction history, token transfers, or token balances for this address. No verified name tags, labels, or community-submitted annotations appear on either explorer. The address has no multichain activity across the 33+ chains supported by Etherscan's portfolio tool. An address with zero transaction history may represent a freshly generated wallet that has never been funded, a vanity address, or an address generated for future use.","heading":"On-Chain Profile","severity":"low","sources":[{"credibility":2,"name":"Etherscan address page: 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE","type":"on_chain","url":"https://etherscan.io/address/0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE"},{"credibility":2,"name":"Ethplorer address page: 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE","type":"on_chain","url":"https://ethplorer.io/address/0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe"}]},{"content":"The address was checked against the OFAC Specially Designated Nationals (SDN) list via the community-maintained repository that extracts and publishes sanctioned digital currency addresses nightly from official OFAC XML data. The address 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE does not appear in the current sanctioned Ethereum address list. The OFAC SDN list as of 2026 contains over 1,200 cryptocurrency addresses spanning Bitcoin, Ethereum, Tron, and other chains, targeting entities including North Korean state-sponsored hacking groups, Iranian financial networks, Sinaloa Cartel money laundering networks, and ransomware operators. No match was found for this address.","heading":"OFAC Sanctions Status","severity":"low","sources":[{"credibility":1,"name":"OFAC Sanctioned Digital Currency Addresses (0xB10C/ofac-sanctioned-digital-currency-addresses) — ETH list","type":"regulatory","url":"https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses"},{"credibility":1,"name":"OFAC Sanctions List Search (official)","type":"regulatory","url":"https://sanctionssearch.ofac.treas.gov/"},{"credibility":2,"name":"Chainalysis OFAC Sanctions Tracker","type":"research","url":"https://www.chainalysis.com/blog/ofac-sanctions/"}]},{"content":"A search of ChainAbuse, TRM Labs' multi-chain scam reporting platform, returned no abuse reports for this address. No results were found across web searches combining the address with terms such as 'scam', 'fraud', 'hack', 'phishing', 'rug pull', or 'complaint'. The California DFPI Crypto Scam Tracker, FBI IC3 resources, and general news outlets returned no mentions of this address. The absence of reports on ChainAbuse does not constitute a clearance, as many illicit addresses are never publicly reported.","heading":"Abuse and Scam Reports","severity":"low","sources":[{"credibility":2,"name":"ChainAbuse — address lookup","type":"community_report","url":"https://www.chainabuse.com/address/0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE"},{"credibility":2,"name":"TRM Labs — Chainabuse platform overview","type":"research","url":"https://www.trmlabs.com/resources/blog/announcing-the-launch-of-chainabuse-the-multi-chain-scam-reporting-tool-that-empowers-crypto-users-against-fraud"}]},{"content":"Searches of SEC EDGAR, DOJ press releases, and general regulatory databases returned no results referencing this Ethereum address. No court filings, indictments, civil complaints, or enforcement actions mentioning this address were identified. No connection to named regulatory targets was established through any available open-source intelligence.","heading":"Regulatory and Law Enforcement Records","severity":"low","sources":[{"credibility":1,"name":"SEC.gov — Investigative Summaries and Press Releases","type":"regulatory","url":"https://www.sec.gov/office-inspector-general/reports-publications/investigative-summaries-press-releases-reports"}]},{"content":"Arkham Intelligence, which deanonymizes blockchain addresses by linking them to known entities, returned no publicly accessible label or entity attribution for this address based on available search results. No named exchange, protocol, fund, or individual has been publicly linked to this address through Arkham or other on-chain intelligence providers including Chainalysis and TRM Labs. The address carries no publicly known ENS (Ethereum Name Service) name.","heading":"Entity Attribution and Intelligence Labeling","severity":"low","sources":[{"credibility":2,"name":"Arkham Intelligence — Ethereum explorer","type":"on_chain","url":"https://intel.arkm.com/explorer/token/ethereum"}]},{"content":"This investigation is constrained by the complete absence of on-chain activity for this address, which limits the applicability of transaction graph analysis, counterparty clustering, or heuristic-based risk attribution. The address may become active in the future, at which point its risk profile would need to be reassessed. Additionally, proprietary blockchain analytics tools (Chainalysis Reactor, TRM Labs Forensics, Elliptic Lens) were not directly queried and may hold non-public intelligence. The trust score of 50 reflects maximum uncertainty: no evidence of risk was found, but no evidence of legitimacy or established use was found either. A score of 50 is the appropriate neutral baseline for an address with no verifiable history.","heading":"Investigative Limitations","severity":"low","sources":[]}],"sources_used":[{"credibility":2,"name":"Etherscan — 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE","type":"on_chain","url":"https://etherscan.io/address/0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE"},{"credibility":2,"name":"Ethplorer — 0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE","type":"on_chain","url":"https://ethplorer.io/address/0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe"},{"credibility":2,"name":"ChainAbuse — address lookup","type":"community_report","url":"https://www.chainabuse.com/address/0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE"},{"credibility":1,"name":"OFAC Sanctioned Digital Currency Addresses — GitHub (0xB10C)","type":"regulatory","url":"https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses"},{"credibility":1,"name":"OFAC Sanctions List Search (official Treasury tool)","type":"regulatory","url":"https://sanctionssearch.ofac.treas.gov/"},{"credibility":2,"name":"Chainalysis OFAC Sanctions Tracker","type":"research","url":"https://www.chainalysis.com/blog/ofac-sanctions/"},{"credibility":2,"name":"TRM Labs — Chainabuse platform announcement","type":"research","url":"https://www.trmlabs.com/resources/blog/announcing-the-launch-of-chainabuse-the-multi-chain-scam-reporting-tool-that-empowers-crypto-users-against-fraud"},{"credibility":2,"name":"Arkham Intelligence — Ethereum explorer","type":"on_chain","url":"https://intel.arkm.com/explorer/token/ethereum"},{"credibility":2,"name":"Tatum OFAC Sanctioned Wallet Tracker","type":"regulatory","url":"https://apps.tatum.io/ofac-wallet-tracker"}],"summary":"0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE is an Ethereum externally owned account (EOA) with no recorded on-chain transaction history, zero ETH balance, and no token holdings as of August 2026. No verifiable associations with scams, fraud, sanctions, regulatory actions, or illicit activity were found across any checked source; however, the absence of on-chain history and public intelligence makes a definitive trust assessment impossible.","timeline":[{"date":"2026-08-07","event":"Address investigated by AVOID.NET. No on-chain transactions, no OFAC designation, no abuse reports, and no regulatory actions found. Address appears dormant or unused.","source":"AVOID.NET investigation (Etherscan, ChainAbuse, OFAC SDN list, Arkham Intelligence, open-source search)","source_url":"https://etherscan.io/address/0xdF8C3A7FFbdC144f462687120E4AE4C4e5E55abE"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 3c9ff267-7463-4004-9647-c44a434cfe88 - #2reviewby reviewerreviewer2026-08-25 22:35:40ZScore: 50 → 50 (no score change)The page's core factual claims -- that the address is an unused Ethereum EOA with zero balance, zero transaction count, no OFAC sanction match, no abuse reports, no regulatory filings, and no public entity attribution -- were independently re-verified via direct JSON-RPC calls, the Ethplorer public API, the live OFAC sanctions list, and SEC EDGAR full-text search, and all matched the page's description as of the review date. Critically, the page does not attribute the address to any named person, group, or campaign, and no such attribution could be found anywhere in public search, so the specific false-attribution risk flagged for this review was not found. One minor supporting detail (the '33+ chains' figure for Etherscan's portfolio tool) is an approximation that could not be precisely pinned down, and one minor detail (absence of an ENS reverse record) could not be independently confirmed with the tools available.anchoranchored
- chain
- ●mainnet-betaslot 443,517,779
- sig
PbfvDRbYdYmA…Jv2EXUiHexplorer ↗- hash
68fHb7geTJp1…SBYGrAdPsha256 → base58
verifying row…full verify ↗canonical bytes (1308 B) ▸
{"actor":"reviewer","decided_at":"2026-08-25T22:35:40.191Z","decision":"review","investigation_id":"af4b83b2-f0cf-4a10-835e-9210b2b08166","new_score":50,"page_slug":"0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe","prev_score":50,"reason":"The page's core factual claims -- that the address is an unused Ethereum EOA with zero balance, zero transaction count, no OFAC sanction match, no abuse reports, no regulatory filings, and no public entity attribution -- were independently re-verified via direct JSON-RPC calls, the Ethplorer public API, the live OFAC sanctions list, and SEC EDGAR full-text search, and all matched the page's description as of the review date. Critically, the page does not attribute the address to any named person, group, or campaign, and no such attribution could be found anywhere in public search, so the specific false-attribution risk flagged for this review was not found. One minor supporting detail (the '33+ chains' figure for Etherscan's portfolio tool) is an approximation that could not be precisely pinned down, and one minor detail (absence of an ENS reverse record) could not be independently confirmed with the tools available.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 80221702-13f7-4241-801d-0a5d754748d0 - #3review approveby judgejudge2026-08-25 22:35:40ZScore: 50 → 50 (no score change)The reviewer's claim_findings array contains 12 entries (the review's own summary block undercounts by one, but the array itself is complete): 10 confirmed, 1 partially_supported, 1 unverifiable, 0 disputed. Per the disputed_pct formula (disputed + unverifiable) / total, that is 1/12, about 8.3%, which falls in the approve band regardless of whether the summary's stated total of 11 or the array's actual total of 12 is used. Every core factual claim -- zero balance, zero transaction count, EOA status, no OFAC match, no ChainAbuse reports, no SEC/DOJ hits -- was independently re-verified by the reviewer via direct RPC calls, the live OFAC list, and SEC EDGAR full-text search, and all held (claim_findings[0], [2], [4], [6], [7]). Most importantly, the page's attribution section was checked specifically for false or premature attribution to a named party, and none exists: claim_findings[8] confirms the page correctly states no named exchange, protocol, fund, or individual is linked to this address, and independent search corroborated that no such attribution exists anywhere publicly. That is the single highest-stakes risk category for a bare-address page, and it is clean. The two non-confirmed items are minor and non-substantive: claim_findings[3] flags an approximate '33+ chains' figure versus sources describing '30+', a low-materiality supporting detail; claim_findings[9] on the absence of an ENS name is unverifiable because the reviewer's lookup tool returned an inconclusive empty response, which reads as a limitation of the review's tooling rather than a defect in the page's claim. No high-priority coverage gaps were reported. Given all this, the page holds up and does not require revision or delisting.anchoranchored
- chain
- ●mainnet-betaslot 443,517,783
- sig
4ZBn4bfw8vWU…GdNysMnNexplorer ↗- hash
51no5L5Y86Uf…7tu5zX7Ssha256 → base58
verifying row…full verify ↗canonical bytes (2115 B) ▸
{"actor":"judge","decided_at":"2026-08-25T22:35:40.191Z","decision":"review_approve","investigation_id":"af4b83b2-f0cf-4a10-835e-9210b2b08166","new_score":50,"page_slug":"0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe","prev_score":50,"reason":"The reviewer's claim_findings array contains 12 entries (the review's own summary block undercounts by one, but the array itself is complete): 10 confirmed, 1 partially_supported, 1 unverifiable, 0 disputed. Per the disputed_pct formula (disputed + unverifiable) / total, that is 1/12, about 8.3%, which falls in the approve band regardless of whether the summary's stated total of 11 or the array's actual total of 12 is used. Every core factual claim -- zero balance, zero transaction count, EOA status, no OFAC match, no ChainAbuse reports, no SEC/DOJ hits -- was independently re-verified by the reviewer via direct RPC calls, the live OFAC list, and SEC EDGAR full-text search, and all held (claim_findings[0], [2], [4], [6], [7]). Most importantly, the page's attribution section was checked specifically for false or premature attribution to a named party, and none exists: claim_findings[8] confirms the page correctly states no named exchange, protocol, fund, or individual is linked to this address, and independent search corroborated that no such attribution exists anywhere publicly. That is the single highest-stakes risk category for a bare-address page, and it is clean. The two non-confirmed items are minor and non-substantive: claim_findings[3] flags an approximate '33+ chains' figure versus sources describing '30+', a low-materiality supporting detail; claim_findings[9] on the absence of an ENS name is unverifiable because the reviewer's lookup tool returned an inconclusive empty response, which reads as a limitation of the review's tooling rather than a defect in the page's claim. No high-priority coverage gaps were reported. Given all this, the page holds up and does not require revision or delisting.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision b4e44c1f-27fd-4c91-b861-ee2fb54c803a
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.