> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/infrastructure/running-a-node-validator/non-sgx-node-beta/setting-up-a-non-sgx-node.md).

# Setting up a Non-SGX Node

Download the Non-SGX Binary from the release page and replace secretd.

Configure Upstream Providers: Define your Provider pool by creating the `~/.secretd/config/sgx_nodes.json` configuration:

```
{
  "nodes": [
    "sgx-provider-1.yourdomain.com:9090",
    "sgx-provider-2.yourdomain.com:9090"
  ]
}
```

Enable Replay Mode:

```
export SECRET_NODE_MODE=replay
```

Start the Node:

```
./secretd-nosgx start
```

#### **Syncing Strategies**

Non-SGX instances are fully compatible with standard Cosmos SDK synchronization methods. Operators may perform a full sync from genesis, utilize rapid State Sync, or deploy a standard snapshot and begin trace replay from the snapshot height.

### Troubleshooting

#### Node stalls with "Waiting for SGX node trace"

The Non-SGX node will persist in retry attempts if the execution trace is unavailable. Verify the following:

* Provider Connectivity: Ensure the SGX Provider is active and the gRPC port is reachable via the network.
* Consensus Lag: It is standard for the Consumer to lag approximately 1-2 blocks behind the Provider during real-time synchronization.
* Data Pruning: The requested block may have been pruned by the Provider. In this case, synchronize from a more recent state.

#### Cannot serve encrypted queries

This is expected behavior. Since Non-SGX nodes do not possess a secure enclave, they lack the keys required to decrypt contract state. All privacy-preserving requests must be routed to an SGX-enabled RPC endpoint.


---

# 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://docs.scrt.network/secret-network-documentation/infrastructure/running-a-node-validator/non-sgx-node-beta/setting-up-a-non-sgx-node.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.