My biggest concern is future compatibility and needing to somehow re-calculate the entire tree of certifications if there’s some new header that needs to be added. Are NFT has a number of importance of expose the info with every NFT in the collection. These are generally exposed to Jason files so that’s easy to query and get all the info about a particular Nft. We also allow multi library to be put into each nft at each of that is certified as well. I’m just trying to think about how we would even convey to a user who’s trying to upload their library. What they need to do about this. We want it to be extensible and allow the user to decide, but it’s one thing to know you want to upload three pictures, it’s another to have to think about how long you want them cached for.
I guess this answers my question. Looks like we’re going to have to have some kind of structure that looks like an HTTP response and that will be encoded somehow? We take the hash of the whole thing and store that? Does it still go in a particular sub tree of the canister certification?
Very helpful responses all around. I’ll reach out directly and maybe we can work through it and figure out a path to get motoko working.