📄️ Create a Schema
A schema defines the data structure for an attestation within the Ethereum Attestation Service (EAS). Schemas are customizable and can be created for any purpose, allowing users to leverage preexisting schemas or create new ones tailored to their specific needs.
📄️ Make an Attestation
Depending on your needs and technical expertise, there are several ways to make attestations with EAS.
📄️ Fetching Data with EAS
EAS provides multiple methods to fetch attestation and schema data. Depending on your use case and technical proficiency, you can choose the method that best suits your needs.
📄️ Referenced Attestations
refUID is one of the most powerful features of an EAS attestation that unlocks its composability by allowing one attestation to reference another.
📄️ Revoking Attestations
Attestations on EAS can be revoked when they are no longer valid or accurate. This can be done both on-chain and off-chain. Revoking an attestation will mark it as invalid. This can be useful in situations where an attestation was made in error, or if the data it represents has changed or become outdated.
📄️ Delegated Attestations
Delegated Attestations enable an entity to sign an attestation while allowing another entity to cover the transaction
📄️ Storing Offchain Attestations
When making an offchain attestation, you have the choice to decide where that data is stored. EAS does not presuppose where that data should live or how it should be used. Thus, by default, all offchain attestations are made private. The EASSCAN server doesn't even know that it exists.
📄️ Timestamping Attestations
Add a verifiable timestamp to your off-chain attestations using the EAS SDK or Easscan UI.
📄️ Using Resolver Contracts
A Resolver Contract acts as a hook for a Schema, ensuring that attestations conform to specific rules or any smart contract logic before they can be completed. This feature allows you to introduce additional smart contract functionality to your schema, such as an allowlist of users that can create attestations or minting NFTs when specific conditions are met.
📄️ Making Gas Efficient Schemas
In this tutorial, we'll explore how to create gas-efficient schemas using Ethereum ABI types. We'll dive into the various Ethereum ABI types, their estimated sizes in bytes, and their associated gas costs. Plus, we'll provide guidance on when to use specific types for different use cases, complete with examples.
📄️ Private Data Attestations
Discover the power of "Private Data Attestations" using Merkle Trees. This is a developer guide for the implementation of private data attestations using Merkle Trees.
📄️ Storing on Ceramic
In our On-Chain vs Off-Chain section we discussed how off-chain attestations can be integrated with other decentralized networks to make it easier for developers to access and query attestations relevant to their communities. When querying attestations at scale, some of these storage options enable faster and more efficient processing, offering a suitable choice for projects that require high throughput.
📄️ Naming Your Schema
As a creator of a schema, you can "Name a Schema". Here's a quick tutorial in how you do just that.
📄️ Schema Descriptions
The clarity and understanding of schemas play a pivotal role. A schema description not only provides context but also ensures that the data being attested to is understood universally. This document will guide you through the importance of schema descriptions, the design choices made by EAS, and a step-by-step tutorial on how to attest to your schema description.
📄️ Schema Context
Contextprovides meaning and clarity, ensuring that data is understood and utilized correctly. With the introduction of "Schema Context" in the Attestation Ecosystem, you can now set a predefined context to your schema, ensuring that it aligns with universal standards and is easily interpretable by various systems and platforms.