Assurance
chainscore.net is not ISO 27001 or SOC 2 certified.
The landing logo strip is directory coverage of crypto-asset service providers, not customers and not a security badge. Independent ISMS / SOC reports are not on file. What follows is what this deployment can actually show a reviewer.
- ISO/IEC 27001
- Not certified. No certificate number, issuer or expiry to show.
- SOC 2 / SOC 3
- Not on file. No Type 2 report to share under NDA.
- Trust centre
- This page. Vendor-style badge walls are not reproduced here.
What this deployment can show
-
Cited public labels
519 addresses from 34 source(s). Rows without an https source_url are refused at load.
-
OFAC SDN overlay
943 designated addresses on screened chains, list published 08/28/2026. Designations override curated labels. Refresh with scripts/refresh_sanctions.py.
-
Fail-closed indexers
Alchemy → QuickNode → Blockscout → Etherscan. A dead indexer is HTTP 502, not a clean screen.
-
Coverage gate
A score below the attribution floor cannot auto-clear. Unlabelled counterparties stay unlabelled. Host is never guessed.
-
Artefact integrity
Every stored report carries a SHA-256 and HMAC of its canonical JSON so an export can be checked against what was issued.
-
Isolated score scales
ScoreGuard 1–100 (lower is riskier), ChainTrace 0–100 (higher is riskier), Holistix 0–10. Raw numbers are never merged.
Sanctions data in this build
US Treasury OFAC SDN: 943 designated
addresses on screened chains
(list published 08/28/2026).
UK, EU and UN lists are not ingested: those publications do not publish
structured digital-currency identifiers the way OFAC does, and free-text
scraping would invent hits.
Cited public labels
519 cited public labels from 34 source(s). Each address carries a URL; uncited rows are refused at load.