Biometric Proof Registry

Each gaze verification session produces an opaque proof hash — a 32-byte digest of the user's AGT tensor sequence. Raw biometric data never leaves the validator node. Only the hash and attestation metadata are bridged to Solana.

Gaze Proof Payload

interface GazeProofPayload {
  sessionId: string;
  timestamp: number;
  expirationWindow: number;          // 30s default
  agtSequence: ("COG" | "EMO" | "ENV")[];
  holdDurationsMs: number[];
  proofHash: string;                 // 32-byte opaque hash (hex)
  confidence: number;                // 0.0–1.0
}

The proof hash binds the session nonce, AGT sequence, hold durations, and timestamp. The encoding algorithm is proprietary — integrators submit the hash via AARON REST endpoints; they do not need to reproduce the hash locally.

AARON Session Flow

1. Create session — POST https://aaron.jettoptics.ai/session returns a challenge with target AGT positions.
2. Capture gaze — client records iris vectors and classifies each hold into COG, EMO, or ENV.
3. Verify — POST /verify submits the proof hash and session metadata.
4. Attest — verified sessions are written to SpacetimeDB and optionally bridged to the jtx_cstb_trust program on Solana.

See How It Works for the step-by-step flow and Client Integration for SDK examples.

On-Chain Attestation

Verified proofs map to AGT attestation PDAs on Solana mainnet via the jettoptx-poa-depin program. The on-chain record stores:

Privacy is enforced at every layer: the chain sees only the hash, never raw iris data or intermediate encodings.

SpacetimeDB Integration

AARON writes session state and proof records to SpacetimeDB at stdb.jettoptics.ai. Clients can subscribe to real-time attestation events for agent workflows. See AARON Architecture for the internal pipeline.