Q4 Report
Summary
In this development cycle, we’ve focused on making ENS domains more powerful and easier for everyone to use. Here’s what’s new:
As highlighted during frENSday by Jeff Lau, most ENS domains today operate through off-chain systems, showing how crucial this technology is for ENS’s success. Building on this foundation, we’re introducing new standards to make domain management more seamless and user-friendly.
First, we’ve created a simpler way for doing transactions between different chains by establishing a behavior that the contracts should implement, making it easier for dapps to integrate regardless of the use case. We named it Operation Router because it acts as an actual router, redirecting the request to the given contract or API.
Second, we’ve applied this router strategy to the ENS use case. With the standard, any dapp can support domain management by following the proposed flow, features that currently require users to access multiple dapps to manage their offchain domain. The standard adoption means that the ENS dapp would be able to manage any kind of domains with the same interface it handles Ethereum ones.
We’ve also launched ens.rent, allowing domain owners to rent out their unused domains easily and securely. This opens up new opportunities for both domain owners to earn from their domains and for others to use ENS domains temporarily without having to buy them outright.
These improvements make ENS more accessible and valuable for everyone, helping it grow from a simple naming system into a more powerful and flexible platform for the future of the internet.
Operation Router EIP Release
The Operation Router EIP represents a significant advancement in offchain data management standards. This implementation is the result of multiple iterations with the ENS community and Nick Johnson (@arachnid) aiming to improve the existing strategies for offchain transactions by transforming the traditional two-transaction flow proposed by the ERC-5559 into a streamlined view call and transaction system.
The standard centers around the getOperationHandler view function, effectively turning the any contract into a router that redirects operations to either onchain or offchain handlers. This standalone solution extends beyond ENS protocol applications, prompting its development as an EIP to serve as the foundation for the proposed ENSIP. In the ENS ecosystem, the resolver deployed to Ethereum would serve as the entrypoint for all the transactions related to offchain domains.
Wildcard Writing ENSIP Update
The Wildcard Writing ENSIP has been enhanced to leverage the Operation Router infrastructure. The latest version in the ENSIPs GitHub repository introduces optimized write operations across the ENS ecosystem.
The specification has been enhanced to support two distinct operational flows. The onchain flow facilitates direct interaction with smart contracts deployed across different layers, while the offchain flow manages database operations through a secure gateway system. This dual approach ensures efficient data management while maintaining strong security guarantees through typed signatures.
There are multiple interfaces that can be inherited by any contract creating a opt-in architecture where each domain provider is able to provide features as intended, e.g. enabling the commit/reveal strategy for registration or providing ways for domains to be transferred.
struct RegisterRequest {
bytes name;
address owner;
uint256 duration;
bytes32 secret;
address resolver;
bytes extraData;
}
interface OffchainRegister {
struct RegisterParams {
uint256 price;
bool available;
address token;
uint256 commitTime;
bytes extraData;
}
function registerParams(
bytes calldata name,
uint256 duration
)
external
view
returns (RegisterParams memory);
function register(RegisterRequest calldata request) external payable;
}
interface OffchainTransferrable {
function transferFrom(
bytes calldata name,
address owner,
address newOwner
)
external;
}
interface OffchainCommitable {
function makeCommitment(RegisterRequest calldata request)
external
pure
returns (bytes32 commitHash);
function commit(bytes32 commitment) external;
}
ENS Rent Platform Release
ens.rent introduces a comprehensive rental system supporting both wrapped (ERC1155) and unwrapped (ERC721) ENS names. Built on BaseRegistrar, NameWrapper, and ENSRegistry components, the platform features per-second pricing, customizable duration parameters, and automated custody management.
Implementation Progress
ENSjs Updates
Although the Wildcard Writing standard still under review process, the team has implemented Wildcard Writing functionality in the ENSjs fork repository, expanding the JavaScript library’s capabilities an making it easier for the community adoption. This implementation provides developers with enhanced tools for managing write operations across different layers of the ENS ecosystem, ensuring backward compatibility.
The end goal is to have the standard being handled on every call that reverts with the specified error, redirecting the request to the given source, the same way the clients do for the CCIP-Read.
Throughout the research of the ENSjs implementation, the team has found an opportunity to contribute to the library by implementing a subdomain registration functionality.
DAO Proposals
The ENS DAO proposals calldata validation implementation strengthens governance process security and reliability through comprehensive validation procedures.
Future Development
Current development priorities include:
- Operation Router protocol optimization based on Ethereum community feedback
- Provide a clear path for the domain providers to adopt the Wildcard Writing standard
- Enhanced rental platform
These developments mark significant progress in enhancing the ENS ecosystem’s capabilities and user experience.