EUDI wallet issuance, not certified, not recognised, and gated on a partner we do not have

Solidus does not ship a wallet that is EUDI-certified, and no Member State recognises anything we issue. We hold no eIDAS qualified trust service provider status: it is a 2027 target, contingent on chaining through a partner, and no such partnership exists. Nothing here is legal advice.

The distinction the whole page is about

Sharing a data format with the EU framework is not the same as being part of it, and the two get merged constantly, usually by vendors, and usually in their own favour.

• Format compatibility means our credentials use specifications the EU framework also uses. It is a technical fact, and it is true of us.
• Recognition means a Member State, or a verifier operating under the regulation, will accept what you issue. It is a legal and accreditation fact, and it is not true of us.

A credential can be perfectly well-formed and carry no legal weight whatsoever. That is exactly our position.

What the EU framework actually requires

The framework rests on accredited parties, not on well-formed JSON:

• A certified wallet. Wallets are provided or certified under Member State schemes and conform to a published architecture and reference framework. Ours is not one of them and has not been submitted to any conformance process.
• Qualified trust service providers. Certain services carry legal effect only when performed by a QTSP, a status granted by a Member State supervisory body after audit. We hold none, in any Member State.
• Person identification data issued under national schemes, with a chain of accountability back to a state. We are not in that chain.

The reference wallet code and architecture documents are public and runnable at github.com/eu-digital-identity-wallet. There is nothing of ours to run against them, and that absence is the honest point.

Where Solidus Identity fits, which is beside this rather than inside it

Solidus Identity is a separate product, a did:solidus-based credential wallet with no relationship to the EUDI specification. It is not a candidate wallet, has not been submitted for certification, and holding a Solidus credential in it confers nothing under the regulation.

A Solidus-issued credential could in principle be wrapped for presentation to a conformant verifier, but only through a partner that already holds QTSP status. That is the whole path, and it starts with a partnership we do not have. We cannot grant ourselves that status, exactly as with Turkish licensing and Law 6222: the barrier is accreditation, not engineering.

And a native holder wallet is still roadmap

A native, hardware-key-bound Solidus holder wallet (the kind of key protection a certified wallet is expected to demonstrate) is roadmap, not shipped.

So even the technical precondition, before any accreditation question, is unmet.

What we would say to a buyer betting on EU alignment

If your requirement is a wallet or a trust service with legal effect in the EU, we fail it completely, and there is no partial credit to offer.