trou

Currently we use a proxy server (Stack Domain Resolver) behind the scence to resolve those bns websites. The routing configurations are stored in a smart contract then it can be...

We will also build the samething with owl.link but the profile page will be served directly under the bns, not like own.link. But it's just a showcase for the DeName...

This is gonna be a long-lived journey since our Stack Domain Resolver (currently a single centralized instance) can be expanded to a p2p network that powers the bns websites to...

@friedger we have done the demo, can check it out here https://drive.google.com/drive/folders/1aqeqTgsfECxYnRWW33ZyCVraYrW736_f

It seems like atlas was unmaintained a long time ago. Btw I think the routing configuration should be stored in a deployed smart contract on Stacks, so it can be...

But yeah, thanks for the suggestion. I have a plan for expanding the Resolver layer but it will make more sense if we have at least some adoption first xD....

> > It seems like atlas was unmaintained a long time ago. > > Atlas is used on a daily basis, mainly by bns contracts. https://github.com/stacks-network/atlas Seems like it was...

> I am wondering if we can add something like MX records for #729 in this design Yeah sure. The end goal for our Resolver layer would be a fully...

agree, this should be released asap

hey let's implement this