To the Lightning engineers: has anyone ever thought about crowd sourcing a payment? I'm specifically thinking, what if Alice has a secret that is valuable to the general populace of users; but any one person finds it too expensive. Say 100 people all "chip in": they pay to the secret with 1/100 of the amount. When Alice claims one she claims all if the preimage is the same across all. Does this make sense practically? It's easier to reason about directly onchain since the concept of "publishing" the secret is more unambiguous there. And with routing there can be failures which makes it messier, right.
waxwing
npub1va…knuu7
2026-06-07 19:03:50 UTC
Author Public Key
npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7Published at
2026-06-07 19:03:50 UTCEvent JSON
{
"id": "184c0d13accea6fe7d4f111184f823776b163d6dec1d3794b6e3256d76b773bd",
"pubkey": "675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728",
"created_at": 1780859030,
"kind": 1,
"tags": [
[
"client",
"Primal Android"
]
],
"content": "To the Lightning engineers: has anyone ever thought about crowd sourcing a payment? I'm specifically thinking, what if Alice has a secret that is valuable to the general populace of users; but any one person finds it too expensive. Say 100 people all \"chip in\": they pay to the secret with 1/100 of the amount. When Alice claims one she claims all if the preimage is the same across all. Does this make sense practically? It's easier to reason about directly onchain since the concept of \"publishing\" the secret is more unambiguous there. And with routing there can be failures which makes it messier, right. \n\n",
"sig": "815c1f293e7aede4c1f0c036592f2d931530bdb97c8434da54e2e2360790c433e223a6134acff7fdcd7c59051c6cfbed3a10f97ad670ea40ff817e1ce95cc486"
}