Ask our Bitcoin node for the chain tip, fees, a transaction or an address, and broadcast a signed transaction, by LoRa mesh radio. No internet, no phone network.
Also 2631493b6a4ff119df63b94282865c4fa0b064be47e57a9cfd29ed6629bdfb96
What it is
MeshCore is open-source firmware for small, cheap LoRa radios. Radios pass short text messages to each other directly, and fixed repeaters on hills and rooftops carry them further, hop by hop. Nothing in the path is an internet provider or a phone network, and the 915-928 MHz band it uses in Australia is open to low-power radios like these without an individual licence.
We have plugged one of those radios into a server at mineracks in Brisbane. It is a contact called mineracks on the South East Queensland mesh. Send it a direct message such as btc height and a small program asks our own Bitcoin node and messages the answer back. Direct messages are encrypted end to end between your radio and ours.
It is slow and tiny by design: a reply is at most 130 characters per message, and a round trip takes from a few seconds to a minute depending on how many repeaters sit between us. It is here for the day the internet is not, and as a demonstration that Bitcoin does not need it.
What people use it for
Checking the chain tip, the mempool and current fee rates when your internet is down.
Seeing whether a payment has confirmed, by transaction id or by address.
Broadcasting a transaction you signed offline, in a few radio messages, with no ISP in the path.
Learning how little bandwidth Bitcoin actually needs.
Get on the air
1. A radio
Any device that runs MeshCore companion firmware: Heltec V3, RAK WisBlock 4631, Seeed T1000-E, LilyGo T-Deck or T-Echo, Elecrow ThinkNode M1 (what we use), and many more. Roughly AUD 40 to 150. Buy the 915 MHz (AU915/US915) version, not the 868 MHz European one.
2. Firmware
Flash companion firmware in your browser at flasher.meshcore.co.uk. Choose the Bluetooth build to use it from a phone, or the USB build to use it from a computer.
3. An app
MeshCore for iOS and Android, the web app at app.meshcore.nz, or the open-source desktop Mesh-client (USB). All free.
4. Radio settings
The mesh around Brisbane runs on 923.125 MHz, bandwidth 62.5 kHz, spreading factor 8, coding rate 5. Your radio must match or it hears nothing. Other regions use other settings; check with your local mesh.
5. Add us
Scan the QR code on this page in the MeshCore app, or add a contact by public key. Then send a flood advert from your radio (Advert, Flood in the app): ours can only answer radios whose advert it has heard.
6. Say hello
Send ping as a direct message. If pong comes back, there is a radio path between us. Then send help.
Commands
ping
pong. The path test.
help
The command list.
btc height
Current block height.
btc info
Chain, height, sync progress, age of the tip and the start of the best block hash.
btc mempool
Transactions waiting, their total size, and the minimum fee rate to get in.
btc fee
Fee rates in sat/vB for the next block, 30 minutes, an hour, and the economy and minimum rates.
btc block [height]
Hash, time, transaction count and size of a block. The tip if you give no height.
tx <txid>
Confirmed or not, the fee and fee rate, and the size of a transaction.
addr <address>
Balance and transaction counts for an address, confirmed and in the mempool.
diff
Next difficulty retarget: the height, blocks remaining and the estimated change.
txb <i>/<n> <piece>
Broadcast a signed transaction, sent as n pieces of hex or base64 in any order. The reply to the last piece is the txid or the node's rejection. txb status and txb cancel manage an upload in progress.
Sending a transaction by radio
Sign the transaction in your own wallet, offline, and export the raw hex. Split it with our small script (bitcoin.mineracks.com/downloads/meshcore-txchunks.py, 20 lines of Python you can read): it prints the txb lines to send, about 97 bytes of transaction per message, at most 12 messages. A typical one-input, two-output payment is 3 messages. We hold no keys and cannot change a signed transaction; we can only pass it to the network or fail to.
How far it reaches
Measured
About 6 km across Brisbane suburbs, through 2 to 4 community repeaters, handheld radio indoors at the far end. Replies arrive, with occasional retries.
In theory
A message can cross up to 64 repeaters. Each hop spans a few kilometres between street-level handhelds and tens of kilometres between repeaters with line of sight from hills or towers. If the mesh map shows a chain of repeaters between you and Brisbane, you can probably reach us; in practice every extra hop adds delay and loss.
Not by internet
MeshCore repeaters relay by radio only. The standard firmware has no internet bridge, and we do not run one, so there is no relayed path from another city's mesh to ours. If no radio path exists, the same data is on our explorer and Electrum servers over the internet.
Extending it
The mesh is built by the people on it. A solar repeater on a roof or a hill between you and us is the way to bring this service to your area.
How we run it
A ThinkNode M1 running MeshCore companion firmware 1.18, on USB to a small container beside our Bitcoin node. The radio sits at a window, not on a mast; a higher antenna is planned.
The bridge reads Bitcoin Core's REST interface and our mempool API. It holds no wallet, no keys and no RPC credentials. Every answer comes from our own node on the same local network, so it keeps working when our internet uplink is down.
Limits, because radio airtime is shared with everyone on the mesh: 6 commands a minute and 40 an hour per sender, 20 a minute overall. The same command repeated within a minute is answered once. Replies are at most 4 messages.
Experimental. One radio, one path, best effort. If it does not answer, the mesh between us is busy or broken, or we are.
Trust, stated plainly
Direct messages are encrypted between your radio and ours, so repeaters and listeners cannot read your question or the answer. They can see that your radio is talking to ours.
We see every command you send, tied to your radio's public key. A transaction id or address you look up is revealed to us, exactly as it is when you use our explorer. We log commands for operations and abuse handling.
You are trusting our node's answer. For a balance or a confirmation that matters, verify with your own node when you can.
A transaction you broadcast is public the moment we relay it. That is what broadcasting means.
Notes
The radio advertises itself on the mesh a few times a day, which is how your app learns its name and route.
Keep it short and occasional. Every message uses airtime that other people's messages also need.