Private communications without product sprawl
Cyber Phone is not just another messenger. It replaces the stock dialer and SMS app, adds optional device-to-device mesh transport, and embeds Bitcoin tools directly into the same contact and thread workflows you already use. No ad stack. No mandatory cloud account. No need to juggle separate apps for calling, messaging, fallback networking, and value transfer.
Live interface
Core stack
Communications
Cyber Phone handles the daily essentials: calls, SMS, MMS, thread management, caller actions, and contact-linked messaging. It is meant to be the app you actually live in, not a niche overlay that only works for one protocol.
Mesh
When ordinary connectivity gets weak, optional mesh messaging and calling can switch to nearby radios and relay routing. That makes Cyber Phone unusual: the fallback path is part of the product, not an afterthought bolted on through a separate app.
Identity
Contacts are not just address-book entries. They can become launch points for calls, messages, payment requests, QR exchange, and shareable identity data, so fewer tasks require bouncing between disconnected screens.
Network posture
Most communication apps assume one backend and one happy path. Cyber Phone does not. The core dialer and message state can remain device-local. Mesh transport can activate only when you want it. Wallet features only reach external Bitcoin infrastructure when you explicitly use them.
That separation is what makes the app resilient. It keeps permissions, routing behavior, and data exposure tied to the feature you selected instead of forcing every task through the same monolithic cloud dependency.
Contacts, call history, thread metadata, and app configuration stay device-bound unless you choose to export or share them.
Nearby discovery and relay routing only activate when mesh is enabled, giving you an alternate transport instead of a hard outage.
On-chain and Lightning operations can reach the required remote systems, but only when you invoke those payment features yourself.
Bitcoin features
Send and receive from the integrated wallet flow, with address sharing built into the same contact surface used for calls and texts.
Lightning send flows and recurring LNURL-style addressing fit into the same UI, so payments do not require a separate app or mental model.
Fedimint support is compiled from pinned source and remains optional, giving power users federation-backed workflows without forcing them on everyone else.
Feature demos
Wallet
Pay and receive without jumping into a separate wallet.
Actions
Call, message, pay, and manage details from one menu.
Messaging
Modern reactions and thread controls stay in the same screen.
Detailed feature set
Secure channel flows can use cryptographic identity and public-key exchange so sensitive conversations and high-trust actions are not limited to plain SMS semantics.
Spam controls and thread filtering help keep unsolicited traffic out of the way without forcing your core messaging workflow into a separate app.
Payment requests, wallet details, invoices, and contact-linked money flows can travel through the same messaging surfaces you already use, including resilient mesh paths where available.
Wi-Fi Direct, Bluetooth LE, and Wi-Fi Aware discovery modes can be combined with routing controls so nearby devices become fallback communications infrastructure.
Contacts can be shared as visual QR handoffs or portable vCards, with room for wallet and cryptographic identity details instead of just a name and number.
Cyber Phone keeps inline thread actions, message composition, and iMessage-compatible reactions together so the app feels current while staying interoperable.
On-chain, Lightning, LNURL-style addressing, and optional Fedimint federation support live in the same product instead of requiring a second wallet app and a second trust surface.
Signed releases, open source code, and a hardened dependency posture make the app inspectable. You can audit what it is, how it builds, and what it ships.
Operational links
