LVCS Registry
The public registry of products and platforms that have passed a CCSA assessment for their segment and level. An analog of the PCI Validated Products List.
LVCS (Listed Validated Crypto Solutions) is the Council’s public registry of products and platforms that have passed a CCSA assessment. A listing grants the right to use the CCSA Badge with its level. Each entry carries a public AOC summary; the full ROC stays confidential.
For buyers of crypto solutions the registry is an objective way to pick a certified vendor and cut due-diligence cost. For regulators it is a ready pre-vetted list. For a vendor it is the main marketing asset of certification.
LVCS lists exactly the four normative segments C.1–C.4. HSM/MPC tooling is checked inside its segment via B.3.1 / B.4.1, not as a separate category. Blockchain analytics, smart-contract audit tools and cross-chain bridges are out of CCSA scope (Section 0.2.2) and are not listed.
Draft v0.2 -> v1.0. Subject to change before 2027-01-01.
LVCS Registry
LVCS registry rows (illustrative)
Registry rows are examples and do not reflect real certifications.
Filter
| ID | Vendor | Product | Segment | Level | Certified | Valid until | Assessor (CCSAC) | Status | Track record |
|---|---|---|---|---|---|---|---|---|---|
| LVCS-2027-0001 | 4pay.online OOO | HethWallet | C.2 | L2 | 2027-03-15 | 2028-03-14 | CCSAC-001 | Active | Clean |
| LVCS-2027-0002 | Acme Custody Ltd | Acme Vault | C.1 | L3 | 2027-06-01 | 2028-05-31 | CCSAC-002 | Active | Clean |
| LVCS-2027-0003 | RegioToken LLC | RegioCoin Issuer | C.4 | L2 | 2027-09-10 | 2028-09-09 | CCSAC-003 | Pending renewal | Clean |
| LVCS-2026-0004 | DEX Labs | DEXFront | C.3 | L1 | 2026-12-20 | 2027-12-19 | CCSAC-001 | Expired | Under investigation |
Track record is a categorical attribute (no numeric score): Clean / Under investigation / Sanctioned. Only events inside CCSA domains B.1–B.8 are assessed; out-of-scope aspects (PoR, smart-contract audits, bug bounty) are not shown.
How a product gets listed
01
Submit an LVCS Application: product, category, claimed level, ROC reference.
02
The Council verifies the ROC: valid, Lead-Auditor-signed, validity and scope match the claimed level, In-Place ratio and Critical Requirements confirmed. Review takes 5–10 business days.
03
Pay the listing fee.
04
Publication: LVCS Certificate ID, a digital CCSA Badge, and the right to use the CCSA Listed Logo.
Badge usage rules
The badge with its level (Level 1/2/3) on the site and in marketing.
Use in pitch decks and pre-sale materials with an explicit reference to LVCS.
A generic “CCSA Certified” without a level.
Use outside the registered scope, or transfer to another product without a separate certification.
Use after expiry without renewal, and any misleading claims (e.g. “PCI DSS certified” when only CCSA applies).
Incident handling
24h
24 hours: status changes to incident-flagged, the Council contacts the vendor, the attesting CCSAC is re-engaged.
7d
7 days: the vendor files an incident report; the CCSAC runs a targeted re-audit of the affected domains.
30d
30 days: decision — (a) a CCSA-domain failure: suspended until remediation and re-audit; (b) external, out-of-scope cause: flag removed with a registry note; (c) tampered original evidence: termination plus sanctions on the CCSAC.
Scale target
Target listing counts: 2027 about 10–20, 2028 50–80, 2029 150–200, 2030 300–400. A target, not a guarantee.