Homepage

What is the Playground?

The playground is a collaborative environment used to support testing and integration of partners within the Potential project. It allows partners to interact with systems and applications, conduct tests, and validate information exchange processes. With continuous integrations, it aims to enhance communication and track developments with a focus on continuous improvement.

The goal of the playground is to promote smooth interoperability between partners by providing necessary resources such as testing environments and reporting tools to standardize processes across partners.

What are the main purposes of the Playground?

Test interoperability

Provide a functional platform to test the interoperability of wallets and use cases

Pictogrammes DSFR — System — Success

Integrate test interfaces from stakeholders

We expect the playground to outlast POTENTIAL as a global interop testbed for all stakeholders

Pictogrammes DSFR — Digital — In Progress

Provide reglementation feedback

Provide field feedback for the ARF and EUDIW reference implementation

Pictogrammes DSFR — Leisure — Community

What is a test interface?

A stub is a technical component that simulates a specific environment or service to allow partners to test and validate the interoperability of their systems before full integration. It is a simplified version of a service or interface that mimics the behavior of a real service but does not necessarily handle all functionalities or processes.

Interfaces enable Playground participants to test different implementations or features by simulating interactions with other entities without requiring that all parties be fully set up. Interfaces are used to facilitate the testing process before moving to real tests, particularly in the context of validating systems through peer-to-peer testing, thus ensuring the interoperability and compliance of different systems within the digital identity ecosystem.

Few examples of interfaces on the Playground:

IN Groupe (Wallet Issuers - SD-JWT)

This Relying Party simulator is developed and designed to validate the interactions between relying parties and EUDI wallet implementations on the SD-JWT data format.

Idakto (Wallet Issuers - mDoc)

This Relying Party simulator is developed and designed to validate the interactions between relying parties and EUDI wallet implementations on the mDoc data format.

Idakto (Relying Party - mDoc)

This demonstration application is used to test the implementation of the 2 protocols needed to create a wallet, the openID for Verifiable Credential Issuance (VCI) and the openID for Verifiable Presentation (VP) on the mDoc data format.

Valera (Relying Party - SD-JWT)

This demonstration application is used to test the implementation of the 2 protocols needed to create a wallet, the openID for Verifiable Credential Issuance (VCI) and the openID for Verifiable Presentation (VP) on the SD-JWT data format.

Frequently asked questions

You can find all the available interfaces on the "Interfaces available" page on this website. Please note that the number of available interfaces is intended to increase over time.

In case of a technical issue, you can:

  • Create an issue on GitLab.
  • Send a message on the Potential Slack channel
  • Contact the developers listed at the bottom of each stub documentation page.
  • Or contact us through the contact form.

Yes, you can integrate your own stub into the Playground. The documentation for this process will be available soon.

To access the Playground, you must be a partner involved in the POTENTIAL project or an associated stakeholder. All resources are freely available, and accessing the Playground will grant you access to the GitLab platform. To register, please complete the following form
After submitting the form, you will receive an email with your login credentials.