Pretty Permanent Domains
One expensive issue with using blockchains for payments is that onchain mistakes are not recoverable. Payment identities like WNS help with human-readability of addresses, but counterparties should have an addressing option that is more or less permanent so that they don't send to Bob.wei but instead get Alice because of domain rotation over time. Each layer of protection that can be offered to allow safer crypto self-custody should always be explored. Blockchain domains like WNS and ENS take the usual path of allowing renewals to promote markets (and so domains are expected to move around). This also helps avoid the potential of canonical domains being locked forever by lost keys, or not being utilized effectively by those who value them most. Other name services like XNS provide what appear to be permanent domains which is good to see in practice as an alternative to this norm, particularly for the payment use case. So that WNS can steer another option here, within our own domain and differentiate on DAO social recovery ("pretty permanent"), I would recommend that we explore leveraging the existing "free" id.wei domain subname registration offered by WNS dapp (wei.domains generally & for multisigs on multisig.software) under the SubdomainRegistrar and purpose this utility towards stable .wei identities (in renewal terms). And market them as such. Towards this end, we can dedicate part of the current DAO treasury to trigger renewal, on a recurring, or indefinite basis of the id.wei domain so that when users get a Bob.id.wei domain, they don't have to worry about their id.wei subname expiring or rotating out, but can otherwise rely on it being under the rules set by the DAO and .wei domain holders (which can also include "locking" it from any changes). This should essentially be zero cost to the DAO treasury since the DAO owns the fees. And effectively, if the DAO renews this fixture for a hundred years, most users will be happy enough with this window - i.e., pretty permanent. To accomplish this onchain, I would transfer the id.wei name NFT to the DAO and also program the SubdomainRegistrar to work much as it does now for id.wei subdomain minting. That's pretty much it. But in this case, the DAO would control the domain and effectively renew it as much as it wants (and can also attach fees to id.wei mints should there be spam issues). Thoughts?
RE: Another convention to explore...
If there is room to extend or brainstorm a bit
idsounds like it's attributable to identity, where aspay.weirhymes (at least in english) and could begin to do smarter concepts for advanced payment-receipt use cases.For instance....
I buy chainpy.pay.wei, put it in a multisig. But, owning chainpy.pay.wei gives me exclusive rights to register enumerable deterministic versions of the same. chainpy.1.pay.wei, chainpy.2.pay.wei, chainpy.3.pay.wei, etc. Then we can do cool things:
Since I've given
chainpy.pay.weito my customers to pay me across dozens of invoices and e-mail chains and it's saved in their contacts, their naive wallets pay my super safe multi-sig directly which is secure but a pain, or their non-naive wallet can iterate upward until it finds 'latest=true'.Just an idea.
RE: XNS
I believe the XNS project attempts block transferability as well. Which, solves some problems, but creates new ones. Plus, the way XNS is set up, there are going to be collisions with web2 and web3 name spaces in the long-run.
I think this is a stronger solution than XNS. And it's a strong idea that's feasible and reasonable. Aligned. I'll leave some other comments, that I'm keen to see how votes come in on...