The usage of ENS records seems to have plateaued despite their enormous potential to provide a decentralised web3 identity and dwebsites. This is a consequence of very high gas costs associated with adding and updating ENS records on the blockchain. Currently, it costs more gas to set a text record than an entire year's registration for a 5-character ENS name. While IPNS has reduced the gas costs associated with updating Contenthash, other records appear to either be unset or rarely updated once set.

CCIP2.ETH Off-chain ENS Records Manager is designed by NameSys.eth to solve the big $GAS problem by storing the ENS records off-chain on IPFS/IPLD and linking them with user's on-chain IPNS Contenthash. Records stored under IPNS are then resolved by ENSIP-10 CCIP-Read implementation of CCIP2.eth Resolver Contract. Users only have to pay gas fees for initial Resolver and IPNS Contenthash setup.

CCIP2.ETH uses randomised list of public IPFS gateways so it doesn't require any centralised web2 gateways to resolve ENS records, and the users are fully in control of their deterministic IPNS keys and data storage. CCIP2.ETH enables fully dynamic record updates as often as possible at zero cost, and only limited by how fast we can pin and propagate IPNS records globally. Users can sign their ENS records to be verified each time before resolving and resolution will revert if ownership of ENS domain changed recently or in scenarios when public IPFS gateways are under attack.

IPNS private key is deterministically generated on client-side and doesn't require to be shared with any third-party IPNS service provider. This is made possible by our NIP-111-like deterministic key generation from wallet signatures. CCIP2.ETH also supports use of ENS as Bitcoin lightning address and Nostr (NIP-05) social profile.

We believe CCIP2.ETH will completely change how ENS records are updated and consumed in future without any centralised service providers.

Source codes and Docs: https://github.com/namesys-eth