Skip to main content
Skip to content
Agentic Finance

Satellite Bitcoin During an Internet Outage: 7 Continuity Checks

Check satellite reception, power, submission and payment evidence before relying on Bitcoin during an internet outage. Includes a local continuity record.

Original editorial illustration for Satellite Bitcoin During an Internet Outage: 7 Continuity Checks
Reading options: audio, text size & sections

Decentralised News · 2027 planning series · Reviewed 21 November 2026

What Matters

Satellite reception can preserve one part of a Bitcoin workflow when a local internet connection fails: receiving network data. That is a valuable capability, but a receiver does not automatically provide a route for submitting a transaction, power for the rest of the equipment or a functioning checkout system. A continuity plan needs to identify the exact service that survives.

Blockstream Satellite supplies a documented example. Its receiver link is one-way. The useful purchasing question is therefore whether that receive path, a separate submission path and the operating environment satisfy the business’s stated outage scenario. This article develops seven checks and a local evidence record. DN has not installed a receiver, measured availability or tested a payment during an outage.

The Signal: receiving a blockchain and sending a payment are separate capabilities

Blockstream’s technical explanation says the satellite link carries Bitcoin network data to a receiving node and cannot transmit from that node. Its transport adds redundancy for reception losses. This supports a concrete distinction: a node can receive useful information while its operator still lacks a working outbound connection.

The distinction matters for an AI agent as much as for a human cashier. An agent may inspect a recently received block and prepare a payment instruction. Neither event demonstrates that another node received the transaction or that the intended payment was confirmed. The interface should report the state that was actually observed.

DN Alpha Thesis

Evaluate satellite Bitcoin as a component in a continuity design. Draw a separate evidence line from the broadcast to the local node, from the wallet to a submission channel and from the observed chain state to the business decision. A successful demonstration of one line should not silently become a claim about the other two.

1. Define the outage and the decision that must continue

“Internet outage” describes many different situations. A premises router can fail while a mobile connection remains available. A wider network failure can affect both. Electricity can fail at the same time, or the building can lose access to the particular service that hosts its wallet interface. A system designed for the first scenario may offer little help with the last.

Write a bounded operating requirement before selecting hardware. A fictional retailer might need to observe incoming Bitcoin payments for six hours while its normal fixed connection is unavailable. A treasury operator might instead need to submit an urgent outbound transaction. A researcher might only need a synchronized node for later analysis. These are three different acceptance tests, even when the same receiver appears in all three diagrams.

Specify what would count as continued service and what would force a pause. For the retailer, that could be a documented transaction appearing in the node’s accepted chain under the retailer’s existing confirmation policy. For the treasury, it might also require authorized signing, an outbound route and acknowledgment from that route. The test should name the observation rather than use an undifferentiated “online” status.

Keep the time horizon explicit. Eight hours of planned operation is an assumption about a scenario, not a forecast of how long an outage will last. The worksheet preserves that distinction. It can compare entered durations, but it cannot predict restoration or guarantee that the equipment will operate for the stated period.

2. Match coverage, receiving equipment and the actual site

A coverage map is a starting point for a location review. It is not a record of reception at the proposed installation. Blockstream publishes a country table and regional coverage map, including partial and absent coverage. Its guidance also distinguishes frequency bands and notes that the store’s flat-panel antennas do not support C-band.

The immediate procurement task is to connect the particular site with the relevant beam, band and compatible antenna arrangement. Preserve the date and version of the material used. A procurement assistant should not interpret a country name appearing in a table as permission to order an arbitrary kit. Where the source marks coverage as partial, the site-specific question remains open.

Blockstream’s kit comparison distinguishes receiver configurations and whether an antenna is included. The buyer should separately record the host computer, networking, power and installation work required for the intended configuration. An inexpensive receiver price is not a complete cost for a working service.

Ask the installer or responsible operator to define a reception check with retained observations. The record should identify equipment, configuration, location alias and test conditions without exposing a sensitive physical address publicly. A vendor specification and an observation at the site remain different evidence types. This article supplies neither a site survey nor a universal reception threshold.

3. Keep the receiving client and validation boundary visible

The data path includes software as well as an antenna. Blockstream documents Bitcoin Satellite as a version of Bitcoin Core adapted to receive and decode the satellite transport. That is a client and transport description. It does not mean that an application can ignore its deployed software version, configuration, storage or operating procedures.

Record the actual receiving client, release and configuration used by the node. Identify the local service that the wallet or payment application reads. If one machine receives the broadcast while another runs the business interface, the local connection between them belongs in the continuity plan. A satellite receiver cannot repair a failed local switch or a stopped application process.

Separate receipt of packets, synchronization of the node and the application’s interpretation of a payment. A status panel may show reception without showing that the node has caught up. The application may display cached information. The review needs an observation that answers the business question, with a timestamp and enough context for another operator to understand it.

