The blockchain sets the timestamp at the moment it’s added. All the ‘user’ can do is upload a hash.
Other than that, it doesn’t matter. It just a table of hashes + dates, and hash tells you nothing without the associated file. Fake media could be hashed, but if a timestamp can’t ‘verify’ the media in question for a particular situation, then it wouldn’t matter to a court anyway.
I guess one particular attack vector would be orgs flooding the system, unfortunately, and that would be difficult to work around.
If the timestamp can’t ‘prove’ its authenticity (like placing the video chronologically before anyone would know what slop to make), then it’s useless as evidence in court, even if the video is real.
What ensures that only valid stuff gets pushed in the first place?
The blockchain sets the timestamp at the moment it’s added. All the ‘user’ can do is upload a hash.
Other than that, it doesn’t matter. It just a table of hashes + dates, and hash tells you nothing without the associated file. Fake media could be hashed, but if a timestamp can’t ‘verify’ the media in question for a particular situation, then it wouldn’t matter to a court anyway.
I guess one particular attack vector would be orgs flooding the system, unfortunately, and that would be difficult to work around.
What guarantees that what was uploaded in the first place wasn’t deepfake slop?
Doesn’t matter.
If the timestamp can’t ‘prove’ its authenticity (like placing the video chronologically before anyone would know what slop to make), then it’s useless as evidence in court, even if the video is real.