OceanSlim on Nostr: Networks come and go, (not Bitcoin of course...) but there are tens of thousands of ...
Networks come and go, (not Bitcoin of course...) but there are tens of thousands of networks. I think the spec could define the major ones, but should be left open to the client to determine it ultimately for other use cases. We can't define all networks, but we can do lightning, liquid, Bitcoin, Ethereum and monero for sure.
But if insteadof w you think it's better to do [ "bitcoin", "BTC:<address>] let me know.
It was my thinking that a single letter w tag would be indexed by relays, and clients would want to fetch all potential receiving wallets for the user. The client doesn't necessarily have to interact with a wallet. A copy paste address function is good enough in 90% of cases.
But if insteadof w you think it's better to do [ "bitcoin", "BTC:<address>] let me know.
It was my thinking that a single letter w tag would be indexed by relays, and clients would want to fetch all potential receiving wallets for the user. The client doesn't necessarily have to interact with a wallet. A copy paste address function is good enough in 90% of cases.