DN’s oracle-data review discusses the broader principle that a data delivery mechanism must match the consumer’s interpretation. For this workflow, retain the current node evidence directly rather than relying on an unrelated provider’s claim about latency. A local agent should be able to distinguish unknown, behind, receiving and observed current states without manufacturing a certainty percentage.

4. Identify a separate route for transaction submission

The one-way receiver is the decisive architectural boundary. A plan for outbound payments must name another way to deliver the signed transaction to the network. Record that route’s dependencies and whether it remains available in the outage being studied. Merely having an alternative provider on a procurement list does not demonstrate an independent route.

Suppose a shop receives satellite data and also has a mobile connection. The mobile path may supply outbound connectivity in a fixed-line outage. That is a conditional design statement. If both paths depend on the same unavailable power source or local equipment, the apparent diversity may not produce the intended continuity. Draw the actual dependencies and retain the result of any authorized rehearsal.

Do not confuse this question with Blockstream’s Satellite API. That service lets users arrange broadcasts of data through an API and pay through Lightning. It does not establish that the receiver itself transmits upward, that a message is a valid Bitcoin transaction or that miners will include a submitted transaction. Message delivery and payment settlement have different success conditions.

The application should preserve intermediate states. Prepared, signed, submitted, acknowledged and observed in a block are useful descriptions when supported by the underlying system. A queue waiting for connectivity should remain a queue. If the business cannot establish the outbound route, the honest operational result is that submission remains unresolved, even when the node can receive blocks.

5. Include the whole power and local-service boundary

Power planning should cover the equipment needed for the actual task. That may include the receiver, host computer, local network equipment, storage, wallet interface and the separate submission channel. Listing the receiver alone can leave the operating workflow dependent on another unpowered component.

For a first planning comparison, record the intended outage duration and the supported operating duration of the complete chosen configuration. The worksheet computes the difference only from those entered values. It does not derive battery performance from a marketing capacity, estimate electrical losses or supply a device-specific consumption model. A measured runtime needs its own configuration and test reference.

Consider a synthetic eight-hour outage with six hours of assumed power for the full setup. The declared shortfall is two hours. That arithmetic does not mean the system is reliable for the first six hours; it only exposes one mismatch in the plan. Unknown reception or an unavailable local application can still prevent service much earlier.

Operating roles belong in the boundary too. Identify who notices a failed service, who is permitted to change the setup and who can suspend payment acceptance when evidence becomes unclear. Preserve an accessible copy of the recovery instructions. An emergency workflow that can only be read from the unavailable cloud service has an unresolved dependency.

6. Preserve signing authority and a payment-state record

Connectivity does not expand the agent’s mandate. The person or organization controlling the wallet must still define what the agent may prepare, sign or submit. A continuity procedure should identify those permissions separately from the receiver’s ability to obtain public network data.

DN’s wallet authority and quantum-migration research provides related questions about signers, recovery and alternative authority paths. Apply the same separation here: the receiver does not need to become a treasury signer simply because the normal connection is unavailable. A fallback process should not silently remove the limits that govern routine payments.

Build a small payment-state record that can be reconciled after connectivity returns. Use an internal alias for the instruction, its authorization reference, submission status, observed result and unresolved exception. Avoid publishing private wallet records in a general-purpose worksheet. The point is to retain the path from a permitted instruction to the result the business actually relied on.

For incoming payments, document the business’s acceptance policy separately from the observed chain state. For outgoing payments, preserve an unresolved or failed submission as such. An agent’s confident summary is not a replacement for the relevant system evidence. If a later observation contradicts the earlier state, record the change and its source rather than rewriting the history as though settlement had always been clear.

7. Check the operating jurisdiction and the fallback decision

A satellite path does not create a jurisdiction-free blockchain. The Outer Space Treaty assigns States Parties responsibility for national space activities in Article VI and preserves jurisdiction and control over registered space objects in Article VIII. These provisions directly contradict the broad claim that placing infrastructure in orbit removes all sovereign legal connection.

Those treaty provisions do not determine every local receiver, telecommunications, financial-service or business obligation. The review must identify the actual operator, equipment, location and activity. This article does not assess an installation’s legal permissions or compare national licensing regimes. Its narrow conclusion is that “in space” cannot serve as a universal legal exemption.

The fallback decision should then follow the documented operating state. A receive-only setup may still be useful for monitoring while outbound payment service is paused. A functioning submission route may permit an authorized workflow to continue under the organization’s existing rules. Missing power or unclear node state may require a different response. The same equipment can support different decisions in different circumstances.

Write the fallback in terms the operator can execute: what observation triggers the change, who owns the decision, which tasks continue and what record is retained. Avoid assigning a broad “resilient” badge to a plan with unresolved dependencies. The useful deliverable is a specific contingency and evidence request for each missing part.

Worked case: the receiver works, but the business remains partly offline

The following case is invented. A small business plans for an eight-hour fixed-line outage. It has references for site reception, a compatible receiving configuration and a local client observation. It enters six hours of assumed power for the complete setup. Its independent transaction-submission route has not been demonstrated in the same outage scenario.

