Reference

Glossary

The vocabulary of a verifiable agent — the 0G primitives it stands on, and the Sworn-specific terms the proof feed uses.

#0G terms

TermDefinition
0G Compute0G’s decentralized compute network. Sworn runs inference against a TEE-capable provider through the compute broker, which can attest the response came from the enclave.
0G Storage0G’s content-addressed storage. A sealed memory blob is identified by a merkle root hash — the public commitment. Propagation is ~3–5 min.
0G Chain0G’s EVM L1 (Galileo testnet, chain id 16602). Hosts the AgentRegistry and settles compute/storage transactions.
TEE / TeeMLTrusted Execution Environment. A TeeML provider runs the model in an enclave and produces a signature the broker verifies via processResponse.

#Sworn terms

TermDefinition
Inference receiptThe proof-feed record of one attested response: provider, model, chat id, and a verified flag straight from the broker — never hardcoded.
Memory receiptThe proof-feed record of one memory commitment: the 0G Storage root hash, tx, and a status chip (Filing → On the record).
The SealThe crimson wax-stamp that renders only on a genuinely attested call. “This call is sworn.”
Encrypt-to-selfSealing a memory object with a key derived from the agent wallet secret (AES-256-GCM) before upload — so the root hash is public but the contents are not.
ConsolidationDistilling a turn into the minimal delta of durable facts worth committing; returns nothing when nothing changed.
ReconciliationThe background pass that flips a commitment pending → verified once its root hash is downloadable and decrypts to a valid memory.
Counsel, not custodySworn advises and the user signs. It never holds, moves, or has signing authority over funds.