StaticverifyVerifies an Ed25519 signature against the provided data and public key.
The signature to verify (Uint8Array).
The original data that was signed (Uint8Array).
The public key to verify against (Uint8Array).
A Promise resolving to true if the signature is valid, false otherwise.
The metadata object associated with this Handle.
Derives a SubHandle from this Handle.
This is the autonomous entry point for IoT devices and other contexts where the Identity is not available locally. The Handle uses its own private key internally (it never leaves the class) to derive a child key via HKDF-SHA256.
The resulting SubHandle is cryptographically identical to the one produced
by Identity.deriveSubHandle(this.name, subName).
The SubHandle name (will be normalized).
Optionalmetadata: SubHandleMetadataOptional SubHandle metadata with constraints.
A Promise resolving to the derived SubHandle with path [this.name, name].
Issues an attestation for a derived SubHandle, binding its derived key to the name and grant. Autonomous: requires only this Handle's own key, no Identity and no network.
The child key is derived internally, so the attestation's
subjectId always equals the key produced by
identity.deriveSubHandle(this.name, subName).
Note: this method does not check this Handle's own grant — it may
not have one (Mode 1). Nesting is enforced by verifiers in
Session.verifyAttested (a child grant exceeding the parent's is
rejected with SCOPE_EXCEEDED/TTL_EXCEEDED at level ROOT).
Optionalopts: { OptionalttlOptionalexpiresOptionaljti?: stringOptionalnow?: numberDeterministically derives a secret (e.g., a password or API key) for a specific service context.
The private key never leaves this class, ensuring maximum security.
A unique identifier for the service (e.g., 'google', 'github').
Length of the derived raw bytes (default: 16 bytes ≈ 22 chars base64url).
A URL-safe base64 string suitable for use as a strong password.
Derives a symmetric 256-bit channel key for secure communication between the Identity (controller) and this Handle (device/context).
Both parties can independently compute this key because:
identity.deriveHandle(name).This enables zero-knowledge encrypted channels without key exchange protocols.
Channel identifier for domain separation (e.g., 'drone-001').
Both parties MUST use the same context.
A 32-byte Uint8Array suitable for AES-256-GCM encryption.
Derives a shared secret using ECDH (X25519) for P2P key exchange.
Converts the Ed25519 keypair to X25519 for Diffie-Hellman key agreement, then applies HKDF-SHA256 to produce a clean 32-byte channel key.
The Ed25519 public key of the other party (32 bytes).
A Promise resolving to a 32-byte shared secret suitable for AES-256-GCM.
Represents a context-specific cryptographic handle derived from an Identity.
A Handle encapsulates a private key tied to a specific name (context). It provides methods for signing data, verifying signatures, and deriving secondary secrets (passwords, channel keys, shared secrets) without ever exposing the underlying private key.
A Handle can also derive SubHandles for hierarchical access control (e.g., an IoT device deriving keys for its components). The private key never leaves the Handle — derivation is performed internally using HKDF.