diff --git a/.github/ISSUE_TEMPLATE/new_chain_to_explorer.md b/.github/ISSUE_TEMPLATE/new_chain_to_explorer.md
index 6af0cab250..be8be8c244 100644
--- a/.github/ISSUE_TEMPLATE/new_chain_to_explorer.md
+++ b/.github/ISSUE_TEMPLATE/new_chain_to_explorer.md
@@ -9,7 +9,7 @@ assignees: ""
 **Adding a new chain to the Explorer**
 To get a new chain added to the Explorer, you will need to submit the following:
 
-1. JSON-RPC spec for Wallets **(only if [one](https://docs.walletconnect.com/2.0/advanced/rpc-reference/ethereum-rpc) doesn't already exist)**. For more information, please review the Ethereum [JSON-RPC API docs](https://ethereum.org/en/developers/docs/apis/json-rpc/).
+1. JSON-RPC spec for Wallets **(only if [one](https://docs.reown.com/advanced/multichain/rpc-reference/ethereum-rpc) doesn't already exist)**. For more information, please review the Ethereum [JSON-RPC API docs](https://ethereum.org/developers/docs/apis/json-rpc/).
    **GitHub Link**:
 2. Write a [CASA namespace spec](https://github.com/ChainAgnostic/namespaces) if not already available for this namespace.
    **GitHub Link**:
@@ -38,8 +38,8 @@ Add any other context here.
 
 **Registering a chain with the Explorer does not impact or improve the ability for wallets and dapps to support your chain.** It is simply a way for users to discover wallets and dapps that support your chain by:
 
-- Browsing the [Chains List](https://docs.walletconnect.com/advanced/multichain/chain-list)
-- Filtering results programmatically via the [Explorer API](https://docs.walletconnect.com/cloud/explorer)
+- Browsing the [Chains List](https://docs.reown.com/cloud/chains/chain-list#supported-chains)
+- Filtering results programmatically via the [Explorer API](https://docs.reown.com/cloud/explorer)
 
 **It is still up to wallets and dapps to provide concrete support for your chain once it is listed as part of the Explorer.**
 
diff --git a/.github/workflows/ci_sign_client.yml b/.github/workflows/ci_sign_client.yml
index 7c15d5a0ca..55f23ecb52 100644
--- a/.github/workflows/ci_sign_client.yml
+++ b/.github/workflows/ci_sign_client.yml
@@ -56,13 +56,5 @@ jobs:
           file: packages/sign-client/Dockerfile
           push: true
           tags: ${{ env.ECR_REGISTRY }}/${{ env.ECR_REPOSITORY }}:${{ env.IMAGE_TAG }}
-          cache-from: type=local,src=/tmp/.buildx-cache
-          cache-to: type=local,dest=/tmp/.buildx-cache-new
-
-      # Temp fix
-      # https://github.com/docker/build-push-action/issues/252
-      # https://github.com/moby/buildkit/issues/1896
-      - name: Move cache
-        run: |
-          rm -rf /tmp/.buildx-cache
-          mv /tmp/.buildx-cache-new /tmp/.buildx-cache
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
diff --git a/README.md b/README.md
index a03caa227f..fc86758d5d 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ Open protocol for connecting Wallets to Dapps - https://walletconnect.com
 To ensure all packages lint, build and test correctly, we can run the following command from the root folder:
 
 > **For tests to pass in the following command, you will need your own `TEST_PROJECT_ID` value**,
-> which will be generated for you when you set up a new project on [WalletConnect Cloud](https://cloud.walletconnect.com).
+> which will be generated for you when you set up a new project on [WalletConnect Cloud](https://dashboard.reown.com/).
 
 ```zsh
 TEST_PROJECT_ID=YOUR_PROJECT_ID npm run check