> For the complete documentation index, see [llms.txt](https://docs.kiiglobal.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiiglobal.io/docs/validate-the-network/run-a-validator-full-node/further-guides.md).

# Further guides

Other guides into configuring Kiichain nodes

### Enabling debug EVM JSON-RCP namespace

To enable `debug_` calls on your JSON-RCP node, you need to update your `app.toml`:

1. Go to `app.toml`

```bash
cd $NODE_HOME/config/app.toml
```

Where `$NODE_HOME` is where your node configuration lives.

2. Add the new configuration

On your `app.toml` look for the `json-rpc` section. There, you need to find the `api` key. The section looks like this:

```
###############################################################################
###                           JSON RPC Configuration                        ###
###############################################################################

[json-rpc]

# API defines a list of JSON-RPC namespaces that should be enabled
# Example: "eth,txpool,personal,net,debug,web3"
api = "eth,net,web3"
```

There, you need to add the namespace you want to add. In this case `debug` :

Replace:

```
api = "eth,net,web3"
```

With:

```
api = "eth,net,web3,debug"
```

You can also enable any other namespace that you may want, such as `personal` and `txpool`.

3. Restart the node

Once the node goes live again, the configuration should be applied.


---

# 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.kiiglobal.io/docs/validate-the-network/run-a-validator-full-node/further-guides.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.