search

envoylabs / whoami

An NFT-based user and smart contract nameservice
Apache License 2.0
16 stars 8 forks source link

Addressing and Deref'ing contracts #45

Closed the-frey closed 2 years ago

the-frey commented 2 years ago

Building on #29

Contracts need to be able to be assigned names. However, this is sort of by proxy, as obviously the logic around signer etc won't quite hold. So it needs probably a different path rather than the mint-by-owner path, although the logic will be broadly the same.

The difficulty will be that you could mint a name for somebody else's address given that you can't ensure it is a contract. Or can you? Maybe you could call a WASM message against it to check it's a contract, in the tx?

the-frey commented 2 years ago

Maybe this works together with #41 in that you're actually reifying a different type of edge

the-frey commented 2 years ago

This is achieved in the first instance by a contract with funds calling the nameservice and assigning itself a name. In the meta, is_contract or similar should be set.