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.