You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the NFT is projected into the game, we need to know which address owns the NFT inside the game
In the PHK case, this is obvious (same person that owns the PHK)
However, in the Owner::NFT and Owner::Receipt case, it's not obvious who owns the projected NFT in the game
Simple solution
For these cases, we will probably need to add an extra key in the datum that encodes who owns these projected NFTs
Complex solution
If we have to add a datum to encode the owner of the project NFT anyway, we may want to consider allowing ownership of the projected NFT to be more flexible. That is to say, right now they can only be owned by a Cardano L1 PKH, but maybe we should generically allow giving permission to a L2/sidechain address (ex: EVM address) or an EVM contract (to support account abstraction), etc.
The text was updated successfully, but these errors were encountered:
Problem
When the NFT is projected into the game, we need to know which address owns the NFT inside the game
In the PHK case, this is obvious (same person that owns the PHK)
However, in the Owner::NFT and Owner::Receipt case, it's not obvious who owns the projected NFT in the game
Simple solution
For these cases, we will probably need to add an extra key in the datum that encodes who owns these projected NFTs
Complex solution
If we have to add a datum to encode the owner of the project NFT anyway, we may want to consider allowing ownership of the projected NFT to be more flexible. That is to say, right now they can only be owned by a Cardano L1 PKH, but maybe we should generically allow giving permission to a L2/sidechain address (ex: EVM address) or an EVM contract (to support account abstraction), etc.
The text was updated successfully, but these errors were encountered: