@merryoscar@podcastindex.social
Post #1839212
2026-02-24 21:23 UTC
@StevenB
we could - there's just the question of how to avoid fake data if anyone can post payment metadata to a public API endpoint
with the rss::payment spec the url to fetch the metadata originates in the payment comment - so there is a direct tie to the actual payment and since apps host the full metadata on a url their reputation is at stake if they fake data
I am open to exploring solutions to this where apps don't have to host the payment urls - and promise I won't mention nostr 😅
Replies (1)
-
@StevenB@podcastindex.social 2026-02-24 21:27
@merryoscar 1) I send you the data, you send me a unique url 2) I send the payment and include the unique url in the message. 3) Fountain hosted wallets get the payment with the message, look in the database to find the metadata that's tied to that unique url found in the message and marks it as paid or verified. 4) You don't have to trust any of the apps, just that your wallet got the payment with the unique url generated by your server.