Skip to content
Product

Talk and transact when the network stops.

BitMadWall is a mobile application. Encrypted mesh messaging and an offline Bitcoin wallet run on the same device and share the same transport. Neither requires internet, a SIM, a subscriber record, or a central server.

Mesh messaging

Messaging with no carrier in the path.

One-to-one and group conversations carried by the devices around you. Your identity is a secure key, not a phone number, and every message is sealed end to end and signed by its sender.

01

No phone number. No account.

Identity is a key pair generated on the device. No registration, no directory, no subscriber record for anyone to request.

02

Sealed and signed

Built on the same published standards Signal uses: keys agreed directly between the two devices, content sealed before it moves, and a signature any carrier can check without reading a word. The named standards are listed on the Security page.

03

Ephemeral by default

Messages live on the handset, not in a cloud. Disappearing timers and secure erase are per conversation; panic wipe is immediate.

Not a data-collecting messenger
No phone number, no email, no contact upload, no central store of conversations. There is no dataset to disclose because none is created.
The messaging screen

What the conversation actually looks like.

The desktop client: a contact list of six mesh identities on the left, each showing its last message and online state, beside an open conversation whose sent messages carry the accent and whose delivery ticks sit under each timestamp.
🔍 Click to expand
The same contact list on a phone, filtered to direct messages, with unread counts and per-contact reachability dots.
🔍 Click to expand
A conversation on a phone: four messages exchanged over the mesh, the last one confirming a transfer sits in the outbox until either party comes online.
🔍 Click to expand

The messaging surface, on the desk and in the hand.

Offline Bitcoin wallet

Sign now. Broadcast when a route exists.

Sign with no connectivity at all; the transaction rides the mesh until any device with a route out hands it to the chain.

Held on this phone, not by a bank0.084 213BTC
  • +0.021 000Received · confirmed
  • −0.004 500Sent · waiting for a route

    Completes when any phone in the mesh reaches the internet. Until then the app counts it as not yet paid.

  • +0.067 713Received · long settled
Recovery phrase: 12 words, shown once. Kept on paper, never online.
01

Signed on the device

Keys are created and kept in the phone's built-in secure hardware where the platform provides it. The payment is complete and signed before it ever enters the mesh.

02

The mesh carries it

Carried like any message, held through the gaps, until a device with internet hands it to the Bitcoin network. If two devices both hand it over, no harm is done: the network accepts it once.

03

Bitcoin first, built for more

The transport treats transaction data as an opaque payload. Further chains are a wallet-side addition, not a protocol change.

Not a bank
We hold no funds and operate no accounts. Keys exist on the handset and nowhere else.
Not custodial
There is no recovery service. If the seed is lost, we cannot restore it. That is a property of the design, not a gap in it.
The wallet screen

A balance, a pending send, and no bank behind it.

The wallet on desktop: a balance in satoshis above a receive address, send and receive controls, and a transaction history of four entries — one of them pending, the rest carrying confirmation counts. A panel at the right summarises confirmed, pending and outbox totals.
🔍 Click to expand
The same wallet on a phone, the balance and quick-send recipients stacked above the transaction history.
🔍 Click to expand

The wallet, holding a balance and an unconfirmed send.

Where it serves

Built for the days the map goes dark.

The scenarios below are the design brief, not marketing. In each, coverage is the people present, and every additional handset is an alternate path.

T-01

Grid blackout

BLE mesh

A city loses power and towers with it; neighbourhoods keep coordinating handset to handset.

T-02

Disaster zone

Mesh + gateway

Infrastructure is down for weeks; response teams message and settle payments locally.

T-03

Contested city

Dense mesh

The network is shut off on purpose; crowds stay reachable without a carrier to lean on.

T-04

Off-grid range

+ LoRa

Valleys and coastlines the towers never reached; one paired LoRa radio joins whole settlements.

T-05

Between villages

Data mule

A traveller carries the mesh on foot. Messages are delivered hours later, by a person.

Trajectory

Shipping plainly, aiming far.

The MVP launches labelled Early Access, and the label is honest: range is limited and delays are expected. What follows it is already designed for.

Next step

Request a technical briefing.

We will walk through the architecture, the threat model, and the limits.

Get in Touch

Or write directly to info@tashitech.ai.