Offline licensing
Ed25519 signatures and the limits of offline operation.
File format
A license download contains payload, signature, algorithm, and the platform public key. payload is the original JSON string. Signature verification must use its original UTF-8 bytes, without parsing and reserializing it first.
Verification workflow
- Pin a trusted public key in the SDK. Do not trust an arbitrary public key supplied by the license file itself.
- Verify the signature using Ed25519.
- Parse the payload and validate the schema, product, platform, validity period, and project ownership.
- Reject initialization if signature verification fails, the license has expired, or parameters do not match.
The platform currently issues trial licenses and does not implement hardware-bound licensing. Device identification, tamper resistance, and protection against system-clock rollback must be implemented by the SDK team before delivery.
Revocation and offline limits
Revocation immediately affects subsequent downloads and cloud calls. A fully offline device cannot receive status changes immediately. An existing license can only be restricted through expiry, a later online check, or a customer update. The console's revoke action must not be described as instantly disabling all offline devices.
Signing-key management
The private key is stored only in the protected server data directory. Production deployments should use a controlled signing service or hardware key management and plan public-key rotation with a transition period.
