Skip to main content

Proof Template Page

The Proof is the answer SSI of the owner to a proof request, if credentials are digital representation of an ID, a proof is the certification that the OPERATOR has the right credentials needed for the proof request.
Holder of credentials can generate verifiable representations (informally named Proof) once a verifier creates a Proof request.
Proof requests can be composed by 2 different attributes:

  1. Restricted
  2. Self-attested

Restricted attibutes are taken from schemes or credentials connected to the organization. Restricted attributes can be REVEALED or UNREVEALED.

  • Revealed attributes will notify the USER that the proof will request and check that field, meaning that the USER will send to the Verifier the knowledge of that credential.

  • Unrevealed, also known as zero-knowledge, won’t show up during the process of proof for the USER and the Verifier will only know the result he need, like:

"Does the USER have a college degree?" the verify will get a "yes/no" answer.

Self-attested attributes are not conntected to schemas or credentials, this type of attributes are a certification that the USER vouch for, without the need for a specific credential. Self-attested can have different type and the could be mandatory or not.

If a self-attested attribute is mandatory, the USER is forced to fill the field in the proof request.
If a self-attested attribute is not mandatory, it won’t be necessary fill this field during the proof request.

Back to top