Verify the source
Validate a laboratory result signature against its expected verifying key.
THE GENYXIS NETWORK
From a person.
To trusted access.
Follow Alex from a service access request, through a laboratory and the Genyxis verification workflow, to a credential the service can evaluate. The complete example plays automatically.
GENYXIS / NETWORK v03D CONCEPT VISUALIZATION
Drag to rotate · Motion starts automatically01 / REQUEST ACCESS
Alex requests access to a fictional partner service. The service asks for a verified identity credential before granting access.
Travelling: access request. No biological information.
What Genyxis does
Protected ingress, laboratory signature verification, result and nonce replay checks, credential issuance and retained evidence.
What the service does
Verify the presented credential and apply its own access policy. Invalid signatures or reused evidence stop issuance earlier.
What stays off-chain
Raw biological information and retained laboratory evidence. The fictional service receives a credential presentation, not a DNA sample.
Illustrative workflow, not live telemetry or an active laboratory/service partnership. Signature verification, replay protection and credential issuance represent the Genyxis proof stack. Consent, laboratory processing and partner-service approval are example integrations. The three nodes are independent instances, not sequential specialist roles. Peer links do not imply consensus or evidence replication. Zero-knowledge proofs remain a development goal.
Reject the replay
Check submission nonces and result reuse before issuing a credential.
Issue with evidence
Create a credential and retain the evidence needed to support review.
Proof stack: signed result / verification / replay checks / credential issuance / retained evidence.