Post #994220

2025-11-07 14:51 UTC

I know my previous nostr-based payment metadata solution didn&#39;t really get adoption from other PC20 apps - so me and @dovydas have come up with a much simpler solution for LNAddress payment metadata: https://github.com/Podcastindex-org/podcast-namespace/pull/734 TLDR - we use the BOLT11 invoice description field to add a rss::payment prefix along with a URL that returns the full metadata in a x-rss-payment header. From today all LNAddress payments sent from Fountain will use this metadata approach - so feel free to start testing!

Replies (3)

@merryoscar@podcastindex.social 2025-11-07 14:53

Here's an example payment link - https://fountain.fm/episode/JCIzq3VyFKQVkEzVNA8v?payment=5XIAt66P29Iv6rjSTZUB And here's how you can query the JSON programatically via curl: curl -I -s -o /dev/null -w '%header{x-rss-payment}' "https://fountain.fm/episode/JCIzq3VyFKQVkEzVNA8v?payment=5XIAt66P29Iv6rjSTZUB" (note this is URI encoded JSON string)

Open ##1291729
@StevenB@podcastindex.social 2025-11-07 14:53

@merryoscar @dovydas With this solution, will the apps be expected to maintain a database and schema for podcasters to use to fetch their metadata?

Open ##1291732
@ericpp@podcastindex.social 2025-11-10 15:27

@merryoscar @dovydas Is there a way to get this same info from Nostr? It looked like it only contained the feed/item guids whereas this has the entire TLV record. I thinking of the case where someone reinstalls Helipad and it has to batch load a bunch of previously received rss::payment records. Nostr would be more efficient for that than fetching those URLs one at a time.

Open ##1291782