Publish TEE-attested data to EAS

Configure what to read from any EVM chain. An OutLayer worker fetches it inside an Intel TDX enclave through an independent-RPC quorum, signs it with a key that never leaves the enclave, and writes an attestation to the Ethereum Attestation Service. Every result is publicly verifiable — on the chain's EAS explorer and against the worker's attestation at workers.outlayer.ai.

1 Network

2 What to attest

Comma-separated Solidity types and names — the standard EAS schema format. Supported types: uint*, address, bool, bytes32, bytes, string. Each field needs one data source below, in the same order.

3 Data sources

Every source is read from several independent RPCs pinned to the same block; if they disagree, the job refuses rather than attest a number one node could have fabricated. A source can target a different chain than the attestation — that is how one attestation compares value locked on one chain against supply minted on another.

4 Attester key

Secrets live on app.outlayer.ai, which holds the wallet and the enclave's public key: the value is encrypted in your browser and stored on-chain by your wallet. The link pre-fills the project, profile and secret name — check the dashboard's network switch (top bar) matches the run, the values match the table below, and sign with your wallet: whoever stores the secret owns it. The project must already exist on-chain, otherwise the transaction reverts with Project '…' does not exist. A private key must never travel in a URL.

5 How to run it

This is the network the job runs on, and it is independent of the chain you attest to — a worker on NEAR mainnet can perfectly well write an attestation to Base Sepolia. Payment keys and secrets belong to one network, so they must match the choice here.

With a payment key the run goes over the HTTPS API — no wallet, no on-chain transaction to start it. Leave it empty to get the on-chain request_execution call to send from your own wallet or CLI instead. The key is used only by this page in your browser to sign the request; it is never stored or sent anywhere else.

Result

Run something above and the evidence, calldata and explorer links land here.

Job JSON



  

Same thing from a terminal