Skip to main content

Quick Start Demo

This tutorial is a quick demonstration of some of Polygon ID's main functionalities. To illustrate how Polygon ID works, we will walk you through some of its products and tools by following along a simple POAP use case. POAP stands for Proof of Attendance Protocol, which is used to prove that someone has taken part in a given event.

This guide will briefly touch on the 3 roles of the Triangle of Trust, namely the Identity Holder, the Issuer and the Verifier. For that, we will take the case of an individual who needs to prove that they were able to participate in a particular event.

These are the steps we will cover in this article:

  1. Set up a Polygon ID wallet
  2. Issue a new credential to attest to the ID Holder's attendance to the event
  3. Fetch the newly created credential
  4. Verify the credential validity

Set up a Polygon ID wallet​

As an Identity Holder, the individual who wants to have a credential to prove his age, for example, will need an application that can hold their credentials. In our case, we will be using the Polygon ID Wallet.

note

You can also use any Polygon ID compatible wallet. Please, check our Ecosystem page for other options.

To get started with the Polygon ID Wallet, download the Polygon ID Wallet App and create an Identity:

note

Polygon ID wallet is an implementation of the Wallet SDK, as a way of showcasing its possibilities. Head to the Polygon ID SDK documentation to know more about how it works.

The process from downloading to creating an identity on the Polygon ID Wallet is just as it is shown below. You need to download the app, create a wallet, set up a PIN number and the wallet is ready to be used.

caution

This demo is using Polygon Amoy testnet. Go to the gear icon at the top right and ensure "Polygon Amoy network" is selected instead of "Polygon Main network".

Issue a new credential to attest to the ID Holder's event attendance​

A trusted entity, for instance, a private institution will now play the role of an issuer. It will be responsible for creating the credential and sending it to the ID Holder.

We are using the Issuer Node UI testing environment to manage credentials. This is the place where the trusted entity can create credentials, manage schemas and generate connections.

However, if you are using a new credential type, you actually need to create a schema for that credential, which basically is the set of JSON files that gather all the attributes of that specific credential.

To facilitate this issuance process, we have already created the credential schema whose URLs are the following:

  • JSON schema URL ipfs://QmTSwnuCB9grYMB2z5EKXDagfChurK5MiMCS6efrRbsyVX
  • JSON-LD Context ipfs://QmdH1Vu79p2NcZLFbHxzJnLuUHJiMZnBeT7SNpLaqK7k9X
note

To learn how to set up your own issuer environment by deploying an issuer node, visit the Issuer section in the documentation.

info

The schema used in this demo was built using the Polygon ID Schema Builder and is available on the Polygon ID Schema Explorer. Learn more about creating new schemas on the Schema Builder UI guide.

Issue the credential​

With the new schema in hand, the issuer should now be able to generate a credential.

  1. First, go to the the Issuer Node UI testing environment.

    danger

    This Issuer Node is publicly available and used only for testing purposes. Do not use personal or sensitive data. All data is deleted every 48 hours.

  2. Now you need to import the schema. Click on Import Schema and paste our previously generated schema IPFS address ipfs://QmTSwnuCB9grYMB2z5EKXDagfChurK5MiMCS6efrRbsyVX:

    You may preview the schema and then Import it.

  3. You can go ahead and click on Issue Credential in the top righ-hand corner. Choose Credential Link on the next page and your schema on the dropdown menu ("POAP01", in our case). For this credential, we are providing a proof of attendance to an event in Paris:

  1. After you click on Create Credential Link, you can also click on View Link on the next screen to check the generated QR code.

Fetch the newly created credential​

Now we are back to the ID Holder role. They will use their mobile application to authenticate themselves by scanning the QR code generated by the issuer in the last step.

Connect to the issuer:

This will instantly trigger a notification on the mobile which will look like this:

Accept the credential:

The ID Holder successfully retrieved the credential and it is visible on the app:

Verify the ID holder credential​

Here comes the third role in this tutorial: the verifier. This could be represented by an organization that needs to check the accuracy of someone's credentials. In our use case, this organization wants to verify whether the ID holder actually attended our made-up Paris event.

Here are the steps to verify the credential:

  1. Visit the Query builder website. The Query Builder is an awesome tool designed to simplify the creation of verification queries.
  1. You now need to define the query. You will again make use of the JSON-LD URL which we have also provided: ipfs://QmdH1Vu79p2NcZLFbHxzJnLuUHJiMZnBeT7SNpLaqK7k9X. Here is how the query should look like:
  1. Click Create Query. Now select the Network as Polygon Amoy (testnet)
  1. After clicking on Test query, you should scan the resulting QR code and follow the instructions on the mobile app.
  1. Click on Approve. After which, the process of generating the proof starts:
  1. And finally, the proof is generated. The verifier will check the revocation status and some additional information. The proof is then sent and validated by the verifier. You will receive the following response on the Query builder website:
info

This was a quick demonstration of Polygon ID's basic functionalities. However, Polygon ID is far more complex than this. It offers a range of SSI-focused tools that allow for decentralized identity and verifiable credentials management.