The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT,
SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document
are to be interpreted as described in RFC 2119.
- Codex Entry: A structured, signed data object that encapsulates integrity proofs, storage references, anchors, identity bindings, and optional encryption metadata. It is the fundamental unit of the Lockb0x Protocol.
- Storage Adapter: A module or function that interfaces with an external storage system (e.g., IPFS, S3, Google Cloud Storage, Azure Blob, FTP/SFTP) and produces verifiable proofs of storage.
- Anchor: A blockchain transaction or equivalent immutable record that cryptographically attests to the existence of a Codex Entry at a specific point in time.
- Verifier: A tool or process that checks the validity of a Codex Entry by verifying signatures, integrity proofs, storage claims, and anchors.
- Certificate: A human- or machine-readable document generated from a Codex Entry that provides evidence of integrity, custodianship, and anchoring. Certificates MAY be represented as JSON objects, W3C Verifiable Credentials, or X.509 certificates.
- Identity Context: Identifiers bound to a Codex Entry that describe the controlling party (individual, entity, or asset) and optional contextual hierarchy (e.g., organization, project, work order).
- Encryption Metadata: Information included in a Codex Entry when assets are encrypted, specifying algorithm, key identifiers, and the
last_controlled_byfield to record which key(s) last controlled the encrypted asset.