3 ms·
Your argument _almost_ sounded cohesive, and I'm a proponent of crypto. Handshake has an improvement proposal called HIP-0002[1] that utilizes the .well-known
by NetOpWibby 3y ago
Your argument _almost_ sounded cohesive, and I'm a proponent of crypto.
Handshake has an improvement proposal called HIP-0002[1] that utilizes the .well-known directory on your domain's server to enable direct payments. You payment address looks like this: https://<domain>/.well-known/wallets/SYMBOL https://<domain>/.well-known/wallets/SYMBOL.
You could even utilize IBAN to send to fiat like so: https://example/.well-known/wallets/USD https://example/.well-known/wallets/USD.
Of course, you'd need do a bit of legwork to implement non-crypto support.
[1]: https://github.com/handshake-org/HIPs/blob/master/HIP-0002.md https://github.com/handshake-org/HIPs/blob/master/HIP-0002.m...
- Sargos 3y agoThe Ethereum Name Service (ENS) provides this functionality in a standard protocol. You can associate Microsoft.com with an ETH, BTC, SOL, etc address. GoDaddy yesterday actually integrated this in a no-gas free manner [https://aboutus.godaddy.net/newsroom/company-news/news-details/2024/GoDaddy-and-Ethereum-Name-Service-Bridge-the-Gap-Between-Domain-Names-and-Crypto-Wallets/default.aspx https://aboutus.godaddy.net/newsroom/company-news/news-detai...]. Other DNS providers will likely follow suite over the next few years. Bonus, most web3 tooling already supports ENS so no jumping through hoops most of the time.
- NetOpWibby 3y ago"web3" is synonymous with Ethereum so that's no surprise to me. What is a surprise is ENS having interoperability with BTC, SOL, &c addresses. I assume these exist as TXT records? Not sure I like exposing that...of course, that's the default with .eth names. The way BTC and HNS works, you can use a different address derived from the same seed and still receive funds. Different strokes for different folks and all that. No one chain will (or should) be THE solve for everything.