gudnuf on Nostr: Testing out shipyard.pub by PABLOF7z Anyone curious how a note could be a prism? You ...
Testing out shipyard.pub by PABLOF7z (npub1l2v…ajft)
Anyone curious how a note could be a prism? You should check out NIP 57 - Appendix G. NIP 57 is where all the specs for zaps live.
Appendix G specifies that a note can have many 'zap' tags each with a *pubkey* and *relative split*. Clients that support this will calculate the receiving address of each pubkey, and how much to send based on the percentage of their split relative to the total being zapped.
Under the hood, the client is individually zapping each recipient.
Go to any prism created by prism (npub1arc…ggtw) and inspect the raw event detail to see what I mean. You'll hopefully see something like this:
[
"zap",
"65478d9d539a83637267d85c69ddfdc1d579af6d728e256402f0a8a839e05ea8",
"wss://relay.damus.io",
"1"
],
[
"zap", "b624f6d00150f62f69eb305d3339db2ff98d5ce777b89d2cfbe7569717494791",
"wss://relay.damus.io",
"1"
],
[
"zap", "b43c91f2a7b9d21bba3ddb08cc321840df249364fb716213508bb17383e1d930",
"wss://relay.damus.io",
"1"
]
Anyone curious how a note could be a prism? You should check out NIP 57 - Appendix G. NIP 57 is where all the specs for zaps live.
Appendix G specifies that a note can have many 'zap' tags each with a *pubkey* and *relative split*. Clients that support this will calculate the receiving address of each pubkey, and how much to send based on the percentage of their split relative to the total being zapped.
Under the hood, the client is individually zapping each recipient.
Go to any prism created by prism (npub1arc…ggtw) and inspect the raw event detail to see what I mean. You'll hopefully see something like this:
[
"zap",
"65478d9d539a83637267d85c69ddfdc1d579af6d728e256402f0a8a839e05ea8",
"wss://relay.damus.io",
"1"
],
[
"zap", "b624f6d00150f62f69eb305d3339db2ff98d5ce777b89d2cfbe7569717494791",
"wss://relay.damus.io",
"1"
],
[
"zap", "b43c91f2a7b9d21bba3ddb08cc321840df249364fb716213508bb17383e1d930",
"wss://relay.damus.io",
"1"
]