# Binding & Delegating 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](/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating/using-a-naas-provider.md) [Running your own Node](/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating/running-your-own-node.md) --- # Agent Instructions: 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: ``` GET https://docs.humanity.org/zkproofer-node/how-to-run-zkproofer-nodes/binding-and-delegating.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.