Satellite internet has expanded dramatically in recent years. Services like Starlink now make it possible to access Bitcoin from a remote farm, a live-aboard vessel, or a bush campsite that no fibre or 4G network could ever reach. That's genuinely useful. It's also a security environment most Bitcoin guidance ignores entirely, because most guides assume you're sitting on a city broadband connection.
Satellite connections introduce specific risks. Latency is high, routing paths are unusual, and the physical hardware sits outdoors where it can be tampered with or pointed at by others. None of these issues are insurmountable, but they require deliberate preparation before you open a wallet or broadcast a transaction.
Why satellite internet is different from other connections
A standard broadband connection routes your traffic through a relatively short chain: your router, your ISP's exchange, and then out to the internet. Satellite internet adds two more hops that most users never think about: your dish to a low-earth-orbit (LEO) satellite, and that satellite down to a ground station. Those extra hops have consequences.
First, round-trip latency on a LEO service like Starlink averages 20 to 40 milliseconds under good conditions, but it spikes sharply during rain fade, dish obstruction, or handover between satellites. That latency spike won't corrupt a Bitcoin transaction, but it can cause your wallet app to time out before it receives confirmation that a broadcast was accepted. Beginners sometimes interpret a timeout as a failed transaction and try to send again, which can result in a double-spend attempt or unnecessary fees.
Second, ground stations are geographically distributed, and your traffic may exit the internet from a country other than the one your dish is located in. This matters for Bitcoin in two ways: your apparent IP address may look foreign to an exchange's fraud detection system, triggering account holds or identity re-verification, and any VPN you're running may behave unexpectedly when the underlying IP country keeps changing.
Third, the dish hardware itself is a physical device with a wireless management interface. On some installations, particularly where a dish has been shared, rented, or set up by a third party, that management interface may be on the same local network as your devices. A compromised router or a malicious device on the same LAN can intercept unencrypted traffic just as easily over satellite as over any other medium.
Steps to take before you transact over satellite
The preparation here is straightforward, but each step matters.
- Verify your wallet software before you connect. Download or update your Bitcoin wallet app before you get to a satellite-only location. Satellite connections are more vulnerable to DNS spoofing, which can redirect update requests to a lookalike server. If you need to update in the field, use a trusted VPN before you fetch anything.
- Use a reputable VPN with a kill switch. A VPN encrypts traffic between your device and the VPN server before it ever reaches the satellite. Make sure the kill switch is enabled so that if the VPN drops during a satellite handover, your wallet traffic doesn't briefly go unencrypted. McLeod Pacific Investments covers how to use a VPN safely with Bitcoin in more detail if you need a starting point.
- Segment the satellite router's LAN. If you're on a shared satellite connection (a marina, a remote work hub, a friend's property), put your Bitcoin device on its own network segment or hotspot. Don't rely on the shared LAN to be clean.
- Avoid large transactions during weather events. Rain fade causes latency spikes and packet loss. Broadcast important transactions when signal quality is stable, and always verify on a block explorer that the transaction ID appears in the mempool before you close the app.
Latency, timeouts, and the mempool
This is the operational risk most satellite users underestimate. When you broadcast a Bitcoin transaction, your wallet sends the signed transaction data to one or more peer nodes and waits for acknowledgement. On a high-latency connection, that acknowledgement can take long enough for the app to show a "failed" status even though the broadcast succeeded.
Before you ever retry a transaction, check a public block explorer using the transaction ID your wallet generated. If the transaction appears in the mempool, it's already been broadcast and is waiting to confirm. Sending again would create a second, conflicting transaction with the same inputs, and depending on your wallet's replace-by-fee settings, one of them will be dropped. Understanding what's in the mempool is worth knowing before you ever need it under pressure: the article on what a Bitcoin mempool actually is explains how that waiting room works and why fees spike when it fills up.
The rule is simple. Timeout does not mean failure. Check the explorer first, always.
Physical security of the satellite equipment
Satellite dishes are outdoor hardware, and on remote properties they're often installed in locations that aren't constantly supervised. A few physical considerations matter here.
The dish's power-over-ethernet (PoE) injector and router typically sit indoors, but the cable run between the injector and the dish is exposed. Anyone with physical access to that cable run can introduce a man-in-the-middle device. If you're transacting Bitcoin on a property where others have unsupervised access to the dish cabling, treat that network as hostile and use end-to-end encryption for everything.
The router's admin interface should always use a non-default password. Starlink's own router has a relatively locked-down interface, but third-party routers used in bypass mode can have admin credentials that were never changed from factory defaults. Check this before you use the connection for anything sensitive.
What satellite internet doesn't change
The fundamentals of Bitcoin security don't shift because your packets are travelling via low earth orbit instead of fibre. Your seed phrase still needs to stay offline. Your hardware wallet still needs to be set up correctly before you travel. Your signing process still happens on the device, not on the network.
Satellite internet is a transport layer. It affects how reliably and privately your signed transactions reach the network. It doesn't affect what's inside those transactions, and it doesn't change the threat model for your private keys. If your seed phrase is written down and locked away, a compromised satellite router can't touch your funds directly. It can only intercept information you're actively transmitting: login credentials, exchange sessions, unencrypted wallet data. Keep that data off the wire whenever possible.
For users operating Bitcoin from genuinely remote locations, the combination of a hardware wallet, an encrypted VPN with a kill switch, and a block explorer check before any retry is enough to transact safely over any satellite connection currently available in Australia. The connection is unusual. The discipline required isn't.