Wavestar Technology · Engineering posture
Trust distributed across every layer of the stack.
Wavestar settles real operator funds against real orbital rights. That forces a posture: no single component — not the clearing engine, not the observers, not the registry, not the anchoring chain — is a single point of trust. Merkle transparency, threshold cryptography, and two public chains combine to make every settlement auditable by any counterparty at any time.
- Transparency log
- Trillian · RFC 6962
- Quorum signatures
- BLS12-381 · 8-of-12
- Anchoring
- Ethereum + Bitcoin · hourly
- DID method
- did:orbit:*
Five technical surfaces
One registry. Four subsystems. One security posture.
Wavestar ships as four modules on a shared identity registry. The technology surface is described in five documents — one per architectural concern — each linked below.
- 01
Trust model
Hybrid: permissioned Merkle transparency log (Trillian, RFC 6962) plus BLS12-381 quorum signatures from a 12-observer federation, anchored hourly into Ethereum and Bitcoin. Merkle for completeness proofs; signatures for agreement; anchoring for civilisational durability. Read the trust model. - 02
did:orbit — the identity registry
A W3C DID method extension for orbital entities. Operators, satellites, ground stations, observers, and cleared contracts all resolve to a signed JSON document served over HTTPS and mirrored in the Trillian log. Read the did:orbit spec. - 03
Federated attestation
Twelve independent observers — ground stations, SSA providers, fleet operators, academic consortia, regulators, and neutral commercial specialists. Eight-of-twelve threshold BLS signatures aggregate to a single 96-byte proof verified with one pairing. Read the attestation architecture. - 04
System architecture
Rust clearing core (sub-2ms matching). Go registry on Trillian plus CockroachDB. Next.js 15 Terminal and Market. NATS JetStream event bus. Python 3.12 AI services. Multi- region active-active with tenant-scoped query isolation at every read path. Read the architecture reference. - 05
Security posture
SOC 2 Type II and ISO 27001 in flight. HSM-backed keys, 90-day rotation with key-continuity proofs, explicit tenant isolation on every DB query, a documented responsible-disclosure programme, and quarterly third-party penetration tests. Read the security posture.
First principle
Every input to a settlement decision must be able to withstand an adversarial court subpoena. Signatures or it didn’t happen.
Technology by the numbers
Engineered for the 2030 orbital tape.
The numbers below are v1 steady-state targets — validated in load testing against the Sprint 8 engine build, not marketing projections.
- Match latency p99
- 1.8 ms
- Attestation p99
- 420 ms
- Transparency append p99
- 95 ms
- Settlement finality
- < 1.2 s
- Observer quorum
- 8-of-12
- Anchoring cadence
- Hourly
- Uptime target
- 99.995%
- Key rotation
- 90 days
For engineers
Every claim on this site is testable.
Source-available protocol, open SDKs, signed attestations on every trade, and a public transparency log. Start with the trust model, or dive straight into the quickstart.