I know this sounds as boring as hell, but the killer use case for #nostr might be the “Verifiable Presentment Layer”.

Remember, “Electronic Bill Presentment” (EBP) of the 90s? Likely not, but that is the protocol you use to pay your online bills. Boring as hell, but critical. Now here we are almost 40 years later, still sending sensitive documents through LLM-slurping, attention-stealing email services, with nary a thought.

Today, my dentist sends a referral to another dentist via email, and I (not being party to the transmission) start getting ads.

Unacceptable.

We need something more secure and open, which I believe only #nostr can deliver being the base protocol.

Tomorrow, it will be “Verifiable Record Presentment.”

Onward!

nostr:note1qanmaregqx6vk6yxs36u5xj9r7wm2d3dczgzrg2m5g8s4em3zmkss70dy7

Reply to this note

Please Login to reply.

Discussion

You thinking public key verification will still need to happen in person or in person with reputable third party?

So maybe your dentist confirms with new dentist you are this public key?

That really depends on the kind and business requirements. The first area I'm tackling is health- the simplest might be a Doctor's note that is verified against a set of npubs. As I discover domain-specific requirements, I try to generalize as quickly as possible into infrastructure requirements.