I don’t do crypto. #icymi

Alright. So nix on this idea. That was fun.

Does this actually work? How to keep the stink down … cause cats don’t flush also?

Sad people.

How fun. Big Nostr Energy is best when shared with others. 💜

Amazing. 👀

It’s like those doctors of olden times who would test their concoctions on themselves first. Famous last words : “let’s just see here if this thing actually works …”

I was wondering what happened. All of a sudden … Derek went dark.

Here’s what I’m thinking, for “smart contracts” to control file download over lightning and Nostr … - author creates a blob (file) for paid access and generates a unique Nostr pubkey only for this blob. - author encrypts the blob (nip 04 style) with their own key AND the blob specific key. - author adds the blob pubkey as “p” tag to the blossom event which uploads the blob to a server. (Requires update to blossom NIP) - author uses Frostr to shard the blob private key as many times as desired. - author creates a key shard for use by every user who pays for access to the blob. - using Frostr tools, author can keep track of every every time any shard is used to decrypt the blob. - this is mostly trustless for the author to maintain access control of the blob download, except for the requirement to “trust” the Frostr key and shard management tools. Do you have thoughts? - the problem I’m aware of is trustlessness for the person who pays for blob access. Is there a way cryptographically to assure that their lightning payment actually triggers a shard generation of the blob key? - similarly the above would also work for advertisers to “assure” that a blob (ad image) has been accessed (viewed) … but I also wonder how to incorporate payments in a trustless manner. I’m really not sure what’s possible with scripts on L2, or lightning specifically. Your feedback would be greatly appreciated.

Come for the freedom. Stay for the people. Nostr is a funny place.