Bridge verified data to ENS.

zkTLS (Zero-Knowledge Transport Layer Security) lets you prove that specific data was served over a TLS connection — without revealing the full response. It turns any HTTPS API into a verifiable data source.

Yes. You need an ENS name that you control (as owner or manager). Your verified credential will be stored as a text record on that name.

No. You can reduct any sensitive data from the proof (for example GitHub token). Notary cannot see the plaintext.

Currently GitHub is supported, with X and other platforms planned. The architecture is extensible to any service accessible over HTTPS.

The proof is generated using TLSNotary — a protocol that lets a Notary attest to the authenticity of data served over a TLS connection without seeing the plaintext. The Notary runs inside a Trusted Execution Environment (TEE), which means even the operator cannot read or tamper with your data. The Notary is economically incentivised to provide honest attestations, so the resulting proof is both cryptographically and economically secured.

IPFS (InterPlanetary File System) is a content-addressed storage network. Every file gets a unique hash (CID) derived from its contents — if a single byte changes, the CID changes. This makes proofs tamper-proof by design: the CID in your ENS record will only ever resolve to the exact proof that was originally uploaded.

ENS (Ethereum Name Service) provides human-readable names backed by Ethereum. By writing the proof's IPFS URI into an ENS text record, your credential becomes publicly discoverable, tied to your onchain identity, and verifiable by anyone — no proprietary API or centralised database required.

You need to pay USDC or other tokens for the verification fee to the Notary (to cover TEE infrastructure costs). There are also gas fees to set a text record on your ENS name.

Each verification costs just 0.10 USDC — paying this on-chain would cost more in gas than the fee itself. Yellow Network uses state channels (powered by the Nitro protocol) to enable instant, gasless micropayments. You deposit once into a state channel and then pay for verifications with a single wallet signature — no MetaMask popups, no block confirmations, no approve-then-transfer flow.