Gasless Offchain for DNS and ENS via TheOffchainResolver

🧑‍💻 ENS Development
18

TOR deployed to Mainnet at 0x84c5AdB77dd9f362A1a3480009992d8d47325dc3

I changed raffy.eth resolver to the new TOR and then set the fallback to the old PRv2, restoring all my on-chain records. My name is currently hybrid: both my "name" and "description" records are off-chain (see screenshot + code below.)

I set text("ccip.context) to "0x2Fc3Fd8444211091De2DF9052741f80e4d78eeee https://raffy.xyz/tog/raffy/e1" which corresponds to my server’s signing key (eeee), my server (raffy.xyz), the router handling my requests (raffy), and a key for the mainnet v1 deployment (e1).

I created mirror.raffy.eth as a real subdomain and also gave it the TOR resolver. On the TOR, I called toggleOnchain() and I changed the fallback to the namehash of nick.eth.

I launched a TOG and created a custom router for my name using a new schema which is like a mix of JSON-notation for records and router-notation for ENSIP-10 handlers.

Code

image
image891×368 18.1 KB

  • I’m also serving some routers I’ve previous shown wiki and eth.cb.raffy.eth.
  • A static route at moo.raffy.eth
  • And an inline handler at chonk.raffy.eth (which is internally mirroring chonk239.nft-owner.eth and then replacing the avatar since it used an avatar string)

I also created few new demos and updated some others: