make registry multi-implementation compatible
Darlington02 opened this issue · comments
Currently, the registry contract just stores a mapping of (token address, tokenID) to TBA address.
TODOs
- Expand
create_account
to be able to create as many implementations as possible for a particular NFT. - Ensure
create_account
checks that the caller/msg.sender is the owner of the NFT, to prevent spams. - remove mapping, thus
get_account
should be able to calculate account address if provided the implementation class hash, public key, etc.