Iām looking for an implementation of the āNFT Project owner (automatically) gives out ENS subdomain to holdersā, especially a version of the implementation that works even when NFTs are transferred.
I know I can search Twitter and reverse engineer some things on Etherscan, but Iām wondering a bit more generally if there is a repository of Interesting Ideas that are implemented on top of ENS?
If itās a brand new NFT contract, then that could be built into the contract itself. Basically the NFT contract would be the owner or approved operator for your ENS name, and then the transferFrom / safeTransferFrom methods would also call setSubnodeRecord to transfer the subname automatically, whenever the NFT itself gets transferred.
If itās an existing NFT contract, then youād need to setup a separate āclaimā contract. That way even if the NFT gets transferred/sold, the new owner can still claim their subname at any time.
In either case the subnames would not be Emancipated in the wrapper, because otherwise the contract would not be able to automatically replace subnames. So that means the owners of the subnames would not be able to use owner-controlled fuses or fuses on any sub-subnames. However you would still be able to use parent-controlled fuses (āperksā) on the subnames if you wanted to.
We have this functionality as well with Bored ENS Yacht Club (BENSYC).
Also the NFT is āname boundā to subdomains on multiple roots, so when the NFT both x.BoredENSYachtClub.eth & x.bensyc.eth are automatically transferred/records updated.