CD-006 - Trust Protocol 2.0

Trust Protocol 2.0

Status: Released
Published: 13.08.2026
Effective: 19.08.2026
Affected Components: Generic Issuer, Generic Verifier swiyu Wallet
Internal Reference: EIDARTFE-1562, EIDARTFE-1975

The swiyu ecosystem is migrating from Trust Protocol 1.0 (TP1.0) to Trust Protocol 2.0 (TP2.0), following an Expand-Migrate-Contract (EMC) approach. During Expand, TP2.0 is introduced alongside TP1.0 (TP1.0 remains as fallback). During Migrate, all ecosystem participants (Issuers and Verifiers) must switch to TP2.0 only and ensure all DIDs intended for continued use are re-onboarded with TP2.0 trust statements. During Contract, TP1.0 support is removed entirely: the swiyu Wallet will no longer accept TP1.0 trust artefacts, and DIDs that have not been change to did:webvh during onboarding will be rejected. Integrators who take no action risk their DIDs, VCs, and endpoints being rejected once the Contract phase begins.

Action required

Tag ⚠️ Required soon Tag 🚨 Breaking Tag 🆕 Optional Tag ✅ Improvement Tag 🐞 Fix

Wallet

⚠️ From 19.08.2026 (subject to app store reviews, Wallet 1.17.x, enforced): TP2.0 support is introduced alongside TP1.0; TP1.0 continues to work as a fallback during the Migrate phase, no action required yet beyond updating to 1.17.x.
🚨 From the Contract phase (Wallet 2.x.x, ~November 2026, exact date tba): the Wallet will no longer accept TP1.0 trust artefacts. All DIDs consumed by the Wallet must be trust-onboarded with TP2.0 before this date, or they will be rejected.
🚨 From the same milestone pinning environments to PROD for PROD apps and allowing only trusted issuers/verifiers on PROD. As a consequence, a Prod Wallet will no longer work against Sandbox environments.

Generic Issuer

⚠️ Ecosystem participants must be running Generic Issuer 4.x.x during the Expand phase (already required as a consequence of CD-002 and CD-004).
🚨 Upgrade to Generic Issuer 5.x.x (Migrate phase, ~September 2026, exact date tba): remove all usage of TP1.0 and old endpoints; switch to TP2.0 only.

Generic Verifier

⚠️ Ecosystem participants must be running Generic Verifier 4.x.x during the Expand phase (already required as a consequence of CD-002 and CD-004).
🚨 Upgrade to Generic Verifier 5.x.x (Migrate phase, ~September 2026, exact date tba): remove all usage of TP1.0 and old endpoints; switch to TP2.0 only.

Ecosystem / Integrators

⚠️ Ensure all DIDs that shall continue to be used obtain new TP2.0 trust statements / onboarding before the deadline for ecosystem migration (~end of October 2026, exact date tba). DIDs that are not trust-onboarded with TP2.0 will no longer be accepted by the swiyu Wallet. If parallel use of old and new VCs is needed, please create an issue via GitHub.
⚠️ Onboard with a new did:webvh if not already done. (Check your DIDLog). Where possible, re-issue old VCs (old VCs can not be used anymore).
🆕 Shift usage and issuance to the swiyu Sandbox wallet Android see assets and iOS if not already done, to validate the TP2.0 migration ahead of the Contract phase (see CD-001).

Migration steps

Upgrade to Generic Issuer & Verifier 4.x.x (Expand phase, already required via CD-002/CD-004).
Update Wallet to 1.17.x (expected from 19.08.2026), introduces TP2.0 support alongside TP1.0.
Onboard all DIDs intended for continued use with new TP2.0 trust statements.
Onboard with a new did:webvh if not already done; Where possible, re-issue old VCs (old VCs can not be used anymore).
Upgrade to Generic Issuer & Verifier 5.x.x (Migrate phase): remove all TP1.0 usage and old endpoints, switch to TP2.0 only.
Shift usage/issuance to the Sandbox wallet if not already done, to validate readiness.
Complete all TP2.0 onboarding before the deadline for ecosystem migration.
From the Contract phase: remove all TP1.0 support and old endpoints (Wallet, Registries); TP1.0 trust artefacts are no longer accepted.

Timeline

2026-08-19 (subject to app store reviews) Wallet 1.17.x (enforced), TP2.0 support introduced alongside TP1.0; TP1.0 as fallback. Expand phase begins.
2026-09 (tba) Generic Issuer & Verifier 5.x.x available, TP1.0 and old endpoints removed, TP2.0 only. Migrate phase begins.
2026-09 to 2026-10 (tba) Ecosystem migrates to Generic Issuer & Verifier 5.x.x; DIDs re-onboarded with TP2.0 trust statements.
2026-10 (tba) Deadline for ecosystem migration, all DIDs must be TP2.0 trust-onboarded.
2026-11 (tba) Contract phase begins: Wallet 2.0? removes TP1.0 support. Wallet no longer accepts TP1.0 trust artefacts; Prod Wallet no longer works against Sandbox.