Nostr Web Client

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 nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp for nostr, nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tc4uevew for blossom, nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm for loom, nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgawaehxw309a5xzan9dchxgctwvdhkuamp09jx2a3wvdhk6tcfnhk4d (?) 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 nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz769wywf

nostr:nprofile1qqszxgvrzkpasudhvdjx3anl77qxse5wd6eunndmyv9x63uwnpn09mgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcgt4a3x 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

Reply to this note

Please Login to reply.

Discussion

DuhLaurien ✌🏻👽💨 0mo 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 0mo 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.

AU9913 0mo ago

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

Moneta Pro Populo 0mo 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.

AU9913 0mo ago

That is probably your NWC then cus I did it on amethyst and it worked.

Which wallet are you using?

Moneta Pro Populo 0mo ago

Minibits.

AU9913 0mo ago

Does it show that the other payment failed in nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0wsvavr

Moneta Pro Populo 3w ago

There was no other payment.

DuhLaurien ✌🏻👽💨 0mo ago

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

𝐒𝐧@𝐱 0mo 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,

AU9913 0mo 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.

Sir Spencer, Wolf of KC 🐺 3w 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

https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/value.md