# FAQs and Troubleshooting

## FAQs

### Q1: What is the current block cadence target?

**A:** Current operational target in this docs set is **4 BPS**. Effective cadence can vary by mode and network conditions.

### Q2: What is the fastest supported setup path?

**A:** Docker Compose (`sudo docker compose up -d`) from [Setup Guide](/testnet/setup-guide.md).

### Q3: How do I control mining behavior?

**A:** Configure `run/hydra.toml` using `mining_type` (`stratum`, `cpu`, `disable`), `mining_author`, and stratum fields. See [Mining Guide](/testnet/mining.md).

### Q4: How do I inspect chain health quickly?

**A:** Run:

```bash
./run/mazze-cli.sh status
./run/mazze-cli.sh summary
```

and use `mazze_getStatus` from [RPC Guide](/testnet/rpc.md).

### Q5: Which section is canonical for privacy implementation?

**A:** `privacy/` is canonical.

## Troubleshooting

### Issue 1: Node starts but chain does not advance

* Confirm RPC responds (`./run/mazze-cli.sh status`).
* If mining is expected, verify `mining_author` and `mining_type`.
* In stratum mode, confirm `stratum_secret`, miner connectivity, and worker logs.

### Issue 2: Miner running but no accepted work

* Check node and miner logs ([Viewing Mazze Logs](/testnet/viewing-logs.md)).
* Confirm `stratum_address`, `stratum_port`, and secrets match.
* Validate thread settings (`NUM_THREADS`, `RANDOMX_FULL_MEM`) where relevant.

### Issue 3: CLI commands fail

* Verify `RPC_URL` points to active endpoint.
* Ensure HTTP RPC is enabled in `run/hydra.toml`.
* Check if local-only RPC port is used by your setup.

### Issue 4: Config changes have no effect in Docker

Apply config by recreating containers:

```bash
sudo docker compose up -d --force-recreate
```


---

# 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.mazze.io/testnet/faqs-and-troubleshooting.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.