> 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/for-chain-operators/seda-overlay-node-quick-start-guide/phase-1-node-setup.md).

# Phase 1: Node Setup

### Step 1: Download Overlay Binary

Visit the [GitHub Releases page](https://github.com/sedaprotocol/seda-overlay-ts/releases) and download the latest version of the `seda-overlay-ts` binary for your platform, or use one of the following commands:

{% tabs %}
{% tab title="Linux x64" %}

```
curl -L -o seda-overlay https://github.com/sedaprotocol/seda-overlay-ts/releases/download/v1.0.2/seda-overlay-linux-x64
```

{% endtab %}

{% tab title="Linux ARM64" %}

```bash
curl -L -o seda-overlay https://github.com/sedaprotocol/seda-overlay-ts/releases/download/v1.0.2/seda-overlay-linux-arm64
```

{% endtab %}
{% endtabs %}

### Step 2: Make It Executable and Verify Version

```bash
chmod +x seda-overlay
```

Check the `seda-overlay-ts` version:

```bash
./seda-overlay --version

# Output: 1.0.0-rc.23 (or higher)
```

### Step 3: Initialize and Configure the Node

```bash
./seda-overlay init --network <testnet | mainnet>

# Output:
# Config file has been created at: /home/ec2-user/.seda/testnet/config.jsonc
# Please fill in all properties (such as mnemonic)
```

Open the config file and enter your SEDA mnemonic (an account with tokens is required, both on testnet and mainnet).

### Step 4: Fetch Your Node's Public Key (for allowlisting)

```bash
./seda-overlay identities info --network <testnet | mainnet> --offline
```

This will print your node’s identity public key. \
\
Example:

```bash
Config file: /home/ec2-user/.seda/testnet/config.jsonc
┌─────────┬──────────────────────────────────────────────────────────────────────┐
│ (index) │ Identity Public Key                                                  │
├─────────┼──────────────────────────────────────────────────────────────────────┤
│ 0       │ '020c4fe9e5063e7b5051284423089682082cf085a3b8f9e86bdb30407d761efc49' │
└─────────┴──────────────────────────────────────────────────────────────────────┘
```

### Step 5: Submit your Overlay Public Key

📫 Submit this Overlay Public Key to the SEDA team to be included in the allowlist via the Form linked below:

* Mainnet: <https://forms.gle/K3nzqtCrzF8wVeyCA>
* Testnet: <https://forms.gle/tB1qJwM6NWCy7ECx9>

<figure><img src="/files/ENyEBxZKR1O7itA3qeFI" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
&#x20;Do not confuse it with your operator SEDA address (starting with `seda...`).
{% endhint %}

{% content-ref url="/pages/aPPiilfA6qfW97YknRVc" %}
[Phase 2: Running the Overlay Node](/home/for-chain-operators/seda-overlay-node-quick-start-guide/phase-2-running-the-overlay-node.md)
{% endcontent-ref %}


---

# 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/for-chain-operators/seda-overlay-node-quick-start-guide/phase-1-node-setup.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.