Thanks Matt! I've read BIP along with comments in github issue. You're very concise about HTTP drawbacks in there - a, b, c. , you don't have to expand on that a lot in DNS-focused spec obviously.. I just recall from my working experience dns is typically far away from what application has to deal with and would like to have dependency on To make changes. I need to go to another team in the company, engage external service provider if it's smb - this is a friction I was talking about. To top this with all the memes that often go around tech industry- "it's always DNS to blame"

I wonder if bitcoin payment scenario is close to OpenID, e.g. how keys are distributed for instance here https://accounts.google.com/.well-known/openid-configuration and what this protocol does in terms of authentication, signing access tokens, etc There are many software libraries for interoperability. it's still plagued by token theft, but smart guys in IETF and OASIS couldn't come with anything better over the years.

I am sure there are benefits to DNS, wildcard sounds easy !