Identity before ingestion.
A payload is useful evidence only when the system can prove which admitted device or partner delivered it.
HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network ↗
VERIFIABLE MACHINE & OPERATIONAL DATA
Machine data
becomes evidence.
Hybrid-Chain authenticates every source, validates every JSON payload, fixes every accepted event into an append-only sequence, and makes the resulting operational history independently auditable.
SOURCE AUTHENTICATEDSCHEMA VALIDATEDPAYLOAD COMMITTEDWEBSOCKET DELIVERY READY
THE OPERATING PRINCIPLE
Store the event.
Prove the sequence.
Audit the machine.
Validation before truth.
Schema, freshness, signature, nonce, and size policy decide whether data joins the canonical chain or private quarantine.
Retention without ambiguity.
Protected content can expire while its commitment, chain position, and retention outcome remain independently verifiable.
THE EVIDENCE PIPELINE
Six boundaries.
No silent shortcuts.
Explore the path from a device-signed JSON envelope to a public-safe proof. Each stage has a different responsibility and an explicit failure boundary.
STREAM CONTRACT · WATER-PLANT-07Signed telemetry evidence
CHAIN INTACT01 · AUTHENTICATE
Know which machine spoke.
A registered device presents its scoped source credential and signs the canonical delivery envelope.
- EVIDENCE CREATED
- Device identity, credential key ID, nonce, signature result, and source timestamp.
- FAIL-CLOSED BOUNDARY
- Unknown, revoked, replayed, or incorrectly signed sources never enter the event chain.
APPEND-ONLY INTEGRITY
Change one event.
Break every link after it.
Each accepted event commits to its payload and the preceding chain state. A later verifier can replay the same derivation and detect deletion, substitution, reordering, or duplication.
Verify an event chain ↗4d71…ca82RETAINED883d…a45eSCHEMA VALIDbf09…17c4INTACTPUBLIC-SAFE PROOF CLASSES
Reveal integrity.
Keep protected data protected.
Evidence Streams can expose enough to verify origin, validation, sequence, and retention without publishing device secrets, customer-only metadata, encrypted attachments, or private payloads.
Who produced it.
Registered device identity, credential key ID, signed envelope, timestamp, and replay-resistant nonce.
Inspect proof output ↗What was accepted.
Schema version, validation outcome, event type, payload commitment, size, and canonical event sequence.
Inspect proof output ↗What remains available.
Encrypted attachment manifest, content hash, retention deadline, redaction state, and surviving commitment.
Inspect proof output ↗Where it belongs.
Previous event hash, current payload hash, derived chain hash, Core receipt, and public verification state.
Inspect proof output ↗ENCRYPTED ATTACHMENTS & RETENTION
Let content expire.
Keep the audit trail.
Images, reports, calibration files, certificates, and other supporting evidence can be encrypted and bound to an event. Retention maintenance removes eligible protected content while preserving the manifest, content commitment, and redaction record needed to explain what happened.
ENCRYPTED AT RESTEVENT-BOUND MANIFESTPOLICY EXPIRYCOMMITMENT SURVIVES
OPERATIONAL DELIVERY
Ingest once.
Operate in real time.
REST and authenticated WebSocket transport serve different device and application profiles, but both converge on the same canonical ingestion rules. Downstream consumers receive accepted evidence—not an unaudited parallel feed.
Signed JSON, batches, and supporting attachments.
Authenticate, validate, sequence, commit, alert, and meter.
API, WebSocket, retained replay, analytics, and public proof.
WHERE IT FITS
One evidence fabric.
Every machine estate.
Turn high-volume JSON and sensor data into auditable evidence. Start with one project or use the same verifiable ingestion boundary across an entire partner and device ecosystem.
Retain flow, pressure, quality, generation, storage, and maintenance evidence across distributed infrastructure.
Bind machine state, production metrics, quality checks, and operator interventions into one auditable sequence.
Prove custody changes, environmental conditions, location events, and supporting documentation across partners.
Preserve instrument observations and dataset provenance so later analysis can be traced to its source conditions.
Give models a signed record of the machine data, policy, and event sequence used to train or trigger them.
Produce a clear operational trail without placing source credentials or protected payloads in a public database.
AUTHENTICATE · VALIDATE · CHAIN · RETAIN · DELIVER · AUDIT