Hey Reed, this is what my agent came back with after I mentioned that most users who use NWC with the app won’t have keysend capability:
Two recognized paths:
A — keysend + TLV 7629169 carrying the boostagram JSON (action: "boost", feed identity, episode_guid). Universal.
B — lnaddress + comment rss::payment::boost <metadata_URL> <message> where the URL serves an x-rss-payment header. Their bots only trust fountain.fm, castamatic.com, tardbox.com/boost/ as the metadata domain — not one we control.
(a) add a bullishBoosts‑hosted metadata domain to the bot’s allowlist (his doc already anticipates “podcaster‑configured domains” for Helipad), then we implement Path B properly; or
(b) have the bot ingest our existing kind:1 boost notes and correlate them to settled payments — nothing changes here.
Does this sound right?
The Bullish ₿itcoiner
npub15y…jmpcx
2026-09-03 19:15:21 UTC
in reply to nevent1q…5lnh
Author Public Key
npub15ypxpg429uyjmp0zczuza902chuvvr4pn35wfzv8rx6cej4z8clq6jmpcxSeen on
wss://wot.utxo.onePublished at
2026-09-03 19:15:21 UTCEvent JSON
{
"id": "c3c298d6fed9c671d9b93eac0b178afe04afc1546763ddb61197f739a41a8e85",
"pubkey": "a10260a2aa2f092d85e2c0b82e95eac5f8c60ea19c68e4898719b58ccaa23e3e",
"created_at": 1788462921,
"kind": 1,
"tags": [
[
"e",
"feb631d945055b551840dc89d53be2bc0c26e6a90bc62c9ea14fea3aae47a694",
"",
"root"
],
[
"e",
"8a1f5280e823ad86d93248016d9cccdb30b8b5d4602449b9aeb72e85d3edb7d4",
"",
"reply"
],
[
"p",
"a10260a2aa2f092d85e2c0b82e95eac5f8c60ea19c68e4898719b58ccaa23e3e",
"",
"mention"
],
[
"p",
"32092ec1a258c9f2c11a9a5bb53b127ca20941f1803dd7f6715050ff8e9fd13a",
"",
"mention"
],
[
"p",
"c330881e28768381dd8bdfd274341dca0c5882c29b8642ea4bc82f7563264592",
"",
"mention"
],
[
"client",
"Circl"
]
],
"content": "Hey Reed, this is what my agent came back with after I mentioned that most users who use NWC with the app won’t have keysend capability:\n\n\nTwo recognized paths:\nA — keysend + TLV 7629169 carrying the boostagram JSON (action: \"boost\", feed identity, episode_guid). Universal.\nB — lnaddress + comment rss::payment::boost \u003cmetadata_URL\u003e \u003cmessage\u003e where the URL serves an x-rss-payment header. Their bots only trust fountain.fm, castamatic.com, tardbox.com/boost/ as the metadata domain — not one we control.\n\n\n\n(a) add a bullishBoosts‑hosted metadata domain to the bot’s allowlist (his doc already anticipates “podcaster‑configured domains” for Helipad), then we implement Path B properly; or\n\n(b) have the bot ingest our existing kind:1 boost notes and correlate them to settled payments — nothing changes here.\n\n\n\nDoes this sound right?",
"sig": "3721a888bbe3d7082824ca3a9c6b0e264e1123e1306aebdfa94be424221cdc64c5b96244781f30f0f9327fc05f375eff51f998644d19e28f4a02d31c9d1358a2"
}