Update README with dYdX-specific instructions on our fork + rename, release publishing, and remaining work for deploying the forked sidecar (#9)

Author: hwray

README.md

@@ -95,3 +95,26 @@ We have an extensive suite of metrics available to validators and chain operator
 
 * metrics relevant to the network's (that is running the instance of slinky) performance are [here](./service/metrics/README.md)
 
+---
+
+## dYdX Fork
+
+### Slinky vs. Connect Rename
+
+* Skip renamed their repo (and code refs) from Slinky --> Connect for branding purposes. 
+* Unfortunately it is impossible to update V4 protocol to use the renamed version, as message names etc. were changed. This would cause downtime during the interval when validators have updated `v4-chain` to use the rename but have not yet updated sidecar (or vice-versa). 
+* As a result, the dYdX fork of `skip-mev/connect` has chosen to roll back to the pre-rename state, `slinky`, as the base for future development (along with backporting any essential post-rename changes to functionality).
+
+### Publishing a Release
+
+To publish a new release of the `dydxprotocol/slinky` codebase, [follow the official Go docs for Publishing A Module.](https://go.dev/doc/modules/publishing)
+
+### TODO: Sidecar Deploys
+
+* The GitHub workflows in this repo can build + deploy new images of the Slinky sidecar (along with other images for E2E testing, local testing, etc.) 
+* However, these workflows have not yet been updated for dYdX's use case. (Ex. ECR + GHCR URLs still point to Skip's accounts, still rely on Skip secrets, etc.)
+* This is not an urgent issue, unless the sidecar code itself is updated, or breaking changes are made to the format of the Market Map. 
+  * Note: Adding new fields to ex. the `metadata_json` string in Market Map, is not a breaking change (assuming these new fields are not required by the sidecar for price-fetching). 
+* **Next Steps to enable deploys for dYdX's fork of sidecar:** 
+  * Update the URLs and secrets in `build-docker.yml` to deploy to dYdX's ECR / GHCR repos. 
+  * Update `v4-chain`'s `docker-compose.yml` to pull from dYdX's repos when building the `slinky0` (sidecar) image.