Adding support for Dynamic and Nested NFTs

[AnmolSirola]

To Implement Support for Dynamic and Nested NFTs, we add the following changes to our project:

First, we will create an ERC-721 compliant smart contract. This contract will include the standard functions required by the ERC-721 standard. To support metadata for each NFT, the contract will implement the tokenURI function, which returns a unique URI for each NFT. This URI can point to a JSON file containing metadata such as the NFT's name, description, image, and other properties.

With this basic ERC-721 contract in place, we can proceed to make the necessary changes to support dynamic and nested NFTs:

1) Smart Contracts:

• Add an NftType enum to differentiate between static, dynamic, and nested NFTs.
• Modify the NftData struct to include fields for nftType, parentId, and childIds.
• Adding the createStaticNft function that creates a new static NFT with the specified recipient and token ID.
• Adding the createDynamicNft function that creates a new dynamic NFT with a new token ID and the specified recipient.
• Adding the createNestedNft function that creates a new nested NFT with a new token ID, the specified recipient, and the parent NFT ID. It also adds the child NFT ID to the childIds array of the parent NFT.
• Adding the getChildNfts function that returns an array of child NFT IDs for a given parent NFT ID. (used to retrieve child NFTs for the nested NFTs)

2) Contract Interaction Functions:

• First we will update the deployment functions to include the new NftType enum and NftData struct.
• Then we will modify the minting functions to support dynamic and nested NFTs, accepting parameters for NFT type and parent ID.
• We will also implement new functions for creating dynamic and nested NFTs, interacting with the corresponding smart contract functions.
• At last, we will add a function to retrieve child NFTs of a parent NFT.

3) Collection and Contract Classes:

• We will then update the Collection class to include properties and methods related to dynamic and nested NFTs, such as creating, retrieving, and updating metadata.
• After that the contract class is updated to incorporate the NftType enum and NftData struct, we will update the relevant methods accordingly.
• At last we will handle the Storage and Metadata Management by:
  • Firstly, enhancing the storage classes to handle metadata for dynamic and nested NFTs, including methods for updating and versioning metadata.
    • Secondly, modifying the metadata structure to include fields for NFT type parent ID, and child IDs.