1 of 9

Dr. Torsten Lodderstedt | CTO | yes.com

Juliana Cafik | Principal Standards Architect | Microsoft

Hart Montgomery | CTO, Hyperledger Foundation | Linux Foundation

​

     �

Open Wallet Foundation

�

1

2 of 9

Introduction to the OWF

���The purpose of the Open Wallet Foundation is to support various open source, open data and/or other projects relating to, or supporting the development of, interoperable digital wallets, including infrastructure and support initiatives.

​

The concept behind the OWF is to create an open-source community that works together to blend different skill sets to build fundamental, standards-based technologies for multipurpose wallets.

​

Currently there are over 300 entities expressing interest in joining.

​

​

��

2

3 of 9

Umbrella Project Structure

  • Do-ocracy: Fundamental proposal for the OWF to do the projects that members are willing to contribute the resources necessary to complete a project;
  • Self-Organization: members self-organize “Code Projects” and associated working groups (where necessary) to propose a Code Project;
  • Members have expressed interest already to contribute resources for these initial building blocks/credential types (based on the EUDI wallet as reference point) - OWF Use Case Interest - Google Sheets: 
  • Code Project proposals will be required to follow (to be agreed) principles/requirements (e.g. security, privacy, interoperability), detail the requirements, the standards on which they are based, and what functions they plan to share with other projects
  • Code Projects will go through a defined lifecycle.

�

3

4 of 9

Proposed Requirements

  • REQ 1: Provision building blocks for multi-purpose wallets. Note: The current building blocks represent multiple purposes;

​

  • REQ 2: Enable access those building blocks with a single login and through a consistent UX;

​

  • REQ 3: Present different credentials from different building blocks in the course of the same transaction; 

​

  • Assumption: REQ 1-3  lead to the following shared functions (common core): 

- shared key management allowing to unlock the keys with for all credentials for a single login

- shared credential management allowing to unlock/decrypt the credentials with a single login

- shared protocol building blocks utilizing available credential building blocks to present credentials

�

4

5 of 9

Shared Code Across Platforms?

  • Do the proposed requirements necessitate that shared building blocks are shared across platforms (like iOS or Android or Cloud)?
  • Assumption: sharing required in wallet on a certain platform, not across platforms, as a certain user’s wallet will run on a certain platform and not several of them;

​

​

​

​

​

​

​

​

  • Decisions will be dependent on source code contributions;
  • The OWF provides an opportunity to join forces and share cost to make building wallets with a competitive user experience and access to platform services more affordable.

​

�

Shared Code

​

+ Cost efficient

  • New programming language?
  • Stability?
  • Platform abstractions required?
  • Potential upfront investment

Platform Native Code

​

+ Use of platform native programming languages (e.g. Swift / iOS & Kotlin / Android)

​

+ Use of platform capabilities

(e.g secure enclave, key chain & NFC)

5

6 of 9

Umbrella Project Lifecycle

  • LF umbrella projects by definition are collaborations among multiple individual projects, some of them have developed processes (and in some cases tools) to facilitate this. For example, the Hyperledger Foundation’s Project Lifecycle process defines six stages in the completely lifecycle of a project as summarized in the diagram;

​

  • It is proposed that a similar six-stage process for OWF projects be defined, and in particular that we establish the combination of maturity, interoperability, security, privacy, and other requirements that a component project must meet to “graduate” and become part of the Open Wallet distribution.

​

6

7 of 9

Foundations for Interoperability

  • To support different member-proposed standard credential types the OWF must develop a common core that lays the foundation for interoperability and inclusivity; 

​

  • To achieve whole product interoperability — the level required for OWF-based wallets to be accepted by governments and regulatory regimes around the world is high and will require the common core to solve for interop at four different layers:

​

    • Legal: Governance for the interoperability of credentials, systems and the management of identity and access rights across multiple applications and services to meet regulatory and security requirements;
    • Business: Alignment of business processes, responsibilities and expectations to achieve commonly agreed and mutually beneficial goals;
    • Semantic and syntactic: The ability of two or more systems to exchange data even if the interface and programming languages are different;
    • Protocol / Technical: The ability of different systems devices, applications or products to connect and communicate in a coordinated way without effort from the end user.

7

8 of 9

Associate Members

  • The experience and expertise of Non-Profit organizations can help guide the Open Wallet Foundation and can increase the opportunities for industry and Governments;
  • As Associate Members, they can participate in many areas including, but not limited to:
      • Trust Framework Awareness, Education and Adoption;
      • International Alignment and Cross Sector Interoperability;
      • Legal and Regulatory Compliance;
      • Technical Standards Conformance.

​

8

9 of 9

Points of Discussion

  1. The Primary objective of the OWF is to produce code, and it must be high-quality, secure, privacy-preserving and standards-based;

​

  • The OWF is built on a group of interdisciplinary people who self-organize and collaborate to build code;

​

  • To move forward the OWF needs Code Projects with code contributions, resources, stated objectives and requirements.

​

9