|
1 |
| -# Attestation |
2 |
| - |
3 |
| -An attestation is a cryptographically attested message, by an attestor stating someone have something. |
4 |
| - |
5 |
| -It's a few lines long and often is delivered through a [MagicLink](MagicLink.md). |
6 |
| - |
7 |
| -Note that an attestation is produced by a trusted attestor. It is not a trustless technology. See [Attestation vs Proof](../faq/attestation_vs_authorisation_vs_proof.md). |
8 |
| - |
9 |
| -There are two types of attestations: token issued as attestations (token attestation for short), and identifier attestations. |
10 |
| - |
11 |
| -## Token Attestation |
12 |
| - |
13 |
| -Token attestations are tokens issued by sending the recipient an attestation. The recipient, by using the attestation, is able to interact with smart contracts as if he has a token in a token contract. |
14 |
| - |
15 |
| -An example of such token is the DevCon 2022 ticket. |
16 |
| - |
17 |
| -The advantage over minting tokens in a smart contract: a token is never minted, and can be used as if it is minted. However, it is not transferable in that form, instead, when transferring, a token contract has to burn the attestation and allocate it to the new recipient, and the new recipient will hold the token as a normal smart contract token (not attestation token). |
18 |
| - |
19 |
| -Tokens that can be issued as attestation are non-fungible. |
20 |
| - |
21 |
| -## Identifier Attestation |
22 |
| - |
23 |
| -Identifier attestations are issued by attestors who verifies an Ethereum key holder also owns an identifier. A typical identifier is a web2 identifier such as |
24 |
| - |
25 |
| -- Email address |
26 |
| -- Twitter handle |
27 |
| -- Facebook ID |
28 |
| -- Github handle |
29 |
| - |
30 |
| -Use-cases of Identifier Attestations are: |
31 |
| - |
32 |
| -- To be used as a dependency for other tokens. For example, when DevCon 2022 ticket is issued, they are issued on user's identifier (email address). To use the DevCon ticket, a user has to acquire an email address attestation. |
33 |
| -- To be used to attest a transaction as from an identified user. For example, in AutographNFT, a person who add an autograph on an NFT must provide a twitter ID attestation, therefore attesting the autograph is from the owner of that ID. |
34 |
| - |
35 |
| -More use-cases can be found in [Attestation Usecases](../usecase/Attestation.md) |
36 |
| - |
| 1 | +# Attestation Appliations |
| 2 | + |
| 3 | +An attestation is a cryptographic message or proof that asserts certain facts about a specific object. |
| 4 | + |
| 5 | +While traditionally produced by a trusted attestor and often signed, some attestations may use zero-knowledge proofs to establish trust without revealing specific details. |
| 6 | + |
| 7 | +When it is presented to the user, it is encoded in a [Magic Link](MagicLink.md). |
| 8 | + |
| 9 | +In TokenScript, various types of attestations exist, and the list is expandable. These attestations are not inherently trustless; they usually come from a trusted source or mechanism. See [Attestation vs Proof](../faq/attestation_vs_authorisation_vs_proof.md). It has many [Applications](AttestationApplications.md) |
| 10 | + |
| 11 | +## Attribute Attestation |
| 12 | + |
| 13 | +This type of attestation asserts specific attributes about a token. For instance, an airline might issue an attribute attestation to update the arrival time for all passengers on a delayed flight. Smart Tokens representing airline tickets for that flight can then use this attestation when interacting with other systems or smart contracts. |
| 14 | + |
| 15 | +## Authorisation Attestation |
| 16 | + |
| 17 | +Authorization attestations are similar to attribute attestations but are designed to grant permissions or access rights. These attestations often come with time limits, intended recipients, and anti-replay attack mechanisms. For example, in the event of a flight delay, an airline could issue an authorization attestation allowing affected passengers to access the lounge. |
| 18 | + |
| 19 | +## Attestation Token |
| 20 | + |
| 21 | +An Attestation Token is a specific type of attestation that attests to a user's ownership of a token. Token issuers typically issue these attestations to users identified by their public keys or Ethereum addresses. These attestations enable users to interact with smart contracts as if they possess tokens in a token contract, allowing for off-chain token issuance. |
| 22 | + |
| 23 | +## Identifier Attestation |
| 24 | + |
| 25 | +Identifier attestations are issued by trusted attestors who verify that an Ethereum key holder also owns a specific web2 identifier, such as an email address or Twitter handle. These attestations can serve as dependencies for other tokens or to authenticate transactions from identified users. For example, when DevCon 2022 ticket is issued, they are issued on user's identifier (email address). To use the DevCon ticket, a user has to acquire an email identifier attestation. |
| 26 | + |
0 commit comments