> For the complete documentation index, see [llms.txt](https://zokanetwork.gitbook.io/zokanetwork/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokanetwork.gitbook.io/zokanetwork/zsilent-core/node-and-miner-control.md).

# Node and Miner Control

ZSilent Core can control the existing Rust binaries through a local process bridge and read node state through the local RPC API.

## Full Node

Users can configure and run a local ZOKA node from the desktop interface.

The node controller starts the local `zoka` binary in full-node mode and keeps mining disabled at launch. This lets the node come online, sync, and expose local status before mining is toggled separately.

Supported runtime configuration includes network selection, optional network configuration files, bootstrap seed settings, Tor proxy options, mining thread preferences, and the reward address used when mining is enabled.

## Miner

Users can configure mining behavior and route rewards to their wallet address.

Mining is controlled through the local node API after the node is running. The desktop app can request `/mining/start` and `/mining/stop`, which allows mining to be toggled without shutting down the node process.

The mining controller validates the reward address and thread count before starting a mining session. It also polls mining status so the dashboard can show whether mining is active and report current session state.

## Operational Flow

1. Start the local full node.
2. Wait for RPC and sync status.
3. Configure the reward wallet address.
4. Start mining with a selected thread count.
5. Monitor node, mining, and wallet state from the dashboard.
6. Stop mining without stopping the node when needed.

## Logs

Logs are useful for diagnosing node and mining state, but must never include private keys, seed phrases, or wallet passwords.

ZSilent Core sanitizes runtime logs before showing them in the UI. Lines that match obvious sensitive terms are redacted instead of displayed directly.


---

# 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:

```
GET https://zokanetwork.gitbook.io/zokanetwork/zsilent-core/node-and-miner-control.md?ask=<question>
```

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.