4 ms·

Imagine a cryptocurrency like log of data verifying images. Essentially, all cameras will be internet connected with a process to force creation of an NFT at th

Imagine a cryptocurrency like log of data verifying images. Essentially, all cameras will be internet connected with a process to force creation of an NFT at the moment users press the photo button which includes the entire data of the image. Any image without that tech will be considered unreliable. Of course that would have implications that no photo could ever be deleted, I’m guessing this system would be government based and they would be just fine with that.

rspeele 5y ago
What can crypto verify here exactly? What stops me from: A. Writing my own software "camera" that does the same gyrations a real camera would do to sign its raw image, but applied to an arbitrary unverified image file on my computer? or B. Printing out an unverified picture and taking a picture of that picture (with good lighting etc so that it is not obvious), with a camera that makes it verified "real"?
- recursive 5y ago
  A. wouldn't work because there would presumably be a private key or something. B. seems like it would work.
kkielhofner 5y ago
This is exactly what my new startup Tovera[0] does. Process is roughly: 1) Upload image with web-based user dashboard. 2) We strip existing metadata (for privacy and all of the reasons everyone else does). 3) Our API generates a unique identifier for the asset (UUIDv4 in hex). 4) The unique identifier is embedded in the image with XMP. 5) A SHA256 checksum of the entire file is generated. 6) Via the API the checksum is associated with the unique identifier (along with some other stuff). 7) (Optionally) the unique identifier and checksum are added as JSON to IPFS via a pinning service and (essentially) an NFT is minted for the JSON verification data on the Polygon blockchain. 8) The user gets sharable[1] and iframe embeddable[2] links and the ability to post directly to various social media networks, etc. When the links are viewed our Javascript reads the unique id, fetches the stored checksum from the API, and generates a new checksum of the image in the browser. If the checksums match a clickable icon appears in the top right of the image with additional information about the image, links to the IPFS and blockchain links, etc. Users can change the additional metadata at anytime and it updates instantly. Long term goals are hosted javascript verification library, browser extensions, mobile SDKs, potential browser/OS integrations, native plugins for popular authoring/editing applications, and so on. Happy to answer any questions! [0] https://tovera.com https://tovera.com [1] https://share.tovera.com/preview/c65b0658ab6e4d89963b1e0a319a1c0a https://share.tovera.com/preview/c65b0658ab6e4d89963b1e0a319... [2] https://share.tovera.com/embed/c65b0658ab6e4d89963b1e0a319a1c0a https://share.tovera.com/embed/c65b0658ab6e4d89963b1e0a319a1...

rspeele 5y ago

What can crypto verify here exactly? What stops me from: A. Writing my own software "camera" that does the same gyrations a real camera would do to sign its raw image, but applied to an arbitrary unverified image file on my computer? or B. Printing out an unverified picture and taking a picture of that picture (with good lighting etc so that it is not obvious), with a camera that makes it verified "real"?

recursive 5y ago
A. wouldn't work because there would presumably be a private key or something. B. seems like it would work.

kkielhofner 5y ago

This is exactly what my new startup Tovera[0] does. Process is roughly: 1) Upload image with web-based user dashboard. 2) We strip existing metadata (for privacy and all of the reasons everyone else does). 3) Our API generates a unique identifier for the asset (UUIDv4 in hex). 4) The unique identifier is embedded in the image with XMP. 5) A SHA256 checksum of the entire file is generated. 6) Via the API the checksum is associated with the unique identifier (along with some other stuff). 7) (Optionally) the unique identifier and checksum are added as JSON to IPFS via a pinning service and (essentially) an NFT is minted for the JSON verification data on the Polygon blockchain. 8) The user gets sharable[1] and iframe embeddable[2] links and the ability to post directly to various social media networks, etc. When the links are viewed our Javascript reads the unique id, fetches the stored checksum from the API, and generates a new checksum of the image in the browser. If the checksums match a clickable icon appears in the top right of the image with additional information about the image, links to the IPFS and blockchain links, etc. Users can change the additional metadata at anytime and it updates instantly. Long term goals are hosted javascript verification library, browser extensions, mobile SDKs, potential browser/OS integrations, native plugins for popular authoring/editing applications, and so on. Happy to answer any questions! [0] https://tovera.com https://tovera.com [1] https://share.tovera.com/preview/c65b0658ab6e4d89963b1e0a319a1c0a https://share.tovera.com/preview/c65b0658ab6e4d89963b1e0a319... [2] https://share.tovera.com/embed/c65b0658ab6e4d89963b1e0a319a1c0a https://share.tovera.com/embed/c65b0658ab6e4d89963b1e0a319a1...