Write blog entry for 0.100.0 SDK release (#84)

Signed-off-by: David Zeuthen <zeuthen@google.com>

Author: davidz25

blog/2026-07-08-release-0-100-0.md

@@ -0,0 +1,69 @@
+---
+title: "Multipaz 0.100.0 Released"
+description: "Announcing the releases of Multipaz 0.100.0 and a preview of the exciting features it brings!"
+date: 2026-07-08
+---
+
+_Written by [David Zeuthen](https://www.linkedin.com/in/davidz25/), Multipaz project leader._
+
+First off, we owe our community a quick apology: we missed writing a blog post for the Multipaz 0.99.0 release back in May! The team was completely heads-down and fully occupied preparing for the **[France Interop event in La Ciotat](https://france2026.mdoc.online)**. It was an incredibly busy but rewarding experience showcasing real-world digital identity interoperability, and we are absolutely thrilled with how everything went.
+
+But now we're back, and we have not one, but two major releases to share! We launched Multipaz 0.99.0 on May 4, 2026, and Multipaz 0.100.0 on July 8, 2026.
+
+You can check out the full release notes and changelogs on GitHub:
+*   [Multipaz 0.99.0 Release Notes](https://github.com/openwallet-foundation/multipaz/releases/tag/0.99.0)
+*   [Multipaz 0.100.0 Release Notes](https://github.com/openwallet-foundation/multipaz/releases/tag/0.100.0)
+
+As always, you can also find our release artifacts published to [Maven Central](https://central.sonatype.com/artifact/org.multipaz/multipaz). 
+
+In this post, we’re going to highlight a few select features from these two exciting releases!
+
+### ISO 18013-5 Second Edition
+
+We've significantly expanded our support for the upcoming [ISO/IEC 18013-5 Second Edition](https://github.com/ISO-SC17-WG10/ISO-18013), which we've been actively helping to finalize within the ISO/IEC SC17 WG10 committee. This update brings powerful new capabilities to Multipaz, including support for [Alternative Data Element Sets](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.mdoc.request/-alternative-data-element-set/index.html), [Encrypted Documents](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.mdoc.request/-encryption-parameters/index.html), [Document Sets](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.mdoc.request/-document-set/index.html), and [SD-JWT VCs](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.mdoc.response/-other-document/index.html). We also conducted extensive interoperability testing against other implementations, giving us high confidence in both the evolving standard and our robust implementation in Multipaz.
+
+### NFCv2: Speeding Up In-Person Presentment
+
+One of the most exciting, user-visible features in ISO 18013-5 Second Edition is **NFCv2**—a highly optimized version of the [NFC](https://en.wikipedia.org/wiki/Near-field_communication) engagement protocol used when tapping a mobile device against an mdoc reader.
+
+In the first edition of ISO 18013-5, NFC engagement came in two flavors—static and negotiated—and was built on top of [NFC Forum Connection Handover](https://nfc-forum.org/build/specifications/connection-handover-technical-specification/), which in turn relied on [NDEF](https://nfc-forum.org/build/specifications/data-exchange-format-ndef-technical-specification/). While this mechanism works, its layered architecture requires the two devices to complete around 10 communication round-trips just to establish the [Bluetooth Low Energy (BLE)](https://en.wikipedia.org/wiki/Bluetooth_Low_Energy) connection. On typical consumer devices, this translates to a noticeable delay of several hundred milliseconds.
+
+NFCv2 drastically simplifies the exchange of APDUs, saving hundreds of critical milliseconds during the tap to deliver an incredibly responsive experience. When combined with another ISO 18013-5 Second Edition feature—conveying the BLE L2CAP PSM directly in the engagement—presenting an mdoc in person becomes up to **10x faster**!
+
+A video is worth a thousand words. See it in action below:
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/l7Q8EV9zddM" title="NFCv2 in action" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+Notice how the entire presentment takes only ~400 milliseconds—well under the critical 500 ms threshold typically expected for a seamless transaction. We think NFCv2 is going to be a game-changer for Digital Credentials!
+
+### High-Level Verifier APIs & SD-JWT VC Support
+
+We've also been busy crafting high-level verifier APIs perfect for server-side integration. Check out the new **[VerificationSession](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.verification/-verification-session/index.html)** and related types in the **[`org.multipaz.verification`](https://developer.multipaz.org/kdocs/multipaz/org.multipaz.verification/index.html)** package.
+
+These APIs make it incredibly easy to request credentials from wallets using a wide range of protocols, including:
+* ISO/IEC 18013-7 Annex C over the W3C Digital Credentials API
+* ISO/IEC 18013-7 Annex A over the custom URI scheme `mdoc://`
+* OpenID4VP 1.0 over the W3C Digital Credentials API
+* OpenID4VP over the custom URI scheme `haip-vp://`
+
+This means websites can now request credentials from multiple different wallets, even if they implement completely different transport protocols and formats. The APIs fully support both ISO mdoc and SD-JWT VC-based credentials.
+
+You can try this out live at the [Multipaz Verifier demo](https://verifier.multipaz.org/light.html). If you need a test wallet, you can also grab the latest APKs for the [Multipaz TestApp](https://apps.multipaz.org) or [Multipaz Wallet](https://apps.multipaz.org) directly from our [apps portal](https://apps.multipaz.org).
+
+Check out this video showing all of these capabilities working together in harmony:
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/RTeNGukp26g" title="SD-JWT VC via ISO 18013-5 Second Edition" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+In this video, a verifier's mdoc reader communicates with a wallet using NFC for engagement and BLE for data transfer. The request sent from the reader is for identification, allowing the holder to present one of several document types, including a Mobile Driving License (mDL), an EU PID in mdoc format, an EU PID in SD-JWT VC format, an Aadhaar credential, a Photo ID, or a Google Wallet ID Pass ([source code](https://github.com/openwallet-foundation/multipaz-wallet/blob/main/shared/src/commonMain/kotlin/org/multipaz/wallet/client/verification/IdentificationDoumentQuery.kt)).
+
+You'll see the holder choose to return the EU PID, and on the reader side, the operator receives and displays the credential details—demonstrating that an SD-JWT VC was successfully transmitted over the BLE connection used for the ISO 18013-5 Second Edition transaction. Pretty sweet!
+
+### What's next?
+
+Beyond the core [Multipaz SDK](https://github.com/openwallet-foundation/multipaz), we've been busy driving several exciting initiatives across the broader Multipaz project, including exploring how Multipaz can be used for **[Agentic use cases](https://developer.multipaz.org/docs/agentic)**, as well as starting to build out a [playground of issuers and relying parties](https://github.com/openwallet-foundation/multipaz-utopia). Additionally, the application shown in the videos above is the new [Multipaz Wallet](https://github.com/openwallet-foundation/multipaz-wallet)—a project we kicked off just a couple of months ago!
+
+While we want the core SDK to remain [boring, stable, and predictable](https://mcfunley.com/choose-boring-technology), the Multipaz Wallet effort is a different beast: an active playground to showcase our SDK, experiment with cutting-edge features (like [link-based verification](https://youtu.be/JIFkuSvviqk) and account-bound credentials), [run the entire Multipaz SDK in-browser for a "web wallet"](https://github.com/openwallet-foundation/multipaz-wallet/tree/main/webApp), and try out other ideas. Remarkably, a huge chunk of it is being built by **[Antigravity](https://antigravity.google/)** and other AI tools! We can't wait to share more about these experiments in future blog posts.
+
+But shifting our focus back to the core SDK: the team recently aligned on our roadmap, and our official plan of record is to reach **1.0.0** around Q4 2026, depending on the time needed to get the codebase fully in shape for this important milestone! With our steady 6-to-8 week release cadence, the 1.0.0 milestone will likely follow a few more 0.x.0 releases, and then it will be time for the big 1.0.0 release. This is also the perfect time to remind everyone that Multipaz is a fully open-source project, and we warmly welcome contributions from both existing downstream users and new contributors alike! The team meets every Tuesday—check out the [OWF community calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/openwalletfoundation?view=week) for details if you want to get involved.
+
+Parallel to the 1.0 roadmap, we are actively participating in the **[DCHP (Digital Credentials Harmonized Presentation)](https://openid.net/wg/digital-credentials-harmonized-presentation-working-group/)** working group and plan to implement early drafts into Multipaz for interoperability testing with other early adopters, routing feedback back to the standards organizations—just like we've done with ISO 18013-5 and OpenID4VP. We are also prioritizing support for [OpenID4VCI server-to-server](https://github.com/openid/OpenID4VCI/issues?q=state%3Aopen%20label%3A%22server-to-server%22) issuance flows and, of course, we'll continue contributing to the ISO/IEC SC17 WG10 and OpenID DCP working groups.