Where proof beats "trust me".
Sorcha fits domains where multiple parties must share data they each need to trust, under regulation that won't accept an operator's word for it.
Government-aligned identity
eIDAS 2 requires every EU state to offer a wallet by December 2026 The same standards the EU Digital Identity Wallet and GOV.UK Wallet are converging on — OpenID4VCI, OpenID4VP and the High Assurance Interoperability Profile — are the ones Sorcha implements. Sorcha is the workflow and verifier layer above these government wallets, not a replacement for them: it issues credentials a citizen can hold in a compliant wallet, and verifies presentations back.
Digital Product Passports
First mandatory DPP — the Battery Passport — required from 18 February 2027 (EU Battery Regulation 2023/1542) A product passport must stay tamper-evident, multi-party and selectively disclosed across a supply chain, and verifiable for the life of the product. Sorcha is the proof substrate underneath a DPP platform: signed, Merkle-chained lifecycle records with post-quantum signatures for the decades a product may last. It complements DPP platforms rather than competing with them.
AI-decision audit trails
EU AI Act high-risk obligations apply from 2 August 2026 (Reg. (EU) 2024/1689, Articles 10 & 12) High-risk AI systems must document the provenance of their data and log their operation automatically. Sorcha's signed, immutable register entries are exactly the kind of record an auditor needs: every input traceable to who asserted it, every state change recorded and verifiable.
SME trade finance
Enabled by the UK Electronic Trade Documents Act 2023 / MLETR A buyer's wallet signature on an invoice is the trust anchor for a lender — no intermediary needs to vouch for the data, and no blockchain token is required. A supplier presenting verifiable credentials gives a financier evidence they can check directly, lowering the cost of establishing trust.
An example workflow
Sorcha ships an end-to-end Assured Identity example: an organisation issues an identity credential, a citizen holds it in the Sorcha Wallet, and a relying party verifies a presentation — the full issue → hold → present → verify loop. It is a demonstration of the platform, not a production deployment.