> For the complete documentation index, see [llms.txt](https://klayoracle.gitbook.io/v1.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klayoracle.gitbook.io/v1.0.0/nodes/install-and-run-node-locally.md).

# Install & run node locally

{% hint style="info" %}
This section is currently being developed. To contribute, open a pull request on the [documentation GitHub repo](https://github.com/KlayOracle/klayoracle-docs).
{% endhint %}

* Generate a selfsigned certificate for each node. [see guide using open ssl](https://github.com/KlayOracle/klayoracle-monorepo/blob/development/setup-guide/openssl).
* Use different authority or wildcard matching authority of each node you intend to run.
* In `node/config.yml`, set the `key` and the `pem` you used to generate the certificate.
* Give the certificate pem file to data providers for authenticating with your Node. You can also run your own data providers.
* Update your organization details in `node/config.yml`. Website must match authority used to sign certificate, an example will be if authority is `*.origineum.com`, website can be `node-1.origineum.com`. Otherwise, node service will fail to start.
* In `.env`, `HOST_IP` is the dns for reaching your node. If you're running a docker container, you can override it and other `env` variable by passing from terminal.
* In `.env` `PRIVATE_KEY` is your Node signer with enough Klay tokens to pay for request.
* In `.env` `COCKROACH_DNS_URL` is your full connection string to <https://cockroachlabs.cloud/> cluster. A free account will suffice for a considerable period.
* In `.env` `OAUTH_TOKEN` is the Oauth token given to data providers using your Node.
* Run `make gomodtidy`, `make node-tables`, `make node-server-nolog HOST_IP=0.0.0.0:50054` or `make node-server HOST_IP=0.0.0.0:50054` on your local machine to test it locally.


---

# 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://klayoracle.gitbook.io/v1.0.0/nodes/install-and-run-node-locally.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.