Twitxy Saved

EAS (Ethereum Attestation Service)

Verified account This account is verified. Learn more

@eas_eth

// open standard for attested data
// 9m+ attestations made by 450k+ attesters.
the world computer attest.org Joined July 2021
99 Following 8.3K Followers 1.4K Posts

Latest posts 5

Pinned post

EAS (Ethereum Attestation Service) Verified account @eas_eth
New agent-first CLI for EAS! 🔥

Now your agents can make and verify attested data directly from the terminal.

npm i -g easctl

github.com/ethereum-attes…
github.com GitHub - ethereum-attestation-service/easctl: Agent-first CLI for the Ethereum Attestation Service Agent-first CLI for the Ethereum Attestation Service - ethereum-attestation-service/easctl
Steve Dakh Verified account @stevedakh Mar 28
npm i -g easctl

An EAS CLI with built-in schemas, JSON output for agent toolchains, and support for 12+ chains.

AI agents are starting to operate onchain. For them to be useful, they need trust — identity, credentials, reputation, accountability.

EAS attestations are the primitive for this. Signed, structured, onchain claims that anything in the ecosystem can verify.
View quoted post on X
6 replies 2 reposts 37 likes 4.1K views View on X
EAS (Ethereum Attestation Service) Verified account @eas_eth
TEE attested data 👀
Vadim (AI, ⋈) Verified account @zacodil Aug 11
OutLayer just shipped an EAS attester that attaches the hardware proof of its own run to every attestation. Web form or console.

Ethereum Attestation Service (EAS) answers who signed a claim. This attester answers the harder question: can you trust how they got the number. Two things here get called attestation, and the difference is the point. The EAS attestation is the on-chain record of who signed. The teeAttestation field inside it is a hardware proof of how the number was produced.

That proof is an Intel-signed quote of the exact run. It seals sha256 of the input, sha256 of the output, and the hash of the WASM that executed with the repo and commit it was built from. The quote is signed by a certificate chain up to Intel's root CA, so its authenticity roots in the silicon, not in our word for it.

The signing key was generated inside the enclave and has never existed outside it. No human, no browser, no operator has ever seen it.

You build none of it. Hand it a schema and a target contract, and inside the enclave it queries several independent RPCs itself, requires them to agree before it proceeds, computes the value, signs the EAS attestation with that enclave-born key, writes it on-chain, and attaches the quote of its own run. No servers, no key management, and no operator you have to believe. The quote, not us, says what ran.

The code is open source and small enough to review in full. Audit it, or fork it for your own schema. You don't even have to trust that the code you read is the code that ran: each attestation proves which binary produced it. Code can change, but a given attestation cannot lie about what made it.

Pick a preset, fund the enclave-born key with about a dollar of gas, and click. The links below verify themselves.
View quoted post on X
5 replies 1 reposts 19 likes 1.7K views View on X
EAS (Ethereum Attestation Service) Verified account @eas_eth
These should be onchain attestations on Mainnet.

easscan.org/attestation/at…
easscan.org Attest with Schema #8 (Make a Statement) - 0xf58b...6cafe Attest with 0xf58b...6cafe on EAS - Ethereum Attestation Service.
zak Verified account @0xzak Mar 30
[X] I affirm that Ethereum is the world computer, will help assure that every transaction on Earth settles to Ethereum and will maintain an energetic focus on keeping it neutral and trustless global infrastructure, such that ETH becomes the most valuable asset in the world
View quoted post on X
3 replies 2 reposts 22 likes 946 views View on X