Current stage and Gaps of Public Beta

The Public Beta environment aims to function as a basis for experimentation and integration efforts conducted by the ecosystem participants from both the public and the private sector. It provides the same technology that will be used by the productive environment in 2026, but with, as of now, reduced maturity and scope. At the moment operation and support of the Public Beta Trust Infrastructure are run on a best effort basis. It is planned to gruadually develop Public Beta into an integration environment that is run in parallel and equivalent to the productive infrastructure from Go-live in 2026 onwards. 

As regards the e-ID, the Public Beta Trust Infrastructure will mimic this credential type through a Beta-ID. Beta-IDs contain the same set of attributes as the e-ID defined in Art. 15 of the BGEID (Bundesgesetz über den elektronischen Identitätsnachweis und andere elektronische Nachweise). However, Beta-ID’s technical features are restricted and the legal requirements defined in Section 3 of the BGEID do not apply.

Roadmap with general overview on GitHub

Our Roadmap on GitHub gives a general overview of the development of the swiyu Public Beta Trust Infrastructure. It includes the closure of existing gaps, new features and the updating of the standards applied. We invite interested parties to subscribe via GitHub discussions or RSS feed to our release announcements to be informed about upcoming changes.

Initial Supported Technical Standards

The following table provides a reference that indicates which standards are currently employed within the swiyu Public Beta Trust Infrastructure. While the Confederation aims to provide a degree of assurance and stability for integrators even at this early stage, evolution seems inevitable. Consequently, set of selected standards will be updated or extended if perspectives within the implementing organizations change. Changes will be considered, especially if they benefit privacy-protection for users, increase the security and stability of the overall system, or if standards converge to serve the purpose of fostering interoperability. We currently differentiate between support for Public Beta and the initial Go-live support.

Aspect Current Hypothesis Public Beta Support Initial Go-live Support
Identifiers Decentralized Identifiers (DIDs) v1.0 according to W3C
DID Method: did:tdw/did:webvh		 SELECTED
Hosted on central base registry provided by Confederation		 SELECTED
Status Mechanisms Statuslist SELECTED SELECTED
Trust Protocol Trust protocol based on VCs SELECTED
Initial support of the “identity” trust statement by Confederation		 HIGH
Additional support of issuer & verifier legitimacy (per VC schema)
Communication Protocol (Issuance/Verification) OID4VC/OID4VP
Issuance
Verification		 SELECTED
In accordance with Swiss profile		 SELECTED
Payload Encryption JWE as proposed by the communication protocol SELECTED SELECTED
VC-Format/Signature-Scheme Combination SD-JWT VC & ECDSA SELECTED
In accordance with Swiss profile		 SELECTED
Device Binding Scheme Hardware based device binding depending on capabilities provided by Apple or Android mobile devices
Software based device binding implemented by wallets		 Hardware SELECTED
Software UNSUPPORTED		 Hardware SELECTED
Software SELECTED
VC appearance Visualization of Verifiable Credential with OCA SELECTED SELECTED

Probability interpretation:

  • UNSUPPORTED = No Solution provided,
  • OPEN = Options are being assessed,
  • CANDIDATE = Standard/Specification is in selection,
  • HIGH = Current hypothesis for implementation,
  • SELECTED = Chosen for system

The versions of the referenced specifications may change. In particular, the e-ID program is planning to upgrade most of the implemented specifications to newer and more mature versions until the Go-live.