This isn’t something that needs to wait for an update to BNS. It’s something that can be done today with existing BNS functionality…all it needs are relatively simple developer tools and wallet support and an agreed upon standard.
I’ve put together a draft of such a standard to enable BNS names to bitcoin address mapping. It takes advantage of BNS’s compatibility with a subset of DNS zone file functionality to enable this feature without having to deploy new or updated smart contracts. The standard itself is actually name system agnostic: tools built to work with it will work not only with BNS names but also enable name-address (or account!) mappings on DNS names and other name systems such as HNS that support zone files.
I’d love your feedback…especially from wallet and application developers. Does this approach make sense? Is this useful for you? I’m happy to contribute this to any group that has formed that is looking to move BNS forward or, alternatively, resurrect the BNSWG.
Would this implementation be a new library, or a PR to an existing library like stacks.js?
Or, some other solution entirely i’m not thinking of?
This was actually brought up in a SIP call last week i think (i had been seeing the same requests in the community for a feature like this), and, like you, i see this as very possible today - but it’d be great to get ahead and standardize how it’s done.
The approaches you’re referring to seem good to me, but i’ll dig in a little deeper to see if i can find any issues with what’s being proposed. overall, it’s very similar to what i was thinking of as a potential SIP - but offloading this work to a library or something makes more sense.
Thank you for drafting and sharing this Larry! I think this is so important for BNS and Stacks. Would love to hear from others in the ecosystem. Xverse is definitely interested in implementing this standard.
Question - does this need to be a SIP or should BNS have it’s own improvement proposal process BNSIP?
Since it is applicable to more than just the BNS/bitcoin ecosystem, my first instinct would be to make a new library. Something that akes a zone file as an input, has some functions to manipulate (add/remove/update) the addresses the name points at and then outputs the zone file. Library developers could choose to integrate this functionality into their libraries if they want but wouldn’t have as long as it gives developers access to the “raw” zone file.
We need more like this! Thank you for the write-up.
For this standard to get wider adoption, I think we need to solve the uniqueness of top level domains that users and wallets need to know when they want to resolve a name. Which blockchain/resolver service should they use for friedger.btc, friedger.bitcoin, friedger.fren, friedger.eth, friedger.de, friedger.id, blog.friedger? This is probably out of scope of the standard, but it should be mentioned that a mechanism should be established. Maybe https://chainagnostic.org/ is a place for that. web3domainalliance tries to create at least no overlaps between their members (like ICANN?).
Then once, the wallet managed to find the zone file which is the correct ticker that the user wants to use and that the recipient intended to publish?
In section 3.1 “Resource Record Namespace” the definition is left out.
coin’s ticker symbol name
Which ticker should be used here? ISO proposal “XBT” or commonly used “BTC”. What happens if a project/exchange decides to change a ticker. Do all users need to change their zone files?
Some more stories about changing token tickers, e.g. at
Probably, similar results can be achieved with the use of did:web specification. The W3C (https://www.w3.org) published a recommendation in July 2022 to integrate into the DID a web reference in order to use the trust that users have in the Internet DNS, calling it did:web, to speed up DID’s adoption.
Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject. Some of this has been addressed here GitHub - paradigma-cl/dappprofile: Stacks dapp public profile
Then having trustable interactions the DID addresses can be used to transfer funds to domain names.
Thanks for sharing Larry, this is great. The Hiro Wallet will of course implement the standard.
Are wallets expected to support DNS hosted names in addition to DNS names? Is there the possibility of naming collisions between BNS & DNS names?
Is it within the remit of the spec to discuss potential scope for abuse? Is DNS spoofing a concern?
Using a single address to receive funds has privacy implications. Would it be the responsibility of wallets to educate users of this? Are there any best practices to minimise divulging financial information? Should users frequently update their listed addresses, or is this futile as all addresses have at some point been public?