The dYdX Chain is producing blocks. We will be monitoring its operation in the upcoming hours.
Posted Jun 06, 2024 - 16:20 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jun 06, 2024 - 15:30 UTC
Scheduled
The dYdX Chain is expected to undergo a protocol upgrade that could potentially disrupt functionalities around the time of the upgrade block height: https://www.mintscan.io/dydx/block/17560000
Important validator upgrade notes: 1. Check out dYdX Sidecar setup instructions: https://docs.skip.money/slinky/integrations/dydx - NB: Make sure to configure the oracle section in your app.toml according to your setup. The oracle_address should point to and be able to access the host:port where Slinky is running (the default is localhost:8080). 2. Set up the API keys: https://docs.skip.money/slinky/validator/rpc-providers/ - If you are not already in direct contact with Polkachu, KingNodes, Lavender.five, Rhino and Helius, please consider filling in the Compliance and Collaboration form (https://forms.gle/r3tbRnP4qwSQgtDe7) to get an invite to the Slack Connect by dYdX Operations subDAO 3. Run Slinky - it's important that you run Slinky v0.4.6 or newer before the upgrade height! - Release / binaries: https://github.com/skip-mev/slinky/releases/tag/v0.4.6 - Slinky sidecar docker image: https://github.com/skip-mev/slinky/pkgs/container/slinky-sidecar/219721936?tag=v0.4.6 4. Connect your Slinky to the metrics ingestor of dYdX Operations subDAO - The sidecar metrics are exposed on port 8002 by default. - either make the port public, or whitelist the subDAO's IP 52.196.160.251 - it's also possible to set HTTP basic auth - share your metrics endpoint with the subDAO or Skip