Mars · Mission health heartbeat

Know why it fails, before it fails.

Every 5–10 minutes a rover or lander captures the health of its main hardware and software subsystems, seals it into a signed receipt and sends it through a Mars orbiter to Earth. A part that is degrading shows up on Earth while there is still time to act.

StatusIn development
CadenceEvery 5–10 min
PathRover → orbiter → Earth
SignatureEd25519 + ML-DSA-65
01 Why this exists

Missions go silent, and too often nobody ever learns why.

A spacecraft that stops talking takes its last hours with it. Engineers are left with the final telemetry that happened to be downlinked, a model of what might have gone wrong, and a list of hypotheses that can never be closed.

One recent example, stated plainly: a Mars rover that landed in 2021 went silent about a year later. Orbiter imagery later found it on the surface, but the public still does not have a full account of why it stopped. That is not a failing of any one team. It is what happens when health data is not recorded in a form that survives the loss of the vehicle.

The founder's design goal for COSRYX is simple: the record of a mission's health should outlive the mission. If the rover dies, the last sealed receipts on the orbiter and on Earth should say which subsystem was failing, for how long, and what was done about it.

And the better outcome is the one where the receipts are read in time: the trend is spotted, Earth acts, and the rover keeps working.

02 What the heartbeat captures

Seven subsystems, one signed snapshot.

Each heartbeat is a compact summary, not raw telemetry: the values engineers need to see a trend, plus digests that bind the summary to the full on-board record.

POWER

Generation and storage

Source output, battery state of charge and temperature, bus voltage, heater draw.

THERMAL

Temperatures in band

Electronics box, actuators, instruments; heater duty cycles against their limits.

MOBILITY

Wheels and drive

Motor currents per wheel, slip estimates, suspension angles, fault counters.

COMMS

Links and margins

Relay link margin, pass success, buffer fill, the backlog waiting to go up.

COMPUTE

Processor and memory

CPU load, memory error-correction events, resets, watchdog trips.

INSTRUMENTS

Payload health

Power states, calibration flags and error codes for each science instrument.

SOFTWARE

Modules and versions

Which modules run, their image hashes, and whether each matches the signed manifest.

03 One degradation, end to end

From a rising current to a signed fix.

Health heartbeat · simulated01 / 05
01 · CAPTURE

Every 5–10 minutes, the rover takes its own pulse.

Power, thermal, mobility, comms, compute, instruments and software are sampled together, so one snapshot shows how the whole vehicle is doing at one moment.

02 · SEAL AND RELAY

The snapshot becomes a signed, chained receipt.

Each health receipt carries the hash of the one before it and a hybrid signature, Ed25519 plus ML-DSA-65. The next orbiter pass carries it up, and Earth checks it offline.

  • A missing or edited receipt breaks the chain visibly.
  • The orbiter relays; it does not need to be trusted.
03 · TREND

Mobility drifts amber, weeks before a fault.

In the simulated example, the current on one drive motor climbs 18% over nine sols. Nothing has failed. Projected forward, it reaches its limit in about two weeks.

04 · DECIDE

Earth chooses a response, and that choice is receipted too.

The options are the founder's four: reassign the task, shed load, disable the failing function, or push a signed software update. Two operators approve; the decision becomes a receipt in the same chain.

05 · RECOVER

A signed update goes up; the trend comes back in band.

The rover verifies the update's signature before applying it, then receipts the result. The next heartbeats show the motor current back under its new cap, and the traverse resumes at reduced load.

04 Anatomy of a health receipt

Small, signed, and bound to everything before it.

A health receipt follows the DCS R-Series receipt format that every COSRYX product uses. It names the vehicle, the time window and the subsystem summaries, and binds them with digests to the full record kept on board.

Two things make it evidence rather than a log line. The chain: each receipt includes the hash of the previous one, so a gap or an edit is visible to anyone checking later. The signature: a hybrid of Ed25519 and ML-DSA-65, so it remains checkable as classical signatures age.

Field names below are illustrative; the schema is still being finalised.

health_receipt {
  vehicle      : "rover-1"
  seq          : 412
  window       : sol 287 · 14:05–14:10 LMST
  prev         : sha256 7c1e…a9
  subsystems   : {
    power      : in band
    thermal    : in band
    mobility   : motor_lf current +18% / 9 sols
    comms      : relay margin nominal
    compute    : ecc events 0 · resets 0
    instruments: idle
    software   : 14 modules · manifest match
  }
  record_root  : sha256 3f90…12
  signature    : Ed25519 + ML-DSA-65
}
05 The numbers that matter

