Web2ENS

Anyone can set github: vitalik in an ENS record. But today, there’s no way to prove it’s real.

Web2ENS fixes that.

It uses zkTLS (vlayer + TLSNotary) to generate a cryptographic proof that a real web server returned your identity data over HTTPS. The proof is stored on IPFS (tamper-proof by design) and linked to your ENS name as a verifiable text record.

This unlocks new use cases for DAOs and ENS-based communication:

• Sybil-resistant DAO membership and voting
• Verified contributor reputation (GitHub, socials, more)
• Gated airdrops and community access
• Onchain directories of trusted agents, builders and operators

Your ENS name becomes more than a username. It becomes an identity layer backed by cryptographic receipts.

• ENS, the proof's IPFS URI is written as a text record on your ENS name, making the credential publicly discoverable and tied to your on-chain identity.

• Yellow Network handles payment for the verification service via state channels (Nitro protocol), so users can pay the notary infrastructure costs in USDC.

• vlayer, generates the web proof (zkTLS/TLSNotary). A notary running in a TEE attests that specific data came from an HTTPS server without seeing the plaintext. This is the core trust primitive.

• IPFS stores the proof. Content-addressing means the CID changes if a single byte is altered, making proofs tamper-proof without any database.