Oh, I have no idea how it could be achieved. Just saying it would be cool if it could act like that. I assume that pooling and allowing stakeholders to withdraw would make it easier. But then the pool holds the funds and as it grows attacks become more and more tempting to bad actors.
Discussion
Pool works just as you described but the split doesn’t happen on every zap but after some time. This reduces the failed invoice rate
At least that’s how I understand it. Maybe nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 can share more insights
Interesting. So we’d just need to find a way to have the pool become the zap target for a track or other collaborative content. Can I make a single note have a different zap address than the other in some clients?
Prisms might make it an instant payment to multiple parties.
Seems some devs find them unsafe at the moment. It’s all beyond my understanding of things. I’m just playing with the idea of nostr content distribution, use code to replace greedy lawyers and accountants. Have zap flow because of content, use the flow of zaps to support infrastructure…
I think all of this is already possible technically