Here’s an update on our current road map plan, both to let people know what’s coming up and to get feedback. ENS has always been an open source and community-driven project. We really appreciate all the help, suggestions, and contributions we get from all of you!
A big thanks for everyone’s understanding and support with our ENS registry bug fix. The whole episode produced a lot of stress for us and put us back about 4 months (!), but I’m glad it’s behind us. Now we’re looking to the future.
What we’re working on right now: The project board we use for our bi-weekly development sprints is public on Github. If you’re ever interested in what we’re actively working on, feel free to check it out.
Here’s our plan for the next few months. Some of these things are being done in parallel, but this should give you an idea of our plan roughly in the order we plan on doing it.
1) Catch up
The last few weeks we’ve spent trying to catch up on tasks that had built up while we were focused on the bug fix. This includes some new Manager features we had been working on before we dropped everything for the bug fix, some Manager UI bug fixes, as well merging some PRs that other people had submitted to us.
An example of the latter is a feature to be able to upload files/folders to IPFS and save the hash to your Content record, all from within our Manager! You can track the PR here. A lot of the work for that has been done by the folks at Temporal.Cloud, whose service the feature uses. We are getting close to finishing the details so we can merge it, so stay tuned.
2) Prep for renewals
In the next few months, .ETH names will start to actually expire and be released for the first time. We’re working on various tools to make it easier for people to track when their names expire, to bulk renew names, and to more easily track when other people’s names are expiring (so you can register them once they expire if you want to).
We’re also considering a proposal to change the way pricing works around expiring names, feedback welcome.
3) DNS namespace integration
I can’t wait for this! This has been a key part of our strategy for a long time, and I’m looking forward to us finally being able to get this done.
If you don’t know what I’m talking about, we’re integrating the DNS namespace for use on ENS. We’ve already integrated .XYZ, .LUXE, .KRED, .ART, and .CLUB, and soon we’ll be rolling out to most of the rest of the DNS namespace. What this means is you’ll be able to send DOGE to example.com using ENS, among other things.
4) Homepage revamp
We’re already working on this in parallel with our other work. If you haven’t noticed, ens.domains is out of date, or at least it is no longer giving a full picture of all the features ENS now has. So we’re going to fix that (and try to keep it up-to-date from now on).
5) Other Manager improvements
There are tons of ways to improve the Manager. Just a few examples:
- Create framework so people can translate the Manager and easily switch between languages
- Create framework so people can easily add support in the Manager for more cryptocurrency addresses (Manager currently supports 15, though ENS on the protocol level can support any)
- Ability for users to set multiple ENS records in one txn
- More web3 sign-in options, e.g WalletConnect
- Mechanism to allow for updating our pre-image so that users see fewer names as hashes in the Manager
- More data types/projects supported in our Content record
- Ability to pay in Dai and other Ethereum-based tokens (something converts the payment to ETH for the user, e.g. Uniswap)
- And more
6) Governance improvements
We’re very thankful for the service provided by the ENS keyholders (see the bottom of ens.domains for more info). We’re actively thinking about how we can improve our governance, including term lengths for keyholders, clearer expectations, et al.
We want your feedback
So what do people think? What do you think we should be prioritizing? Is there something not listed here that you see as a top priority (or just that you’d love to see)? Thanks for your support!