# Enabling SEDA FAST on a Data Proxy

SEDA FAST is a low-latency data access layer built on top of SEDA.\
For an overview of SEDA FAST, see [Getting Started](/home/developer/getting-started/quickstart.md).

To enable SEDA FAST on a Data Proxy, operators must:

1. Upgrade the Data Proxy to a compatible version
2. Enable SEDA FAST support via configuration (or CLI)
3. Restart and verify the configuration
4. Ensure the Data Proxy is registered on the SEDA FAST side

SEDA FAST can be enabled independently on **testnet** and **mainnet**.\
Credits, keys, and registration are **network-specific**.

### Prerequisites

Before proceeding, ensure that:

* You operate a SEDA Data Proxy
* You have access to the Data Proxy configuration and restart process
* You are enabling SEDA FAST on the **correct network** (testnet or mainnet)

### Step 1: Upgrade the Data Proxy

SEDA FAST support requires **Data Proxy version v1.3.4 or later**.

Upgrade your Data Proxy using the official release:

* <https://github.com/sedaprotocol/seda-data-proxy/releases>

### Step 2: Enable SEDA FAST Support

SEDA FAST is enabled by adding the FAST public key as a trusted client in your Data Proxy configuration.

The Data Proxy CLI provides a helper command:

```bash
seda-data-proxy enable-fast "<FAST_PUBLIC_KEY>"
```

#### FAST Public Keys

Use the public key corresponding to the network you are enabling:

<table><thead><tr><th width="123.48046875">Network</th><th>FAST PublicKey</th></tr></thead><tbody><tr><td>Testnet</td><td><code>021eacf821d4d21ad61515fc1212ca75739730bf0abcf4925045e3ebde0f93a7e8</code></td></tr><tr><td>Mainnet</td><td><code>025316f89e976d2e41b1437f7a6552a547a1e4900e861ca485c842ed3f016a7824</code></td></tr></tbody></table>

You can verify the active testnet FAST key at:

* `https://fast-api.testnet.seda.xyz/info`
* `https://fast-api.mainnet.seda.xyz/info`

> ⚠️ **Important**\
> Testnet and Mainnet FAST keys are different.\
> Make sure you use the correct key for each Data Proxy instance.

#### Alternative: Enable SEDA FAST via Configuration File

Instead of using the CLI, you can enable SEDA FAST by updating the Data Proxy configuration file directly.

Add the FAST public key to the `sedaFast` section of your `config.json`:

```json
{
  "routeGroup": "proxy",
  "routes": [
    // ...
  ],
  "sedaFast": {
    "enable": true,
    "allowedClients": [
      "PUBLIC_KEY_FROM_ABOVE"
    ]
  }
}
```

### Step 3: Restart the Data Proxy

After enabling SEDA FAST support, restart your Data Proxy so the updated configuration is loaded.

### Step 4: Verify the Configuration

You can verify that SEDA FAST is correctly enabled by querying the Data Proxy info endpoint:

```bash
curl <DATA_PROXY_URL>/status/info
```

The response should include a section indicating that **SEDA FAST is enabled**, along with the configured FAST public key.

### Additional Considerations

Enabling SEDA FAST in the Data Proxy configuration is required, but not sufficient on its own.

Each Data Proxy must also be **registered on the SEDA FAST side** under the Data Proxy’s public key.\
This registration is handled by SEDA and includes assigning a credit cost to the Data Proxy. If a Data Proxy is not registered, SEDA FAST requests routed through it will not succeed.

If you plan to enable SEDA FAST on your Data Proxy or have questions about registration, please reach out to the SEDA team for next steps.


---

# 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.seda.xyz/home/tech/operating-a-data-proxy/enabling-seda-fast-on-a-data-proxy.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.