Privacy Rings, Provable Authority, and Confidential Compute in one Solana settlement loop.
Every component executes on Solana L1 (~400ms slots) with per-escrow PDAs so thousands of autonomous agent calls settle concurrently without exposing balances, vendor graphs, or request payloads.
Interactive state transitions
Select any stage of the Sealed 402 Settlement loop to inspect on-chain predicate checks and wire commitments.
HTTP 402 Challenge
The agent calls an attested endpoint via kalo.fetch(). Pre-execution middleware strips IP, user-agent, and session identifiers in under 6ms p99. The provider replies with HTTP 402 containing request_hash, price commitment, and its registered enclave_pubkey.
HTTP/1.1 402 Payment Required
X-Kalo-Protocol: kalo-402/v1
X-Kalo-Request-Hash: 0x4e9b...81a2
X-Kalo-Enclave: IntelTDX · tdx:8a2f...e91b
X-Kalo-Price-Commitment: 0x9f4a...c21eThree deterministic protocol invariants.
Enforced on-chain inside kalo_protocol (7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S) on every instruction.
1. No unauthorized spend
lock_sealed_402 succeeds only when mandate.revoked == false, the mandate has not expired, the service category bit is allowed, per-call and epoch caps hold, and the UTXO nullifier has never been spent.
2. No payout without TEE receipt
settle_with_receipt releases funds only when an Ed25519 signature over SHA256(escrow_pda || request_hash || output_hash) verifies against an active, non-expired EnclaveRegistry key.
3. Conservation of value
For every settled escrow, the sum of the provider’s shielded output commitment and the protocol fee commitment equals escrow.commitment_in via Groth16 / Pedersen balance proof.
On-chain program surface
Program ID: 7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S