Sovereign secure communications
Communications that do not depend on the network.
BitMadWall turns the handsets already in the field into the network. Encrypted messages and signed Bitcoin transactions relay device to device, with no carrier, no SIM and no server in the path.
How it worksStep 01
Every device is a node
No tower, no server. Each handset discovers the handsets near it over Bluetooth Low Energy and Wi-Fi Direct, and forms a network out of what is present.
Step 02
Traffic moves hop by hop
Encrypted messages pass from device to device, up to seven hops from the sender. Reach depends on how many devices are present, not on coverage maps.
Step 03
Only the recipient can open it
Every message is signed by its sender and sealed for its recipient. The devices in between confirm nothing was tampered with and pass it on, without ever being able to read it.
Step 04
One node reaches the internet
The first device to regain a route broadcasts the Bitcoin transactions it is already holding, and completes the message paths that needed one foot online.
Capability that does not depend on infrastructure.
Encrypted mesh messaging
One-to-one and group messaging with no carrier in the path. Content is encrypted on the device and signed by the sender before it is handed to the mesh.
Offline Bitcoin transfer
Construct and sign a Bitcoin transaction with no connectivity. The signed transaction travels the mesh until a device with a route to the internet broadcasts it.
Extended range over LoRa
Paired LoRa hardware lifts a single hop from tens of meters to kilometers, joining clusters that phone radios alone cannot bridge. Phone radios remain the default fabric.
Identity is a key pair
No phone number, no email, no SIM, no registration. A user is a cryptographic identity held on the device and verified in person or by QR code.
Self-healing routing
Messages spread device to device with a strict hop limit, and no device carries the same message twice. Every phone that joins adds another path, so the network gets stronger as it fills rather than slower.
Store and forward
When no path exists, the message waits. A handset carried into range of the recipient delivers it later. Delivery is delay-tolerant by design, and stated as such in the interface.
The drawings behind the claims.
Three sheets from the engineering set, published as drawn. The page above says it plainly; these say it precisely, with the byte counts and the named standards, for the reader who evaluates before they trust.
Chat module
One message end to end: sealed and signed on the sender's phone, hopped through the mesh, verified and opened only on the recipient's.
Wallet module
A payment built with no network: keys that never leave the phone, a payment signed in memory, and the gateway hand-off that reaches the chain.
Transport module
The radios and the air they share: Bluetooth and Wi-Fi Direct as one carrier, the airtime budget, and how separate clusters bridge.
Security
Trust placed in cryptography, not in an operator.
AES-256-GCM
Message content is locked on the device before it leaves. The phones that pass it along carry sealed data they cannot read.
Double ratchet
Signal-style ratcheting. Compromise of one session key does not expose earlier traffic.
No servers
No service holds messages, contacts, or keys. There is no archive to seize, subpoena, or compel.
Panic wipe
One gesture destroys identity keys and message history on the device.
Deployment contexts
Where the network cannot be assumed.
Continuity of government
Hold a chain of command open while public networks are down or saturated. Runs on the handsets staff already carry, so there is no network infrastructure to procure, deploy, or defend.
Disaster response
Coordinate inside an affected area in the first hours, before power and backhaul return. Every responder carrying the application extends the coverage of the whole team.
Field operations in denied environments
No SIM, no subscriber record, no registration on a carrier network. Optional cover traffic and randomized send delays reduce what a passive observer can infer from radio patterns.
Areas without coverage
Border districts, valleys, maritime routes, and rural areas no carrier has built out. The network is formed by whoever is present, and grows as more people arrive.
FAQ
Frequently asked questions
Direct answers on operating without a carrier, mesh range, offline Bitcoin transfer, and what BitMadWall does not do.
Communication continuity when the usual network is unavailable or cannot be relied on: infrastructure failure, disaster response, shutdown and censorship events, denied or degraded environments, and areas no carrier has ever covered. Devices relay for each other, so a channel exists wherever people are present.
No. BitMadWall operates with no internet, no SIM, and no cell tower. Devices link over Bluetooth Low Energy and Wi-Fi Direct, and over LoRa where hardware is paired. A route to the internet is needed only to broadcast a Bitcoin transaction to the blockchain, and any device that has one can do it.
The payment is built and signed entirely on your phone. It then travels the mesh like any other message until it reaches a device with internet, which hands it to the Bitcoin network. Until the network confirms it, the app clearly marks it as pending.
The message waits. A device holds the sealed message and passes it on when a path appears, including the case where someone simply walks it into range hours later. Delivery is best effort, and the app tells you honestly where each message stands.
No. Content is encrypted on the device and private keys never leave it. We operate no server holding messages, contacts, or keys, so there is nothing for us to read, hand over, or be compelled to produce.
Per hop: roughly tens of meters over Bluetooth Low Energy, around 100 meters over Wi-Fi Direct, and 2 to 5 kilometers over LoRa with line of sight. A message travels at most seven hops, so total reach depends on how many devices are relaying rather than on where towers were built.
No. BitMadWall is a closed source, proprietary product. It is free to download and use. The code is not open for contribution or redistribution.
Keys and message history exist on the device and nowhere else. Treat it as you would a hardware wallet: hold recovery material securely and offline, and use panic wipe if the handset is at risk of being taken. There is no cloud copy for us to restore.
Subscription
Program updates.
Release notes, field results, and technical publications. No marketing, no third parties.