Podcasting 2.0 value block did V4V better than Zaps.
From the start they thought of the self sovereignty ease. All you need is a node pub key, no lnurl, no ln address.
They implemented splits for the value flow. Each boost or streaming payment calculates splits to each person in the value flow. The app developer gets a cut, the feed is the source of truth with how the rest is split up.
By default it doesn't reveal the identity of the sender, there is an optional name field that can be set to anything, no tied identity.
Is it perfect? No. But it's implemented better and fairer than Zaps.
Not Sure
npub1n0…d04ya
2023-03-21 15:43:35
Author Public Key
npub1n0tsuresxrr9gcywtwgevyv2wahjvzyk8p8hmw0gtyweql0mh4cssd04yaPublished at
2023-03-21 15:43:35Event JSON
{
"id": "3a5180c7a943b2b19655263e59a84e6224e6743eb5cf613e4ba103a4414b5522",
"pubkey": "9bd70e0f3030c654608e5b9196118a776f260896384f7db9e8591d907dfbbd71",
"created_at": 1679409815,
"kind": 1,
"tags": [],
"content": "Podcasting 2.0 value block did V4V better than Zaps. \n\nFrom the start they thought of the self sovereignty ease. All you need is a node pub key, no lnurl, no ln address.\n\nThey implemented splits for the value flow. Each boost or streaming payment calculates splits to each person in the value flow. The app developer gets a cut, the feed is the source of truth with how the rest is split up. \n\nBy default it doesn't reveal the identity of the sender, there is an optional name field that can be set to anything, no tied identity. \n\nIs it perfect? No. But it's implemented better and fairer than Zaps. ",
"sig": "865bd5e9b1230c701105abb73d7385a85e053c0b29721b4c09dc77707b2490abeee99f39b761b97e7c4a743bf81733f0c4eb16c54d2177b84416e85cb0a840fc"
}