The following instructions assumes you are running a single validator full node with a remote instance of Connect. If you are not running a full node, you do not need to run Connect.
This document will guide you through setting up and running Connect, as well as configuring your node to receive data from Connect.
This tab provides general instructions for starting the Connect sidecar.
If you are running one of the chains listed in the tabs above, please refer to those instructions.
To run Connect, which starts the service on the default port of 8080, enter the following command:
This tab provides general instructions for starting the Connect sidecar.
If you are running one of the chains listed in the tabs above, please refer to those instructions.
To run Connect, which starts the service on the default port of 8080, enter the following command:
The required version for Connect with dYdX v7 is v1.0.13.
First, please ensure you’ve received your API keys for the relevant decentralized provider nodes. If you have not received API keys, please reach out to the provider team in the relevant communication channels.
Next, place your API keys under their corresponding URLs in the following file and save it to your system. Keep the file path handy as we will pass it into a flag when running Connect.
We will also supply an edited configuration for the dydx_migration_api which facilitates graceful migration from dydx’s x/prices to x/marketmap.
For the dydx_migration_api provider, make sure to fill in the URL for the REST endpoint and gRPC endpoint of your node (in that order). The migration API will not work unless the REST API endpoint is the first endpoint in the endpoints list.
The required version for Connect with dYdX v6 is v1.0.13.
First, please ensure you’ve received your API keys for the relevant decentralized provider nodes. If you have not received API keys, please reach out to the provider team in the relevant communication channels.
Next, place your API keys under their corresponding URLs in the following file and save it to your system. Keep the file path handy as we will pass it into a flag when running Connect.
We will also supply an edited configuration for the dydx_migration_api which facilitates graceful migration from dydx’s x/prices to x/marketmap.
For the dydx_migration_api provider, make sure to fill in the URL for the REST endpoint and gRPC endpoint of your node (in that order). The migration API will not work unless the REST API endpoint is the first endpoint in the endpoints list.
The required version for Connect with dYdX v5 is v1.0.5.
First, please ensure you’ve received your API keys for Raydium markets. If you have not received API keys, please reach out to the team in the relevant channels.
Next, place your API keys under their corresponding URLs in the following file and save it to your system. Keep the file path handy as we will pass it into a flag when running Connect.
The required version for Connect with Stargaze is v1.0.12.
You need to configure a custom API endpoint for use with the Osmosis provider, https://rest.osmosis-1.interchain-apis.com.
Set the following oracle.json configuration file. Keep the file path handy as we will pass it into a flag when running Connect.
In order for the application to get prices from Connect, we need to add the following lines under the [oracle] heading in the app.toml.
Remember to change the oracle_address value to the address of your Connect sidecar.
app.toml
Copy
Ask AI
# ... other sections[oracle]enabled = "true" # if you are not running a full node, set this to "false"oracle_address = "<YOUR_CONNECT_SIDECAR>:8080"client_timeout = "250ms"metrics_enabled = "true"interval = "1500ms"price_ttl = "10s"
Once your app.toml is configured, you may start your node as normal.
Using a remote signer? Have a distributed validator setup? Check out the advanced setups to learn how to properly configure your validator infrastructure.
