View Envoy Labs projects on GitHub envoylabs/blog
Now that we’re on mainnet, it’s time to define a rough roadmap for what’s to come.
We’re about to release some minor fixes, that allow for experimental things like messaging via message memos (caveat: we have no idea if this will scale).
Regardless, we have a rough idea that the roadmap will be (in order):
† with the critical difference from elsehow’s blog post being that nobody other than the current owner of a name can burn, transfer or send a name - there is no central authority, and at present that also includes the base token. They can point it at things without transferring ownership, if they want to maintain control over a base token, or sub path.
Obviously all of this is subject to change, but that’s where we are right now.
As always, you can get in touch via the #name-service
channel on the Juno Discord, or tweet us @decentralizedns.
We’ve said before that this was very much a side project, and we’re blown away and a little humbled by the response it’s gotten.
We had originally a quite different roadmap in mind, as we assumed we would have a very small initial user base - but it’s bigger than expected, and you’ve told us that Keplr is the priority - so we’ve switched things around, as the list above shows.
All that remains to be said is thanks to everybody that’s checked it out and thinks it’s cool. It’s very early days for projects like this in the Cosmos, and hopefully it will develop into something really cool, with your support!