> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/features/hardware-binding.md). # Hardware binding and bans With binding on, a key has one canonical device. The first successful keyed admission binds an unbound key. A different device is rejected until the binding is reset. ## Reset a binding Reset when a user changes devices or loses their local identity. A reset clears the binding and invalidates affected leases. It doesn't renew the key, restart its timer, erase history/usage, or remove bans. User Discord resets follow the project's allowance. Owner resets preserve that quota. A v2 reset needs a bound, non-banned, non-revoked key; otherwise it returns `KEY_STATE_CONFLICT`. ## FFA and binding disabled FFA keys and projects with binding off skip the binding rule. Neither bypasses a hardware ban. ## Ban a key or a device? * **Ban key:** blocks that key. * **Ban HWID:** blocks that device across keys in the project. * **Ban both:** does both. Unbanning a device doesn't unban its key, or vice versa. ## Fingerprints Additional fingerprint observations help compare runs and resets. They are advisory client-supplied signals, not identity proof. The enforced HWID and the fingerprint have different jobs; fingerprint metadata isn't a hardware-ban target in the bot. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://vampauth.gitbook.io/vampauth-docs/features/hardware-binding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.