> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/tech/for-chain-operators/linking-to-an-external-node.md).

# Linking to an External Node

**Contents**

[#seda-rpc-endpoints](#seda-rpc-endpoints "mention")\
[#configuring-external-node](#configuring-external-node "mention")

### SEDA RPC Endpoints

When connecting externally, choose a trustworthy node operator. Unscrupulous operators might tamper with query outcomes or block transactions. The SEDA team currently provides the following RPC endpoint:

* Mainnet RPC address: `https://rpc.mainnet.seda.xyz`
* Testnet RPC address: `https://rpc.testnet.seda.xyz`

### Configuring External Node

This section is for those linking to an external node, so if you want to run commands from your local machine, or don't feel like running a node yourself you can use the `sedad` binary to connect to an external node. This can be done two ways:

1. Add the `--node` flag to your CLI commands, followed by the RPC endpoint in the `https://<hostname>:<port>` format.
2. Alternatively, tweak configurations in `client.toml` in your chain's configuration directory (default location `~/.sedad/config/client.toml`):

Recommended client configuration for mainnet:

```
###############################################################################
###                           Client Configuration                            ###
###############################################################################

# The network chain ID
chain-id = "seda-1"
# The keyring's backend, where the keys are stored (os|file|kwallet|pass|test|memory)
keyring-backend = "file"
# CLI output format (text|json)
output = "text"
# <host>:<port> to CometBFT RPC interface for this chain
node = "https://rpc.mainnet.seda.xyz"
# Transaction broadcasting mode (sync|async)
broadcast-mode = "sync"
```

Recommended client configuration for testnet:

```
###############################################################################
###                           Client Configuration                            ###
###############################################################################

# The network chain ID
chain-id = "seda-1-testnet"
# The keyring's backend, where the keys are stored (os|file|kwallet|pass|test|memory)
keyring-backend = "file"
# CLI output format (text|json)
output = "text"
# <host>:<port> to CometBFT RPC interface for this chain
node = "https://rpc.testnet.seda.xyz"
# Transaction broadcasting mode (sync|async)
broadcast-mode = "sync"
```

**License**\
Contents of this repository are open source under [GNU General Public License v3.0](https://github.com/sedaprotocol/seda-chain/blob/main/LICENSE).


---

# 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.seda.xyz/home/tech/for-chain-operators/linking-to-an-external-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.