Cryptographic field photo proof (Ed25519, RFC 3161)
Crypto-signed field photos with zero backend trust, but disputes aren't new—and adoption requires both sides.

AI provenance registry when C2PA and Content Credentials already exist.
AI content creators, digital artists, agencies selling AI work
C2PA · Content Authenticity Initiative · Originality.ai
This is not meant to “solve copyright” by itself. It is meant to create a clean provenance record creators can point to when their work is reshared, copied, licensed, or used commercially. With AI after all, even Software Engineers are becoming AI creators as well as their coding agents take over their job, haha.
I’d especially appreciate feedback on:
- What metadata should be included or excluded? - How should proof links balance transparency with creator privacy? - Would studios/AI creators actually use this before publishing?
Also, is there anyone here who would love to try it out and give some feedback, it's like the very first version.
Thanks a lot.
- Celestino (https://x.com/_celestino127)
Crypto-signed field photos with zero backend trust, but disputes aren't new—and adoption requires both sides.
Timestamp-first workflow challenges Day One, now testing native iOS beta via TestFlight.
Focused 4DGS viewer for an emerging tech that lacks dedicated tooling.
Clever crypto stack (Ed25519 + RFC 3161 TSA + GPS) but solves a niche dispute problem solo can't fix.
Searches YouTube transcripts, but Glasp and Eightify already do this.
Frame.io UX for Google Drive videos without the subscription fee or upload sync.