Research
Glossary
Terms used across the site. Same definitions power inline tooltips elsewhere.
- bearingsProtocol
- The six directional choices (up, down, left, right, forward, back) a prover makes each round. Bearings are one-shot: by the time anything could observe them, they are already spent.
- binaryArtifact
- The compiled executable form of a circuit. Built from the standard, hardened, or hybrid source with its configuration and entropy embedded, so identity travels with the artifact rather than sitting in a vault.
- burnLedger
- Spending a nonce so it can never be used again. The gate burns the nonce before it validates the proof, which is the structural reason replay fails: every submission spends the nonce even when validation later rejects it.
- circuitIdentity
- A user's or workload's cryptographic identity, embodied as a compiled binary that carries its own config, entropy, and policy. Identified by a handle and by the SHA-256 of the artifact.
- commitLedger
- The ledger operation that marks a nonce SPENT.
- envelopeProtocol
- The authority object that replaces a bearer token. A one-shot proof bound to the method, the endpoint, the hash of the request body, the policy, the timestamp, and a single-use nonce, so it authorizes exactly one request and nothing else.
- EPINPlatform
- The public API surface: the set of public domains and endpoints through which the platform is reached.
- gate orderProtocol
- The fixed sequence of checks a gate runs on an untrusted request before any application logic executes: recompute the request hash, check endpoint and policy, confirm the circuit is active, check freshness, burn the nonce, validate the proof, apply application policy, then serve.
- handleIdentity
- The user or organization identifier that resolves to the current circuit. Deactivating a handle is how revocation happens (one state change rather than a rotation campaign).
- hybrid circuitIdentity
- A circuit variant with a four-shard prime and an X25519 + Kyber768 key exchange, giving post-quantum protection for the key agreement. Adds agent mode for machine-to-machine use.
- manifestArtifact
- The metadata record for a binary: its hash, size, timestamps, and self-validation state. The registry uses it to verify and index artifacts.
- nonce_uuidLedger
- The identifier of a ledger-reserved nonce. It is issued at reserve, returned with the proof, and spent on use. A nonce is good for exactly one request.
- proof_hashProtocol
- The hash the circuit produces from a proof run, carried in the proof payload and checked during validation.
- protected endpointPlatform
- A single route or tool placed behind a gate. It is the unit of value on every commercial page (what you buy is endpoints under proof, not seats or circuits).
- reserveLedger
- The ledger operation that allocates a fresh nonce with a timestamp and a time-to-live, marking it RESERVED.
- tau (τ)Protocol
- The timestamp, in microseconds since the UNIX epoch, that the ledger sets when a nonce is reserved. It is bound into the proof and checked against a freshness window, so a captured envelope goes stale in seconds.