License Management

Lifecycle

Action	Effect
Create	Issue a new key with an optional expiry and alias.
Revoke	Ban the key. `key/check` returns `KEY_BANNED`.
Expire	Key passes its `expires_at`; `key/check` returns `KEY_EXPIRED`.
Reset HWID	Release the hardware binding(s) so the key can activate on new hardware.
Delete	Remove the key from the project.

HWID binding

Keys lock to the hardware that first activates them. key/check compares the client-sent hwid against the key’s bound hardware IDs and returns FINGERPRINT_MISMATCH when they differ.

hwid_binding (project setting) — master switch.
max_hwid_per_key — how many hardware IDs one key may bind (1–10). Forced to 1 when binding is off.
FFA — free-for-all keys skip binding entirely. Forced on when project binding is disabled.
HWID is passthrough: the client computes its own hwid string; Vampauth only compares what it receives.

Usage stats

Every successful key/check increments executions, refreshes last_used, and seeds first_used. These persist on the license in real time.

⌘I