ComponentDeclared evidenceWhat remains unresolved
Receiving pathIllustrative site and client referencesReferences are not authenticated by the worksheet
Power durationSix hours against an eight-hour scenarioTwo-hour declared duration gap
Outbound submissionNo independent route observationAbility to send during the outage
Payment outcomeNo particular payment assessedAny actual confirmation or business acceptance

The scenario supports a narrow conclusion: the plan describes a receive path but does not yet document the required outbound service or full-duration power. Buying an additional antenna would not necessarily address either gap. The next work is to resolve the missing route, validate the complete power boundary and specify the fallback operating decision.

DN Satellite Continuity Record

Use the worksheet to describe one outage scenario and keep the receiving, sending and operating evidence separate. The default entries are synthetic. A reference means that the reader has identified a record; the tool does not fetch or authenticate it. Blank durations remain unknown, and a duration comparison never becomes a probability of availability.

DN Satellite Continuity Record

Change the illustrative assumptions below. This worksheet runs locally in your browser. It records your declarations; it does not verify evidence, connect to accounts, submit instructions or grant approval.

Synthetic continuity record — unresolved items remain

Receiving references entered4 of 4 (not a score)
Declared duration gap2.00 hours
Separate submission routeUnresolved
Payment-state referenceNot entered
  • Four receiving-path references are entered. None is fetched, authenticated or tested.
  • The declared full-setup power duration is shorter than the planned outage.
  • The separate submission route is unresolved; reception alone does not establish outbound service.
  • Payment authority has no reference in this record.
  • No actual payment outcome is documented in this record.
  • Identify the fallback owner and operating decision.
  • This worksheet does not verify installation, legal permissions, signing authority, transmission or settlement.

The initial numbers are synthetic. Unknown evidence remains unresolved. Downloads contain the values you enter; use aliases and avoid private or identifying information.

Methodology, limitations and corrections

DN reviewed the linked Blockstream materials and treaty sources on 21 November 2026, then designed the dependency record and synthetic case. No hardware installation, network outage, site reception test, payment transmission or legal review was performed. The scope is continuity planning for documented satellite reception, not an inventory of orbital blockchains or a recommendation to buy equipment.

The duration calculation is gap = max(0, planned outage hours minus declared supported power hours). Both values concern the complete scenario specified by the reader. A zero gap only means the entered power duration is at least as long as the entered outage. Missing evidence in any other part remains unresolved. The tool makes no network requests, grants no transaction permission and predicts no restoration time.

Reopen the record after a material change in site, receiving hardware, client version, network dependencies, power arrangement or authorized payment workflow. Preserve the prior version and the reason for the change. Source dates and record-creation dates describe different things; creating a new worksheet does not refresh the underlying evidence.

Sources and evidence register

Primary sources reviewed on 21 November 2026. The article distinguishes documented facts, DN analysis and synthetic examples. Recheck changeable rules and configurations before acting.

  1. Blockstream: satellite data and one-way transport — Receive-only satellite links, transport redundancy and separate transmission requirement.
  2. Blockstream: satellite coverage — Coverage distinctions and antenna-band compatibility; not a site survey.
  3. Blockstream: kit comparison — Receiver configurations and antenna inclusion.
  4. Blockstream: Bitcoin Satellite client — Client receives and decodes the satellite transport.
  5. Blockstream Satellite API — Broadcast-data service distinct from a terminal uplink or Bitcoin transaction inclusion.
  6. UN Treaty Series: Outer Space Treaty, registered text — UNTS volume 610, registration 8843. Articles VI and VIII establish States Parties’ responsibility, supervision and jurisdiction/control boundaries.
  7. UNOOSA: Outer Space Treaty official records — Treaty background and official records.

Frequently asked questions

Does Blockstream Satellite let a receiver send Bitcoin transactions?

The documented satellite receiver link is one-way. An outbound payment needs a separate submission route. Receiving data does not establish that a transaction was submitted or confirmed.

Can a receiving node remain useful when its normal internet link fails?

It may continue receiving through the documented satellite path if the actual site, equipment, client, power and local services remain functional. This article does not establish availability for any particular installation.

Does satellite coverage mean any antenna or kit will work?

No. Check the site, beam, frequency band and compatible equipment. The provider distinguishes partial coverage and notes that its flat-panel antennas do not support C-band.

Does an eight-hour battery claim prove eight hours of payment service?

No. The runtime must concern the complete operating setup, and reception, software, local networking, signing authority and submission remain separate dependencies.

Is a satellite blockchain outside sovereign jurisdiction?

That broad claim is unsupported. The Outer Space Treaty retains state responsibility and jurisdiction/control relationships for space activities and registered objects. Specific local equipment and financial obligations require their own review.

Does the worksheet test the receiver or approve payments?

No. It records user declarations and compares entered durations. It performs no external verification, device operation, wallet connection or transaction approval.

DN research note: This article is original editorial analysis supported by the linked sources. Calculations and example cases are illustrative unless explicitly described otherwise. The worksheet is a planning aid; it does not carry out the actions it describes.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.