From 224e5f1a5ab0f3dc43ef0931fe86f83b5b4ff1be Mon Sep 17 00:00:00 2001
From: nms-7 <57442379+nms-7@users.noreply.github.com>
Date: Sun, 16 Nov 2025 08:33:12 -0500
Subject: [PATCH 1/3] Updates  README.md

---
 spot-subgraph/README.md | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/spot-subgraph/README.md b/spot-subgraph/README.md
index 12d43781..660a8458 100644
--- a/spot-subgraph/README.md
+++ b/spot-subgraph/README.md
@@ -4,7 +4,7 @@ The Graph is a tool for for indexing events emitted on the Ethereum blockchain.
 
 ```
 Public graphql endpoint:
-https://api.thegraph.com/subgraphs/name/ampleforth/spot
+https://api.goldsky.com/api/public/project_cmgzjl03n004g5np20v5j3qpx/subgraphs/ampleforth-spot/prod/gn
 ```
 
 ## Getting started
@@ -26,13 +26,24 @@ Setup project:
 yarn
 ```
 
-To build and deploy the subgraph to the graph hosted service:
+To build and deploy the subgraph to the goldsky's hosted service:
 
 ```
 # local deployment
 ./scripts/deploy-local.sh sepolia ampleforth-spot-sepolia
 
 # prod deployment
-./scripts/deploy.sh sepolia ampleforth-spot-sepolia
-./scripts/deploy.sh mainnet ampleforth-spot
-```
\ No newline at end of file
+
+You should have your own Goldsky API key to use with the Goldsky CLI.
+Note you must set the (new) version to deploy to, and then update the tag separately.
+
+```
+./scripts/deploy.sh sepolia <VERSION> ampleforth-spot-sepolia
+./scripts/deploy.sh mainnet <VERSION> ampleforth-spot
+```
+
+Once deployed, update the tag that frg-web-api looks for.
+
+```
+goldsky subgraph tag create <SUBGRAPH-NAME>/<VERSION> --tag prod
+```

From a5a2b0198606ea01ddd2fd72c0c21ccc6fe98adb Mon Sep 17 00:00:00 2001
From: nms-7 <57442379+nms-7@users.noreply.github.com>
Date: Sun, 16 Nov 2025 08:35:36 -0500
Subject: [PATCH 2/3] Update deploy.sh

---
 spot-subgraph/scripts/deploy.sh | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/spot-subgraph/scripts/deploy.sh b/spot-subgraph/scripts/deploy.sh
index 0c8bcfb8..519cd0c9 100755
--- a/spot-subgraph/scripts/deploy.sh
+++ b/spot-subgraph/scripts/deploy.sh
@@ -3,14 +3,4 @@ set -e
 
 yarn mustache ../spot-contracts/deployments/$1.json subgraph.template.yaml > ./subgraph.yaml
 
-yarn codegen
-
-yarn build
-
-echo "NOTE: graph deploy to Alchemy fails when you redeploy with the same IPFS hash"
-
-# yarn graph auth $THE_GRAPH_API_KEY
-# yarn graph deploy $2
-yarn graph deploy $2 \
-  --node https://subgraphs.alchemy.com/api/subgraphs/deploy \
-  --deploy-key $GRAPH_AUTH
+goldsky subgraph deploy $2/$3 --path .

From 459dc1c09d8ee2821458d562486ad68b76d3a5d7 Mon Sep 17 00:00:00 2001
From: nms-7 <57442379+nms-7@users.noreply.github.com>
Date: Sun, 16 Nov 2025 08:36:01 -0500
Subject: [PATCH 3/3] Update README.md

---
 spot-subgraph/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spot-subgraph/README.md b/spot-subgraph/README.md
index 660a8458..ec39daeb 100644
--- a/spot-subgraph/README.md
+++ b/spot-subgraph/README.md
@@ -38,8 +38,8 @@ You should have your own Goldsky API key to use with the Goldsky CLI.
 Note you must set the (new) version to deploy to, and then update the tag separately.
 
 ```
-./scripts/deploy.sh sepolia <VERSION> ampleforth-spot-sepolia
-./scripts/deploy.sh mainnet <VERSION> ampleforth-spot
+./scripts/deploy.sh sepolia ampleforth-spot-sepolia <VERSION>
+./scripts/deploy.sh mainnet ampleforth-spot <VERSION>
 ```
 
 Once deployed, update the tag that frg-web-api looks for.