In 2018, I spent six weeks auditing Gnosis Safe’s Solidity v0.4.24 code on a local testnet. I found three signature malleability flaws that early auditors missed. That experience taught me one thing: trust is not a feature; it’s a mathematical certainty you verify yourself. When I read the announcement of Radar Chat — a self-custodial Bitcoin Lightning Network messenger built on a Signal fork — my first instinct wasn’t excitement. It was to check the invariants. And that’s where this story gets interesting.
Radar Chat positions itself as the privacy-first messaging app that finally brings Bitcoin payments to the masses. It forks Signal’s end-to-end encrypted protocol and bolts on a self-custodial Lightning wallet. No KYC, no middleman. The pitch is seductive: combine the gold standard of private messaging with the gold standard of decentralized payments. But code doesn’t lie, and the commentary from the project’s PR machine already hides the hard truths.
Context: What Radar Chat Actually Is
Radar Chat is a fork of the Signal Android client, meaning it inherits Signal’s core protocol: the Signal Protocol for end-to-end encryption, the same server-side architecture, and the same privacy guarantees. On top of that, it integrates a self-custodial Lightning Network wallet. “Self-custodial” means the user controls the private keys and manages the Lightning channels directly. There is no third-party custodian, no hosted solutions like Wallet of Satoshi. The user is the bank.
The project claims this combination will drive mainstream adoption of Bitcoin payments. To anyone who has actually built or used a Lightning wallet, that claim is a red flag the size of a channel close transaction.
Core: The Technical Overhead of Self-Custodial Lightning
The Lightning Network is not a simple payment rail. It is a complex state machine where every payment requires channel management, liquidity balancing, and active monitoring. I’ve seen this firsthand. In 2020, I deconstructed Uniswap V2’s AMM model with a Python simulation to understand slippage mechanics. The constant product formula is elegant. Lightning, in contrast, is a dynamic system where the invariant isn’t a formula but a set of states: the channel balance, the commitment transaction, the revocation keys, the HTLC timeout. Get one wrong, and you lose funds.
Self-custodial Lightning wallets exist — Phoenix, Breez, Zeus. They work because they abstract away the complexity: automatic channel management, liquidity providers, and even a degree of custodial hand-holding. Radar Chat, by going fully self-custodial, inherits all the pain. Users must: - Understand UTXOs and on-chain fees to open channels. - Maintain enough inbound liquidity to receive payments. - Monitor channels for force-close risks due to timeouts. - Run a node (likely embedded) that stays online to forward payments.
This is not a UX that will drive mainstream adoption. The “Lightning Network hides its truth in the channel management invariant” — and that invariant is a headache for non-technical users.
Furthermore, forking Signal introduces its own maintenance burden. Signal’s codebase is actively developed with frequent security patches and protocol improvements. Radar Chat must either keep up with upstream (difficult for a small team) or stagnate. In 2021, during my Axie Infinity forensics, I found a breeding fee calculation flaw that allowed infinite token generation. The vulnerability existed because the team had patched a different component but missed the edge case. Forking adds a long tail of such edge cases. Radar Chat’s team? Completely anonymous. Not a single name on the website. “I don’t believe in projects that ask you to trust without transparency.”
Security: The Unaudited Fork
Signal’s code is battle-tested, but the fork is not. Radar Chat modifies the payment flow, the UI, and the network layer. Every change introduces new attack surfaces. Consider the following: - The Lightning integration likely uses LDK (Lightning Development Kit) or a similar Rust library. LDK is safe, but the binding between Android’s Java code and the native library is a known source of memory corruption bugs. - The Signal fork may have altered the database schema to store channel state. Any misalignment between Signal’s changes and the Lightning state machine could lead to data leaks or fund loss. - The default server used for messaging? Likely the same as Signal’s, but that means traffic metadata is still visible to a central server. The project does not claim federation.
“Zero knowledge isn’t magic; it’s a cryptographic proof. Radar Chat offers no proof of security.” No audit has been published. No bug bounty. The team’s identity is hidden. In the 2022 aftermath of the LUNA crash, I pivoted to studying ZK-SNARKs precisely because they provide verifiable correctness. Radar Chat gives users neither verification nor transparency. That is a gamble, not a feature.
Contrarian: The Real Blind Spot — Project Sustainability
The conversation around Radar Chat usually focuses on technical feasibility: can they make self-custodial Lightning usable? That misses the larger point. The biggest risk is not technical but organizational. The team is anonymous, there is no native token, no disclosed funding, and no roadmap beyond the initial release. This is not a startup; it’s a weekend project with ambitions of a world-changing app.
In my 2024 due diligence on institutional custody solutions for the ETH ETF, I analyzed how even well-funded projects with public teams struggle to maintain security and user trust. Gnosis Safe is a multi-sig standard today because its developers are known, accountable, and responsive. Radar Chat has none of that.
Without a token, there is no incentive for node operators, no liquidity mining, no staking. The value capture goes to Bitcoin and the Lightning network, not to the app. The project must rely on altruism or eventual monetization (e.g., routing fees). But the Lightning routing fees in a self-custodial context are negligible. Users will not pay for the app if they can use Signal for free.
Furthermore, the competitive landscape is brutal. Telegram’s TON integration already offers custodial payments with a user base of 900 million. Phoenix Wallet offers near-custodial ease. Signal itself has 40 million active users but zero payment features. Why would a Signal user switch? The only answer is extreme privacy, but even that is questionable because Signal already provides E2EE.
Takeaway: A Fork in the Road, Not a Path to Adoption
Radar Chat’s announcement is not a sign of mainstream adoption. It is a stress test of the belief that forking and combining two open-source projects is easy. The code doesn’t lie, but the commentary does. The project will likely fade into obscurity within six months unless it makes drastic changes: reveal the team, publish a full security audit, and introduce a token or clear value capture mechanism.
If you are building a Lightning wallet, do not hide your team. Show me the math, show me the audits, and show me the user tests. Otherwise, you are just adding noise to the signal. And as I learned in 2018 from that Gnosis audit, the noise can hide vulnerabilities that cost people real money.
