FAQs

Yes, you can run it anywhere - but please defer to any chain-specific recommendations if there are any!

No, IPv6 is currently not supported for sidecar-node communication.

We are currently working on supporting this feature. It will be available in a future release.

No. Prices are stored in x/oracle module, and only stores the most recently posted price. However, you can use blockchain indexers or inspect past blocks to see the prices committed on previous heights.

Prices within Connect are committed on a one-block delay, since validators use the vote extensions from block n-1 to securely submit their price data for block n.

Most of the time, prices will update every single block. Price updates happen when over 2/3 of validators are correctly running the Connect sidecar.

Prices will not update on any given block if:

• The market is disabled within x/marketmap
• Less than 2/3s of validators (by stake weight) contributed to a price update. This can happen if not enough validators run Connect, or there is a massive, widespread outage across providers.

Upgrading the Connect binary can be done out of band of the chain’s binary. If you have a load balancer, CNAME, etc., in front of your sidecar you can simply start up the new version and switch out which version traffic is being directed to during live chain validation.

If you are running the Connect sidecar in a container you can shut down the container, pull the updated container image and relaunch your container to update.

If you are running the binary via systemd or other management tool, you will need to stop the process and re-launch using the newly released binary.

The node will still be able to participate in consensus without the sidecar, and will begin attaching prices to blocks once Connect is available. In the worst case, an upgrade in any of these manners will cause you to miss including vote extensions for a single block which should have no negative effects on you or the network.

No.

No, the Connect binary is very lightweight. On a 36 GB Macbook Pro M3, a Connect instance fetching 125 markets took up only 50MB of memory, and 6% of the CPU.

If you’re a validator and need help getting your infrastructure setup, head over to our Discord and let us know what chain you’re validating for in the #waiting-room channel.