> 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-an-sgx-provider-node/registering-sgx-provider-with-the-contract.md).

# Registering SGX Provider with the Contract

Optionally, the SGX Provider can register its services with the Registration Conract so that the Non-SGX node operators can discover the services

The registry repository, including the contract details and listed provider nodes, is available in the [sgx-node-registry README](https://github.com/scrtlabs/sgx-node-registry/blob/master/README.md). This step is optional. Direct connections still work when the provider endpoint is already known.

The registry contract is deployed on Secret mainnet, so you can query it directly to inspect registered providers before configuring a Non-SGX node. This is useful when you want to discover available SGX providers, check a specific node identity, or list all nodes published by one operator.

Use the following examples against the mainnet contract:

```bash
# List registered nodes
secretcli q compute query secret1h7xzl06j47vvp4ajwfge6la7gu8anxvpqt326k \
  '{"list_nodes":{}}'

# Get one node by identity
secretcli q compute query secret1h7xzl06j47vvp4ajwfge6la7gu8anxvpqt326k \
  '{"get_node":{"identity":"<NODE_IDENTITY>"}}'

# List all nodes registered by one operator
secretcli q compute query secret1h7xzl06j47vvp4ajwfge6la7gu8anxvpqt326k \
  '{"list_nodes_by_operator":{"operator":"<WALLET_ADDRESS>"}}'
```


---

# 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-an-sgx-provider-node/registering-sgx-provider-with-the-contract.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.