Page tree
Skip to end of metadata
Go to start of metadata



FAQ

Find a repository of our most frequentely asked questions

General

As we build the European regulatory framework, in the transition from paper to digital, a key question arises: how to share official documents, called ‘evidences’ or ‘credentials’ in a way that can be trusted?

Blockchain changes the traditional pattern of data sharing due to its distributed nature, as opposed to a centralised information exchange protocol. Blockchain can act as a point of truth that supports the verification of the entities involved in the transaction and the authenticity of information without requiring real-time access to the source of the information.

EBSI's objective is leveraging on blockchain to accelerate the creation of cross-border services for public administrations and their ecosystems to verify information and to make services more trustworthy.

The European Blockchain Partnership (EBP) was created in April 2018 by a Joint Declaration and includes all EU Member States and members of the European Economic Area (Norway and Liechtenstein). The signatories of this Joint Declaration commit to working together towards realising the potential of blockchain-based services for the benefit of citizens, society and the economy. As part of this commitment, the Partnership is building the European Blockchain Services Infrastructure (EBSI), which will deliver EU-wide cross-border public services using blockchain technology.

The European Blockchain Services Infrastructure (EBSI) is a network of distributed blockchain nodes across Europe. It is the first EU-wide blockchain infrastructure, driven by the public sector, in full respect of European values and regulations.

The EBSI nodes composing the network support multiple protocols (pluggable protocols) and a full set of APIs. The main protocols supported at the moment are Hyperledger Besu (with IBFT 2.0 consensus) and Fabric. See EBSI’s architecture in more details.

Decentralised identifiers (DIDs) are a new type of identifier that enable verifiable, decentralised digital identity. A DID refers to any subject (e.g., a person, organisation, thing, data model, abstract entity, etc.) as determined by the controller of the DID. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralised registries, identity providers, and certificate authorities.

Verifiable credentials (VCs) are an open standard for digital credentials. They can represent information found in physical credentials, such as a passport or license, as well as new things that have no physical equivalent, such as ownership of a bank account. They have numerous advantages over physical credentials, most notably that they are digitally signed, which makes them tamper-resistant and instantaneously verifiable.

EBSI is currently restricted to public administration and EBP-endorsed partners. You can contact your national EBP representative for more information on how to get involved in your national initiatives (if applicable).

The EBSI team does not engage directly with private companies, however, you are welcome to contact your national EBP representative on opportunities with EBSI.

The EC and EBP do not engage in promotional activities with private companies.

Our existing communities are currently restricted service providers working for the EBP member countries.

You can follow us on our social media channels or subscribe to our recurring newsflash!

  1. Twitter
  2. Facebook
  3. LinkedIn
  4. YouTube
  5. EBSI Newsflash

Our specifications are available in the documentation section. The specifications are constantly evolving and the documentation will continuously be updated.

Early Adopters programme / Piloting

The Early Adopters programme is currently restricted to public administrations and EBP-endorsed partners. You can contact your national EBP representative for more information on how to get involved in your national initiatives (if applicable).

The Early Adopters programme is currently closed, registrations are foreseen to reopen soon. You can already subscribe to our waiting list here and be informed once the programme is accepting new applications.

In order to join the programme, your project must be endorsed by your national EBP representative. Some of the factors taken into consideration in your application is the maturity of your project, its cross-border aspect, whether or not it is ready to be implemented on EBSI.

Wallet conformance testing

We have documented all the testing and flows (hyperlink to page WCT on new EBSI website), which need to be implemented by your wallet. Once you have completed the test scenarios successfully - please create a ticket in the service desk and our support team will run some verification steps to confirm the testing is correct.

Once you have passed the Wallet Conformance Testing, you will be informed of the result by our Support Office. An electronically signed conformance report will be supplied to you and conformant solutions will be displayed on the EBSI website.

Node

EBSI nodes are being operated by the EBP members that partner with local service providers. In order to get involved, please contact your EBP representative.

The complete hardware and connectivity requirements for hosting a node are available in our documentation.

When you have the hardware and connectivity requirements ready at your side, please create a new node request in our service desk - our support team will then walk you through the entire Node installation/verification process.

The Support Office will verify the following before confirming the node setup is complete:

  • The minimum hardware requirements are met;
  • Connectivity to the other nodes is correct;
  • Stability of the node (uptime, memory, disk usages);
  • Connection reliability to our configuration management system.

Once your node is operational, the Support Office will give you access to our dashboard service which gives current performance and connectivity information for your node.

Releases are pushed out automatically from our side, five working days before a release the support office will send out a communication containing the changelog and timing of the release.

We have created a special page to address any concerns you may have with the Log4j Vulnerability (please note you have to be logged in via your EU login account to access this page).

Integration

The API and associated swagger specification are located here.

Along with the API, we have developed a test-scripts package which shows examples, calls and flow of how the API can be integrated into your application. You can check out an example here.

  • No labels