$updog

Working on a fix

Yeah, the client needs to support zap splits, but essentially you fetch invoices from each users, lighting address, and pay all the invoices.

Currently snort, amethyst, and http://zapper.nostrapps.org support paying zap splits.

Prism creation is made possible through this often overlooked part of the zap spec https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-g-zap-tag-on-other-events

This part of the spec allows you to add multiple zap tags to a single note, each with their own relative weight split.

This is essentially a prism, our service simply coordinates the creation of these zap split notes.

This is a cool idea, and I thought about it a lot myself but sadly there’s not a very clean solution with lightning. From what I can tell the only way to make this possible today with lightning would be to take custody of it upfront when the prism is created through some kind of escrow. But I don’t think that’s a great idea.

Although If you knew the recipients in the prism upfront I believe this would be possible with HODL invoices.

Create a prism from any note after the fact 👀 nostr:note10h0h56ssnqmyycalnh04a6ty0k6gmpsdz6q3xsg7l0r60aahs4xsq4pzev

Just checked again, there’s no error message or really any kind message I’m able to catch except for the onClose which is throwing an error code 1006. When I switch the event kind to 1 and remove the parameterized replaceable event tags blastr accepts it.

Here is an example crosspost note that fails on blastr: note1fdvjrf6n7k659vy6zveds9qqf52eagjlq2gv2ds73ueh7rhttk7s82rud3

Looking now!

LFG

I got to build crossposting to nostr on stacker.news, it was a lot of fun! Only discussion posts for right now, polls, jobs, and bounties coming soon tm.

https://stacker.news/items/274643

note1aalsryyzglk6kryprwewdhxlvtyqj38szc7gd4mc9jr6z6cs4ttsa9usc3

What do you call it when a Bitcoiner has blue balls?

Unspent transaction output

What is something that both nostr users, and nostr developers are tired of seeing?

AI generated NIPS.

Tailwind can be so grim sometimes:

“justify-end self-end” 😥

Does lightning.video have an API?

Hey nostr, you’re smart. Is there a way I could broadcast a note offering a video for sale. The note would contain all of the metadata about the video but the .mp4 url itself would be encrypted (or else someone could take it without paying) I would want it to be a flat price and would want there to be no interaction required for someone to pay for the video (perhaps by zapping the note) and then receive the decryption key to decrypt the url?

I think it could be possible with lnurl LUD-10 success action potentially if the seller pregenerates a preimage that acts as the encryption key for the url in the note?

AFAIK they only support the zapping of notes with multiple zap tags not the creation of of those notes (let alone logic around who gets to become one of the zap recipients in the prism)

You need to zap the bots quote note of the OP’s note.

Since we don’t know who the re-posters will be upfront, and we can’t edit the note after the fact, we have to create a new note with the zap tags of all of the re-posters.

Ideally, it will incentivize engagement by giving those who engage with a note a split of the zaps that note receives

Right now we have to do it via proxy through another note though.

We want to find a way to build this natively in the spec, but this is our first iteration.

Here is a note with a prism tag. The prism tag is $boost

Now what will happen is after either 10 reposts of this note or 12 hours our bot npub12u7xgzak939jlap3fnev05eky6d4ntwr4lrs03kgnnfd9njmtvrsr9jjmt will create a new note quoting this one and featuring a zap split of all of the reposters.

When you zap that note, the sats will be split across all of the first 10 reposters

Yeah need to add a more technical explanation.

Basically we have a server that listens for any of the $prism tags (only have boost at the moment) and after 10 reposts or 12 hours it will post a new note with the reposters included in the zap tags

https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-g-zap-tag-on-other-events