
CD207: SETH FOR PRIVACY - RADAR - BITCOIN IN SIGNAL
By ODELL
Aired Jul 8, 2026 · 1h 4m · Last boosted Jul 11, 2026
Chapters
Show Notes
Seth For Privacy joins to chat Radar, a new app that adds Bitcoin payments directly into Signal. We discuss forking Signal while keeping full account and chat compatibility, why they built on Signal’s network instead of Nostr or SimpleX, donating back to Signal Foundation, and how end-to-end encryption keeps payments invisible even to Signal. Then we go deep on the tech: Spark versus Ark trust models, unilateral exit, privacy tradeoffs, Lightning interoperability, seed backups tied to your Signal account, stable balances, on and off ramps, and the goal of bringing Bitcoin to everyday chat users. Radar: ht...
Nostr Boost Stats
- sats
- 16k
- boosts
- 6
- boosters
- 4
- sats
- 0
- boosts
- 0
- boosters
- 0
- sats
- 0
- boosts
- 0
- boosters
- 0
- sats
- 16k
- boosts
- 6
- boosters
- 4
Nostr Community
Everyone who has boosted CD207: SETH FOR PRIVACY - RADAR - BITCOIN IN SIGNAL on Nostr, ranked by sats sent, all time.
- Johnny Stimulus 10k sats
-
Oscar Merry
5k sats
-
btconboard #LNHANCE or #CTV
300 sats
- npub1m0gm4…7lad 250 sats
Episode Boosts
Every boost sent to this episode, as published to Nostr, newest first.
-
Great rip guys
-
If it doesn’t have in app unilateral exit, it’s custodial, period. This is not negotiable. If something is not implemented then it simply doesn’t exist for the average user. 99.99999% of Spark users don’t even know a CLI app exists let alone how to use it. Without local caching and unilateral exit actually implemented in the app and having hard dependency on operator cooperation to exit then it’s custodial. Listen I actually like Spark and think it makes reasonable tradeoffs in a world without covenants, but as it stands it’s a custodial product. Happy to revise this once we see an actual implementation of unilateral exit and more operators and LSPs, but it’s just the honest reality today.
-
If it doesn’t have in app unilateral exit, it’s custodial, period. This is not negotiable. If something is not implemented then it simply doesn’t exist for the average user. 99.99999% of Spark users don’t even know a CLI app exists let alone how to use it. Without local caching and unilateral exit actually implemented in the app and having hard dependency on operator cooperation to exit then it’s custodial. Listen I actually like Spark and think it makes reasonable tradeoffs in a world without covenants, but as it stands it’s a custodial product. Happy to revise this once we see an actual implementation of unilateral exit and more operators and LSPs, but it’s just the honest reality today.
-
Very informative thank you!
-
-
👍🏻🫡👍🏻

