Frequent enough to see a trend. Small enough to fly.

5–10 minHeartbeat cadence, set per mission
7Subsystem groups in every snapshot
3–22 minOne-way light-time, Mars to Earth
≈150–300Heartbeats per sol, at that cadence

A sol is about 24 hours 40 minutes, so a 10-minute cadence gives about 148 heartbeats a sol and a 5-minute cadence about 296. An ML-DSA-65 signature is 3,309 bytes and Ed25519 adds 64, so per-receipt signing costs a few kilobytes each. Whether to sign every receipt or sign a batch per relay pass is an open design question, not a settled answer.

06 What Earth can do

Four responses, each one on the record.

01 · REASSIGN THE TASK

Move the work to another unit.

If one instrument or vehicle in a team is degrading, its task can be handed to another. The reassignment is receipted, so the science record shows which unit did what.

02 · SHED LOAD

Ask less of the struggling part.

Shorter drives, fewer heaters, lower duty cycles. The rover keeps working while the trend is watched in the next heartbeats.

03 · DISABLE THE FUNCTION

Turn off what is failing, deliberately.

A function that threatens the vehicle can be switched off before it fails on its own terms, with the decision and its reason sealed into the chain.

04 · SIGNED SOFTWARE UPDATE

Change the behaviour, verifiably.

A new limit, a new mode, a patched module. The rover checks the update's signature before applying it, and receipts what it applied, so Earth can prove which code was running afterwards.

Commands still reach Mars 3–22 minutes after they are sent. That is why these responses work on trends, not seconds: the heartbeat gives Earth days or weeks of warning, and the rover keeps operating within signed bounds while Earth decides. See Mars without round trips.

07 If the rover goes silent anyway

The last receipts become the account.

Some failures cannot be prevented. When one happens, the health receipts already relayed sit on the orbiter and on Earth, signed and chained. Investigators can see which subsystem was trending, when, and every action taken in response, and they can check that none of it was altered after the fact.

If the rover loses contact without failing, it keeps sealing heartbeats on board and forwards the backlog when a relay is in view again. That is the store, seal and forward path.

08 Where it sits in COSRYX

Built on parts that already exist.

PartRole in the heartbeatStatus
Mission Recorder V2The on-board, chained record each receipt is bound toBuilt · G0 + G1 complete
COSRYX-EDGEOn-board assurance: model integrity, signed update channelBuilt · Simulation-validated
DSRPStore-and-forward relay across interrupted linksSimulation-validated
COSRYX-MCCMission control: trend view, decision support, countersigned actionsBuilt · Simulation-validated
PQ-AgilityThe hybrid signature constructionTested
Health heartbeatThe cadence, the subsystem schema and the trend logicIn development
09 Honest status

In development. Not yet in the test totals.

The founder reports that the heartbeat code was written around 27 August 2026. It is not part of the published totals (692 product tests, 410 integrated tests), and no result for it is claimed on this site.

Everything shown in the scenes on this page is illustrative and simulated: the values, the trend and the update are examples of how the feature is meant to work.

StepState
Concept and receipt designIn development
Code for capture and sealingIn development
Test suite and simulationPlanning
Radiation testing (G3)Planning · next on the roadmap
On our own CubeSatPlanning · no launch contract signed

Status as of 21 October 2026. Internal security freeze (RC3) complete · External audit not completed · No flight qualification claimed.

10 Questions

On the heartbeat.

Does this replace the mission's own telemetry?

No. The mission's telemetry system stays as it is. The heartbeat adds a signed, chained summary that a third party can check later. We do not replace mission security; we add mission evidence.

Why every 5–10 minutes rather than continuously?

Relay passes are short and bandwidth is shared. A fixed cadence gives a steady trend line at a cost a mission can plan for. The interval is meant to be set per mission.

What if the orbiter is not overhead?

Heartbeats are sealed on board and queued. When a relay is in view, the backlog goes up in order, and the chain shows that nothing was lost in between.

Can an update be pushed without anyone knowing?

Not without leaving a mark. The update is signed, the decision to send it is receipted on Earth, and the rover receipts what it applied. All three sit in chains that anyone can check.

Has this flown?

No. It is in development, and no flight qualification is claimed.

11 Next

And when contact is lost for months?

The rover keeps sealing receipts on board and forwards the whole backlog when a relay is back in view. Nothing is lost, and nothing can be quietly changed.