The underlying system of protocol relies on Attestations. which are stored on the Attestation Registry. When recording any achievement to protocol you make an attestation on smart contract level. This attestation includes a claim and a proof. The Attestation Registry follows the architecture based on Sismo.io protocol.
Attestation consists of three things particularly:
A claim can be thought as something like
“I have contributed to EIP repository and I request to have attestation stored for this wallet address.”
A proof is the evidence with the data showing that this action is true. It can be based on off-chain records using for example an off-chain oracle based on GitHub API to verify contribution. Proof can also be a reference to an on-chain credential for example an NFT earned after completing a Solidity tutorial.
Person who creates an attestation requests to store the attestation value under their wallet address to the specific section in the Registry.
All successful attestations are stored on the Attestation Registry which is a special storage inside protocol’s contracts. Identity, Skills and all other credentials are stored there.
You can read more about the Registry here.
Attesters are functions that handle, verify and store attestations. Only authorised Attesters can store attestations to protocol’s registry. This means that each new credential type that is to be added to protocol has to be authorised first. Authorisation happens by community choosing if the new attester is to be allowed to have editing access to a specific part of the registry.
You can read more about Attesters here.
If the form doesn’t load, please continue here.
Table of Contents