If you're building a naming service, don't do this.

Built @basename, @orangedao, prev @shapeshift, IBM, Rhino Security

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

@base builder #001; onchain cities w/ OAK & city3

gm guys,

Thank you for your feedback and suggestions. We appreciate your input. We understand that there is a desire for shorter names and even the inclusion of emojis in the naming service. We are actively working on proposals to address these requests.

In order to facilitate community involvement and decision-making, we will be sharing the proposals on https://snapshot.org/#/basenamedao.eth. This will allow users to review and vote on the proposed changes. We believe that community input is crucial in shaping the direction of the Base Name Service.

We are committed to making improvements based on user feedback, and we will carefully consider all suggestions. Thank you again for your feedback and support.

Hey 👋 are there any docs detailing how forward and reverse resolution works for .base names? We'd like to integrate BNS into everyname.xyz

editor https://lowercase.cards/ prev: everyname (acq. Q4 '23)

Gm @vinayvasanji.eth,

While we don't have specific documentation on forward and reverse resolution for .base names, we do have API documentation available for looking up .base names and addresses.