Update on technical development: After having many discussions with potential users from across the ecosystem, we have been working on finalizing the technical foundation for the spec.
The first iteration of the idea was a top-down approach. It used the naming and structure of a .eth domain to convey meaning. For example, a top-level manifest file could specify that delegates.root.eth would contain information on all DAO delegates.
We have since proposed a new system which is much more flexible and easier to maintain. In this version, the roles of each “node” in a tree of subnames would be explained solely using text records, and the tree structure would be ignored. This means users are free to choose a naming scheme and layout that makes the most logical sense for their use case, and whatever they choose will be compatible with our system. This provides multiple benefits over the original idea:
- Cheap to implement (only one record per subname)
- Can be added to existing registrations with no changes required
- Compatible with other systems and use cases (e.g. it doesn’t break Enscribe contract naming)
- Easy to maintain: to update one node, only a single text record needs to be changed.
- Easy for non-technical people to understand; just like adding labels to each subname.
We have published an overview of this latest thinking on our Notion page with more details. For next steps, we will be asking for feedback/review by technical members of the community. If you would like to be involved, please join our Telegram group and/or watch this space for notice of our next working session.