Customer release status

Shipping in LINK v0.10.2; core, both SDKs and Android wallet landed on interop branches post-tag, pending live hardware exchange (iso-rs event matrix still flags it as a gap).

Event-only, semver-exempt implementation checked against the actual ISO/IEC DIS 18013-5 edition 2 ballot text (PDF dated 2025-11-06), with later proposals applied narrowly: N2885 NFCv2 and N2933 SD-JWT. Includes edition detection, issuer identifiers, alternative elements, use cases/document sets, multi-document requests/results, response encryption, and request views. A focused application-layer wallet-to-verifier suite passes 120 tests with no failures across the 2021, edition-2 and TS 18013-7 targets; two Annex B gaps remain explicitly ignored. oneproof-verify exposes edition-2 options through /v1/mdoc/proximity/request; Android and iOS remote engines pass the same edition policy and options used by their offline engines. The iOS holder supports automatic detection plus a single-mDL baseline and fails closed for unsupported advanced requests; the Android event holder remains the implementation for advanced wallet profiles. Reader Auto remains 2021 for ambiguous/2021 engagements and never silently downgrades a standards-significant option. Physical and independent-implementation tests remain pending. N2549/N2718 are CD lineage, not the DIS.

N2885 APDU/DO53 wire; reader + Android holder on event branches. oneproof-verify now accepts exact NFCv2 HandoverSelect/HandoverRequest bytes, builds the edition-2 SessionEstablishment, and retains crypto state; both SDK remote engines are wired while APDU transport remains native. A live physical staging exchange is still pending. iOS supports verifier/reader NFCv2 only; iOS wallet tag emulation is not available.

HPKE Base P-256 request/emission/decryption paths exist. The automated wallet-to-verifier loop covers request, wallet emission, reader decryption, request-ID binding and tamper rejection. oneproof-verify generates and retains the response-encryption key for QR and NFCv2 sessions, supports latest_accepted and explicit dis_2025 transcript profiles, normalizes encryptedDocuments, and returns applied/docRequestIds evidence. Android and iOS remote engines pass options and surface the result; offline event paths remain available. A real Photo ID exchange and transport matrix remain cross-vendor/device tests.

haip-vp://, signed JAR, encrypted responses. In core interop tag; verify-api, Android SDK and Android wallet facades on interop branches; not exposed on iOS. Annex D Draft 3 (N2648) in standards library.

HAIP-Final semantics over openid4vp://, x509_hash client-id, request_uri_method=get, DCQL-only, SD-JWT VC permitted. verify-api interop branch. German trust anchors and test-wallet access still blocked on RP onboarding.

Core issuance, selective disclosure, KB-JWT verification, and event carrier parsing are implemented. N2933 proximity wire uses docFormat dc+sd-jwt plus mandatory docRequestIds and request/session-derived aud + nonce. oneproof-verify verifies otherDocuments against configured SD-JWT trust anchors, and both SDK remote result contracts preserve those reports. Android event wallet can emit single or mixed mdoc/SD-JWT responses. Live event validation remains pending; production offline behavior is unchanged.

OpenID4VCI 1.0 Final is implemented on interop branches. mdl-core exposes real metadata, by-value/by-reference offers, pre-authorized and authorization-code+S256-PKCE grants, nonce, JWT proof and trusted key-attestation validation, single-use state, and bound mso_mdoc/dc+sd-jwt credential issuance. Android and iOS SDK wallet facades and both wallet apps implement byte-preserving offer import. Android on-device Geneva imports have been observed; presenting those exact stored credentials to the OneProof verifier, duplicate/default-mDL policy, deletion UX, and iOS live issuance/presentation still require recorded device tests. Optional deferred issuance, notifications, PAR and DPoP are not advertised. Production issuance and the offline production SDK default remain unchanged.

Published installation and issuance protocol. The interop issuer implements strict MCD/SAAO capability validation, dehydrated and batch IssuerSigned structures, deterministic hydration, the plaintext/encrypted exclusive choice, and Annex H HPKE identifiers. OpenID4VCI currently returns full IssuerSigned credentials, which the protocol permits; dehydrated batch issuance is not advertised. This is not yet a production endpoint claim.

Core parses and signature-verifies VICAL, validates the signer path to an explicitly supplied root, supports verify-then-swap replacement, and applies runtime IACA anchors on proximity and UniFFI paths. The newest supplied Geneva VICAL verifies against the supplied Trusted Lists Root CA and has a regression test. Verify API receipts now reach both SDK remote result contracts without changing offline behavior. Daily freshness refresh and live event testing remain required.

DIS Annex F / N2718 lineage. Core signature-verifies RICAL through a bounded leaf-first signer path to an explicitly supplied root, then separately reports whether presented ReaderAuth chains to a CA in the loaded RICAL; applications must require both. The newest supplied Geneva RICAL verifies against the supplied Trusted Lists Root CA. Full RFC 5280 policy/path processing and revocation are not implied. SDK event variants and Android wallet display are wired; live cross-vendor ReaderAuth remains required.

Core trust-verifies both identifier and status-list COSE/CWT tokens. Status-list validation binds the MSO URI to CWT subject, verifies ES256/x5chain to the Geneva IACA, requires DIS bits=1, caps ZLIB expansion, and evaluates the LSB-first index; the supplied all-valid Geneva token passes. oneproof-verify accepts one configured identifier or status token, preserves revoked/not_revoked/unknown distinctly, and both SDK remote mappers now expose the same verdict as offline. The supplied CWT omits DIS-mandatory exp, accepted only by debug/explicit event builds; ordinary production rejects it. Live server testing and multi-list/fetch/cache support remain pending.