> 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-run-zkproofer-nodes/binding-and-delegating.md).

# Binding & Delegating

Bind your license NFT and delegate it to start verification work and accrual of rewards.

Two things need to happen before your node starts doing anything: you bind the License NFT to a node instance, and you delegate it to a burner wallet. The burner wallet is what actually submits verification proofs on-chain.

Once delegation is live, the node starts sending heartbeats and accruing rewards.

***

### Pick your setup

There are two ways to do this. The main difference is whether you want to run the node infrastructure yourself.

#### Using a NaaS Provider

A NaaS provider runs the infrastructure for you — the Docker container, the burner wallet, gas top-ups, uptime. You keep ownership of the License NFT and delegate to their wallet. If you don't want to think about servers, this is the way to go.

#### Running Your Own Node

You run the Docker container yourself. You manage the burner wallet, fund gas, and keep the node online. More work, but you control everything.

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

[Running your own Node](https://docs.humanity.org/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating/running-your-own-node.md)


---

# 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://docs.humanity.org/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating.md?ask=<question>&goal=<user_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.
