EAS is an infrastructure public good for making attestations onchain or offchain about anything. It's open-source, permissionless, and credibly neutral.
Attestations are digital signatures on structured data. In other words, an entity signs a piece of data using its Ethereum wallet. This can be a person, business, or smart contract. It's used to build more trust online and onchain by allowing entities and others to verify a piece of information came from a particular source.
We're on a mission to build more trust online and onchain. If we are successful together, we can decentralize more than just money and assets and realize the full potential of Ethereum-based products & experiences.
How do you decide who and what to trust? Our online and onchain worlds are filled with both genuine and deceptive information. We need a common way we can trust the authenticity of information and safety of our interactions. Anytime you need to prove or verify something, attestations will play a critical role.
In the age of misinformation - verifying facts, and proving the authenticity and trustworthiness of information become critical. In our offline worlds, people attest to things all the time. A notary attests that you signed a document, a doctor attests to your health, a university attests to your diploma, you attest to the post and likes you make on social media, a bank attests you're qualified for a loan, and even your friends attest that they like you or that they trust you. The interactions are endless. However there is no universal and standard way for making attestations online or onchain. It's been highly fragmented.
A public infrastructure for making attestations about anything. At its core, EAS revolves around two primary contracts: registering a schema and making attestations.
Attestations are the building blocks of building trust online. Think of an attestation as a digital stamp of approval on a piece of data. It's a way for one entity to say, "I vouch for this information." and gives others the optionality to rely on that information.
But for this system to work seamlessly, we need a standardized way to structure this data. This is where schemas come into play. Think of a schema as a blueprint or template. It defines the structure and format of the data you want to attest to. For example if you want to attest to someone you trust, all you'd need is a true false field for "isTrusted". Or if you wanted to a vote, you might have a "eventName" and a "location" and "startTime" and "endTime". It's the builder's choice to determine the right schema for their particular use case.
Supported by community grants & contributions
Want to grow through just grant funding
Global