I’m working on Stems, an experimental server on the Bluesky social network.
Bluesky has two unique features: (1) anyone can run a server with its own features and (2) domains are used as handles. It’s great that Bluesky does not roll their own identity system and instead outsources this to DNS.
Stems takes that concept a step further by extending our server’s resolution so that ENS domains can be natively verified and used as more sovereign and secure handles. We do this within the existing Bluesky format of TXT-based verification by allowing users to set onchain TXT records following the EIP-1185 standard.
(Note: TXT is a DNS format different from ENS “Text Records”)
Hey @brxwn.eth really cool concept here… Also seeing it’s your first post to the forums, so welcome!
It may be good to present(if that’s something you want to do) the concept and demo at the ENS Ecosystem Working Group meeting. The meetings happen weekly and here is the agenda for today’s meeting.
Joining those calls would give the community a chance to see it in action and hear it explained a bit more. It’s also a great avenue to receive feedback and suggestions from the community. Hope to see you there one day!