Discussions

Ask a Question
Back to all

Can transaction metadata hold a consent manifest hash for media generation?

I am evaluating a provenance record for a two-image video input flow . Before a generation request, the application can create a small manifest containing the two asset hashes, consent flags, duration, aspect ratio, and a schema version. I do not want to put the source images, names, or other personal data on-chain.


Would it be reasonable to canonicalize that JSON, compute a SHA-256 digest, and store only the digest plus schema version in a TrustNote transaction? Is there a recommended data field and practical byte limit for this kind of application metadata?


I would also appreciate guidance on updates. If one source photo is replaced before the final render, should the client write a second record that references the first digest, or simply treat the previous manifest as abandoned and record only the final one?