There are some things that are not easily accessible in the smart contract, we might need to consider upgrading the contract, such that we can easily fetch some kind of data, without making the contract much more heavy.
[x] We can submit the same data CID over and over again, we might want to add a check in the smart contract, restricting the combination: CID + Submitter.
[ ] We want to specify a minimum amount of participants so we can add this to the accessConditions of the user, this so everyone has the same access conditions, and we can make sure that the NFT creator is able to create a new NFT
[ ] We also want to be able to revoke access to the contract, maybe at a boolean to tableland so we can setShared to false.
[x] Change some of the naming so we have consistent naming pattern.
[ ] Provide CID of lit actions that needs to perform the check
[x] Add job ID of the computation, so the data contributors are able to check which computation will be performed on the data.
[x] Make it possible to add (multiple) categories/traits for the request NFT. Preferably in the same table (if this is not possible, please explain why?)
There are some things that are not easily accessible in the smart contract, we might need to consider upgrading the contract, such that we can easily fetch some kind of data, without making the contract much more heavy.
Please provide feedback on the topics.