Thread - Nostr Hypermedia

AU9913 auggie@nakaMOtown.com 2 months ago

How would I integrate royalties voluntarily into zaps so users don't have to pay multiple invoices? I would like to add 1% to the inventor of any protocol/client I use for a given operation, ie @fiatjaf for nostr, @hzrd149 for blossom, @Arjen for loom, @DanConwayDev (?) for grasp when I create an invoice for a CICD pipeline on nostr. Another example would be to have a percentage of my zaps on regular notes go to @Amethyst @Sir Spencer, Wolf of KC 🐺 do you have any ideas based on what you do with PC2.0? BC the only way I can thing to do it would be to setup a new ln address and have something in the backend that does the accounting #asknostr

Replies (12)

DuhLaurien ✌🏻👽💨 duhlaurien@nostrplebs.com 2 months ago

There is an option called "split and forward zaps" on Amethyst (when it works) or "zap splits" on NoStrudel where you can add npubs with percentages of the value split from zaps you want forwarded to them. In RSS, we use the value tag to add splits.

AU9913 auggie@nakaMOtown.com 2 months ago

Last time I used this it made me pay 1 invoice per user. I think that how it has to work with the existing setup because you need a backend server.

3 replies ↓

AU9913 auggie@nakaMOtown.com 2 months ago

Well shit, I guess that has been upgraded.... Guess I'm making a feature request to @Amethyst so i can set a global value.

Moneta Pro Populo monetapropopulo@btcwill.win 2 months ago

It did not split on Amethyst. It sent one one invoice, half, to a single individual. It did not to a second for the remainder.

1 replies ↓

AU9913 auggie@nakaMOtown.com 2 months ago

That is probably your NWC then cus I did it on amethyst and it worked. Which wallet are you using?

1 replies ↓

DuhLaurien ✌🏻👽💨 duhlaurien@nostrplebs.com 2 months ago

My understanding is that's how LNURL payments work versus keysend, which is what has been historically used on the RSS side.

Moneta Pro Populo monetapropopulo@btcwill.win 2 months ago

Minibits.

1 replies ↓

𝐒𝐧@𝐱 _@lifelog.be 2 months ago

I think zap splits is the answer. It needs to be invisible for the user though, they need to approve a single payment and the split is handled in the background,

1 replies ↓

AU9913 auggie@nakaMOtown.com 2 months ago

Yeah, but I believe that depend on the clients supporting it and maybe their wallet. BC I just zapped that post using primal and it didn't respect the splits.

AU9913 auggie@nakaMOtown.com 2 months ago

Does it show that the other payment failed in @Minibits

1 replies ↓

Moneta Pro Populo monetapropopulo@btcwill.win 2 months ago

There was no other payment.

Sir Spencer, Wolf of KC 🐺 spencer@nostr.fan 2 months ago

In the PC 2.0 world we have typically defined value splits in an RSS feed and allowed apps to generate keysend payments on behalf of the payer based upon those split percentages

GitHub

podcast-namespace/docs/examples/value/value.md at main · Podcastindex-org/podcast-namespace

A wholistic rss namespace for podcasting. Contribute to Podcastindex-org/podcast-namespace development by creating an account on GitHub.