Keynote Speaker Announcement at 2024 Oxford Blockchain Conference

**ENS DAO has approved a new Security Council** that will operate for the next two years with authority to cancel malicious proposals. **Key Details:** - Eight-member council with veto power over passed proposals before execution - Operates through a 5-of-8 multisig requiring majority agreement - Two-year term unless extended by DAO vote **How It Works:** The council can intervene after a proposal passes but before it executes, providing a safety mechanism against malicious governance attacks. [Read full details about mandate and members](https://ens.domains/blog/post/introducing-the-newest-ens-security-council)

The Ethereum Name Service has appointed eight new council members: - **Nick Johnson** (@nicksdjohnson) - **Hudson Jameson** (@hudsonjameson) - **Pablo Sabbatella** (@PabloSabbatella) - **Colton Liberacki** (@Coltron_eth) - **Kevin Gaspar** (@ValidatorETH) - **Alex Van de Sande** (@avsa) - **Griff Green** (@griffgreen) - **Alex Netto** (@alextnetto) The announcement marks a governance expansion for ENS, the blockchain-based naming system that maps human-readable names to Ethereum addresses and other identifiers.

**The Reverse Record Issue #7** explores fundamental aspects of ENS naming systems. **Key Topics:** - Why humans instinctively name everything and how this applies to blockchain identities - The evolution of ENS names from simple identifiers to complex identity systems - Technical deep-dive into the Universal Resolver and its behind-the-scenes operations **Also Included:** - Latest developer updates from the ENS ecosystem - Community highlights and integrations - Technical improvements and tooling updates The newsletter continues its tradition of making technical ENS concepts accessible while providing valuable updates for developers and users alike.

**ENS is upgrading its resolver system with ENSv2** The Ethereum Name Service is introducing a Universal Resolver - a single smart contract that can resolve names across multiple environments: - ENSv1 names - ENSv2 names - Layer 2 networks - Offchain names via CCIP-Read **What developers need to know:** Applications using ENS should update their libraries to ensure compatibility with the new Universal Resolver. The system uses CCIP-Read protocol to fetch data from L2s and offchain sources. This consolidation simplifies the resolution process by eliminating the need for separate resolvers for different name types and networks. Developers can find implementation details in the [ENSv2 readiness documentation](https://docs.ens.domains/web/ensv2-readiness/). **Action required:** Review your ENS integration and update libraries to support cross-chain resolution.

ENS has introduced `registerAgentIdentity()`, a new function that provides AI agents with on-chain identity infrastructure. When called, agents receive: - A human-readable ENS subname - An on-chain passport - Cryptographic proof linking the agent to its owner This builds on ENS's evolving role beyond simple name resolution. The system now supports: - **Arbitrary records** that carry an agent's full trust stack - **Identity scoring** (none, registered, discoverable, verified, full) - **Programmable resolvers** that execute logic like token swaps or privacy routing ENS serves as the accountability layer, transforming raw cryptographic keys into verifiable, human-readable identities. One ENS name can hold everything: identity, discoverability, code integrity, and capabilities. The infrastructure makes agents resolvable and accountable while maintaining the flexibility to chain complex actions through custom resolver logic.