It allows contracts to indicate their ability to digest specific call data types, like multicalls
ENSIP-22 (based on EIP-7996) defines a way for resolvers to declare and implement extra “features” via ERC-165
ENSIP-23 – Standardizes the universal resolver
The universal resolver now has a standard interface with three functions: find resolver resolve (forward resolution), and reverse (primary name resolution)
Added llm txt files as a standard format for putting data into a text file that can be used with LLMs to provide relevant context.
Add MCP server support as a public standard that anyone can use to connect to their LLM available in EFP now.
Build internal AI tools for GitHub PRs handling, MCP server for meetings that transcribes, summarizes, and creates action items, agents that review PRs on GitHub, etc.
Took over SIWE
Prevoius team abandoned the project and stopped responding to messages.
New website for SIWE has been created with a clear overview and value proposition.
SIWE uses Ethereum accounts; no additional requirements needed.
The goal is to spread the adoption of SIWE inside and outside of Web3.
6. Open Space for Additional Topics
6.1 ENScribe update
Conor discussed primary naming for smart contracts using ENS
Aiming to provide contract-specific metadata using ENS (verified source code, GitHub repos, licences, etc.)
Mental model: Smart contracts with ENS name linking to verified source code or a Dapp registry associated with smart contracts on ENS