Proposed new #superpower for the nostr protocol - using the “o” tag to store the sha256 digest of any original document/byte array (pdf, jpg, bin, etc).
That means the digest is automatically indexed searchable as the “#o” tag in a filter.
I’ve tested it. It works. I am planning to use this for transferable title documents, such as electronic bills of lading (printed as a PDFs).
This approach also releases me from those janky proprietary certificate authority schemes, like Adobe Acrobat that try to trick you into a subscription service when all you want to do is issue and validate the authenticity of a f***ing pdf, without using some paid certificate authority racket.
#Nostr is the protocol that keeps on giving.
Over the weekend, I experimented with publishing events with an “o” tag having the sha256 digest of an original document (pdf, jpg, etc). Then using a separate script to calculate the digest of a selected document to see if there is a corresponding event. It worked, because according to NIP-01, single letter tags are indexed, so I could filter for the event.
This is a big deal because now I have the basis to build an electronic transferable record (ETR) system that does not require any “blockchain”. This can be used to manage title documents such as a bills of lading. Even, better, since payments is already tightly integrated (nip57, lud16) adding payments for title transfer will be a breeze!
Onward!