Earth orbit · Space situational awareness

Prove the warning. Prove the move.

Low Earth orbit is crowded with satellites and debris. When two objects may collide, COSRYX binds the observations, the alert, the decision and the result into one receipted chain, so an operator, an insurer or a court can check later what was known and what was done.

SPACETRACE29/29 product tests
SSA ACCOUNTABILITY34 product tests
COSRYX-WATCH33 product tests
SWARM TRUST38 product tests
01 The problem

After a near miss, everyone asks who knew what, and when.

Conjunction screening runs every day across thousands of tracked objects. Most alerts end quietly. A few lead to a manoeuvre, and a very few to a dispute: a damaged satellite, a debris cloud, a claim between operators.

At that point the record matters more than the physics. Which observations was the alert built from? Was the warning sent, and received? Who decided to manoeuvre or to hold, under which policy, and with what data in hand?

Today those answers are spread across emails, logs and spreadsheets that each party controls. COSRYX makes them one chain of signed receipts, from the sensor to the spacecraft action, that any party can verify offline without trusting the others.

We do not replace space traffic coordination; we add the evidence trail beneath it.

02 One conjunction, receipted

Sensor → alert → action → accountability.

Conjunction chain · simulated01 / 04
01 · OBSERVATION · SPACETRACE

Every track is sealed as it arrives.

Radar and optical observations are hashed and signed at ingest. From that moment, anyone can tell whether an observation used later is the one that came in.

02 · ALERT · COSRYX-WATCH

The alert names its sources.

A conjunction alert carries the root hash of the exact observations it was computed from, plus the miss distance, time of closest approach and probability. A later reviewer can recompute it from the same inputs.

03 · DECISION · THE OPERATOR

Manoeuvre or hold, signed.

The operator's decision is a receipt chained to the alert: what was decided, by whom, under which policy. A decision to hold is recorded just as carefully as a decision to burn.

04 · ACCOUNTABILITY · SSA ACCOUNTABILITY

Replayable, years later.

Post-event tracking closes the chain with the actual outcome. Any third party can replay observation → alert → decision → result offline and see exactly what was known at each step.

03 Four products, one chain

Each link has an owner.

N13 · SPACETRACE

Observation provenance

Binds sensor observations to the alerts derived from them, and alerts to the spacecraft actions taken in response: a reviewable end-to-end lineage.

Built · Ground-demonstrated 29/29 product tests

S2 · COSRYX-WATCH

Conjunction and anomaly alerts

Receipted alerts, so an operator can later prove which observations a warning came from.

Built · Simulation-validated 33 product tests

S8 · SSA ACCOUNTABILITY

Liability evidence

For satellite and debris-removal operators: prove you warned them, and prove the manoeuvre was reasoned. Emitted in standard space-data formats, mapped to the duties of the 1972 Liability Convention.

Built · Ground-demonstrated 34 product tests

S7 · SWARM TRUST

Decisions of many spacecraft

A receipt for every collective decision of a swarm or constellation, including in a blackout; tolerates up to ⌊(n−1)/3⌋ faulty units and quarantines a rogue one.

Built · Simulation-validated 38 product tests

04 What one alert receipt holds

Enough to recompute. Signed so it cannot drift.

The receipt does not replace the conjunction data message an operator already exchanges. It wraps it: the data, the observation root it came from and the screening policy, under one hybrid signature in the chain.

Field names are illustrative.

conjunction_alert {
  id         : CA-2207
  objects    : A, B
  tca        : +42 min
  miss       : 180 m
  pc         : 2.1e-4
  obs_root   : sha256 9f2c…41   (14 observations)
  policy     : screening v3
  prev       : sha256 51d0…7e
  signature  : Ed25519 + ML-DSA-65
}
05 Who it serves

Every party gets the same checkable record.

OPERATORS

Show you acted on what you knew.

A signed trail of each alert and decision, ready before anyone asks.

INSURERS

Assess a loss on evidence.

Replay the chain offline instead of reconciling each party's logs.

REGULATORS

See that screening happened.

Receipts show which alerts were raised, received and answered.

DEBRIS REMOVAL

Account for close operations.

Rendezvous decisions with a target object, each one receipted.

CONSTELLATIONS

Many satellites, one record.

SWARM TRUST receipts collective manoeuvre decisions across a fleet.

RESEARCHERS

Trace a dataset to its sensors.

SPACETRACE lineage from published result back to raw track.

06 In the numbers

134 product tests across the SSA chain.

29/29SPACETRACE product testsGround-demonstrated
33COSRYX-WATCH product testsSimulation-validated
34SSA ACCOUNTABILITY product testsGround-demonstrated
38SWARM TRUST product testsSimulation-validated

29 + 33 + 34 + 38 = 134, part of the 692 product tests. The conjunction in the scenes on this page is illustrative and simulated: its miss distance and probability are example values.

07 Limits

Evidence, not tracking.

COSRYX does not operate sensors or a catalogue, and it does not decide whether a satellite should manoeuvre. It records, signs and chains what the sensors, screening tools and operators already do.

A receipt proves what was recorded and when. It cannot prove a sensor was accurate or a decision was wise; it lets others judge that on the real record.

The products are built and validated on the ground and in simulation. None has been used in a real operator's screening process.

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

08 Questions

On space situational awareness.

Does this need anything on the satellite?

No. The SSA chain is minted on the ground: at sensor ingest, at screening and at the operator's console. A spacecraft that receipts its own manoeuvre execution adds one more link, but it is not required.

Can two operators share one chain?

They can each keep their own and cross-reference the other's receipts by hash. Neither needs to trust the other's database.

What standards does it use?

Alerts are emitted in the CCSDS conjunction data message family. Receipts use the DCS R-Series format with hybrid Ed25519 + ML-DSA-65 signatures.

Is the collision probability computed by COSRYX?

COSRYX-WATCH computes alerts in simulation. In a real deployment, the operator's own screening service can stay in place; the receipt wraps its output.

09 See everything

Every programme, on one board.

Earth, Moon, Mars and cross-mission products, with status labels and test counts named by population.