Technical Glossary
This technical glossary is aimed to provide a broad overview of Sismo Attesters and Attestations.
For a more concrete view of Sismo protocol, head to the examples section which goes over both simple and advanced use cases in more detail.
Term | Description |
---|---|
Account | An account is a pair of an account identifier (e.g an Ethereum address, github username or twitter username) and a particular value (e.g number of votes submitted to the ENS DAO or number of twitter followers). |
Group of Accounts | A group bundles accounts that share reputation or historical characteristics. The group can either exist on-chain (e.g current owners of an ERC20 token) or off-chain (e.g ENS DAO Voters, generated off-chain on June 10th, 2022).
Group examples:
|
User Claim | A user claim targets a specific group. It consists of:
|
Term | Description |
---|---|
Available Groups (Attester Data) | A group is said to be available for an attester when the attester has access to on-chain data in the specific format that it requires. This enables the attester to validate user claims.
Most attesters require a third party to post on-chain data (e.g merkle roots), though some just read from the EVM directly. Each available group in the context of an attester has a group identifier. |
Standard User Request (Attester Input) | A user request targets a specific attester and specific groups of that attester. It has two components:
|
Proof (Attester Input) | Arbitrary data required by the attester to validate the request "Here is proof for my claims and proof that I own the destination" |
Attester: verifyRequest (Attester internal function) | Each attester has its own way to verify user requests.
|
Attester: buildAttestations (Attester internal function) | Once an attester has verified a user's request, it constructs one or multiple attestations. Each attester has its own logic to construct attestations from verified user requests.
Example: Alice claims to be part of the 'ENS DAO Voters' group with 5 votes, and wants the attestation on 0x2.
|
Attestation Recording (Attester Output) | All generated attestations are stored in the Attestations Registry, a contract that keeps all user attestations in collections. |
Term | Description |
---|---|
Attestation | An attestation is a certificate that proves a fact. Attestations are bundled in collections. An attestation consists of:
|
Attestations Collection | The Attestations Registry is divided into attestation collections. A collection bundles owners that share some historical or reputation characteristics. |
Authorized Issuers | Multiple types of issuers can be authorized to write in the attestation registry (attesters, bridges, front contracts etc..). Issuers must be authorized/unauthorized by Sismo's governance. |
Term | Description |
---|---|
Badge | A badge is a Token representation of an attestation. It is a stateless ERC1155 contract that reads balances from the attestation value
|
Last modified 3mo ago