> For the complete documentation index, see [llms.txt](https://docs.humanity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humanity.org/zkproofer-node/how-to-manage-zkproofer-nodes/managing-licenses.md).

# Managing Licenses

View, transfer, and re-delegate your license NFTs across nodes.

Before a node can begin running, each Verifier Node License NFT must be registered and bound to a specific node installation. This ensures that every license corresponds to a single active zkProofer node within the Humanity network.

The easiest way of binding your node is delegating through a NaaS Provider

[Using a NaaS Provider](/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating/using-a-naas-provider.md)

## **When Binding Can Be Released**

> ⚠️ Unbinding becomes possible only after the 12-month vesting period has completed.

## **What Unbinding is**

Binding remains in place until you explicitly choose to Unbind / Stop delegating your license to a partcular node, either thourh a NaaS or in case you run your own node.

Unbinding must be performed if you plan to:

* Transfer the license to another wallet
* Sell or gift the NFT
* Migrate your node to new hardware
* Delegate node operation to another party

The process can be seen at 

[Stopping Delegation & Unbinding](/zkproofer-node/how-to-run-zkproofer-nodes/stopping-delegation-and-unbinding.md)

## **What Happens After Unbinding**

Once unbound, the Verifier Node License NFT becomes a **free-floating asset** again:

* It **no longer belongs to any node hardware or operator setup**
* It can be **transferred, sold, or delegated** freely
* It remains inactive until a **new binding** is completed
* It does **not accrue rewards or fees** while unbound

This ensures a clean state for safe transfer and reactivation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.humanity.org/zkproofer-node/how-to-manage-zkproofer-nodes/managing-licenses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.