The dYdX Chain seems to have been stabilized with dYdX Chain Protocol v4.0.5, we advise all validators to update to it as soon as possible with the steps suggested earlier.
Posted Apr 11, 2024 - 21:41 UTC
Update
There’s a new issue that validators and other node operators ran into, with an error signature of: "invalid memory address or nil pointer dereference"
Paths for nodes on different binaries: - 4.0.2 → Nodes on v4.0.2 might want to stay on v4.0.2 until they are ready to do the resync on v4.0.4/v4.0.5. Recent snapshots using v4.0.4 are available below. If they stop their node while running on v4.0.2, there’s a chance it won’t restart: - use a recent snapshot that’s created on v4.0.4, and start running v4.0.5 on top of the snapshot - or use v4.0.5 to resync from post-upgrade height - 4.0.4 → just switch over to 4.0.5, because there’s no state change, just a mempool metric change.
The devs think they've identified the issue. Working on a remedy / recovery steps. Testing internally and a small set of external validators to confirm the fix.
The fix will be more widely available in the next couple of hours.