diff --git a/data-scientists/ocean.py/remote-setup.md b/data-scientists/ocean.py/remote-setup.md
index 7f458558..6d8268de 100644
--- a/data-scientists/ocean.py/remote-setup.md
+++ b/data-scientists/ocean.py/remote-setup.md
@@ -61,7 +61,7 @@ Then, hit Ctrl-C to exit the Python console.
Now, you have two EVM accounts (address & private key). Save them somewhere safe, like a local file or a password manager.
-These accounts will work on any EVM-based chain: production chains like Eth mainnet and Polygon, and testnets like Goerli and Mumbai. Here, we'll use them for Mumbai.
+These accounts will work on any EVM-based chain: production chains like Eth mainnet and Polygon, and testnets like Mumbai. Here, we'll use them for Mumbai.
### 3. Get (test) MATIC on Mumbai
diff --git a/developers/retrieve-datatoken-address.md b/developers/retrieve-datatoken-address.md
index 855ed174..7bbb94d2 100644
--- a/developers/retrieve-datatoken-address.md
+++ b/developers/retrieve-datatoken-address.md
@@ -45,7 +45,6 @@ Here are the networks and their corresponding chain IDs:
"energyweb: 246"
"moonriver: 1285"
"mainnet: 1"
-"goerli: 5"
"polygonedge: 81001"
"gaiaxtestnet: 2021000"
"alfajores: 44787"
diff --git a/developers/subgraph/README.md b/developers/subgraph/README.md
index 6d168591..f0355998 100644
--- a/developers/subgraph/README.md
+++ b/developers/subgraph/README.md
@@ -34,7 +34,6 @@ When it comes to fetching valuable information about [Data NFTs](../contracts/da
| Polygon | [Subgraph](https://v4.subgraph.polygon.oceanprotocol.com/) | [GraphiQL](https://v4.subgraph.polygon.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
| OP Mainnet(Optimism)| [Subgraph](https://v4.subgraph.optimism.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.optimism.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
| Mumbai | [Subgraph](https://v4.subgraph.mumbai.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.mumbai.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
-| Görli | [Subgraph](https://v4.subgraph.goerli.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.goerli.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
| Sepolia | [Subgraph](https://v4.subgraph.sepolia.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.sepolia.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
{% hint style="warning" %}
diff --git a/developers/subgraph/get-veocean-stats.md b/developers/subgraph/get-veocean-stats.md
index 92e61660..60259e43 100644
--- a/developers/subgraph/get-veocean-stats.md
+++ b/developers/subgraph/get-veocean-stats.md
@@ -9,7 +9,7 @@ If you are already familiarized with veOCEAN, you're off to a great start. Howev
On this page, you'll find a few examples to fetch the stats of veOCEANS from the Ocean Subgraph. These examples serve as a valuable starting point to help you retrieve essential information about veOCEAN. However, if you're eager to delve deeper into the topic, we invite you to visit the [GitHub](https://github.com/oceanprotocol/ocean-subgraph/blob/main/test/integration/VeOcean.test.ts) repository. There, you'll discover a wealth of additional examples, which provide comprehensive insights. Feel free to explore and expand your knowledge! :books:
{% hint style="info" %}
-The veOCEAN is deployed on the Ethereum mainnet, along with two test networks, namely Mumbai and Goerli. The statistical data available is specifically limited to these networks.
+The veOCEAN is deployed on the Ethereum mainnet, along with two test networks. The statistical data available is specifically limited to these networks.
{% endhint %}
###
diff --git a/discover/networks/README.md b/discover/networks/README.md
index bbf9231e..0c718909 100644
--- a/discover/networks/README.md
+++ b/discover/networks/README.md
@@ -149,19 +149,6 @@ This is the chain for [Energy Web Foundation](https://www.energyweb.org/).
Unlike production networks, tokens on test networks do not hold real economic value.
-### Görli
-
-
-
-**Wallet.** To connect with e.g. MetaMask, click on the network name dropdown and select _Goerli_ from the list of available networks.
### Sepolia
diff --git a/infrastructure/deploying-aquarius.md b/infrastructure/deploying-aquarius.md
index dbf45db4..c7793b92 100644
--- a/infrastructure/deploying-aquarius.md
+++ b/infrastructure/deploying-aquarius.md
@@ -286,7 +286,6 @@ Aquarius supports indexing multiple chains using a single instance to serve API
The following deployment templates could be used for guidance. Some parameters are [optional](https://github.com/oceanprotocol/aquarius) and the template could be adjusted based on these considerations. Common cases are the deployments for one/multiple Ethereum networks:
* Mainnet
-* Goerli
* Mumbai
a. Create a YAML file for Aquarius configuration.
diff --git a/infrastructure/deploying-ocean-subgraph.md b/infrastructure/deploying-ocean-subgraph.md
index afade8da..1c7fc6b6 100644
--- a/infrastructure/deploying-ocean-subgraph.md
+++ b/infrastructure/deploying-ocean-subgraph.md
@@ -479,7 +479,6 @@ Skipping bsc
Skipping energyweb
Skipping moonriver
Skipping mainnet
-Skipping goerli
Skipping polygonedge
Skipping gaiaxtestnet
Skipping alfajores
diff --git a/infrastructure/deploying-provider.md b/infrastructure/deploying-provider.md
index ac0f5431..c7c68134 100644
--- a/infrastructure/deploying-provider.md
+++ b/infrastructure/deploying-provider.md
@@ -11,7 +11,7 @@ As mentioned in the Setup a Server document, all Ocean components can be deploye
## Deploying Provider using Docker Engine and Docker Compose
-In this guide, we will deploy Provider for two chains: Goerli (Ethereum test network) and Mumbai (Polygon test network). Therefore, please note that in the following configuration files, "5" and "80001" are the chain IDs for Goerli and Mumbai respectively.
+In this guide, we will deploy Provider for Mumbai (Polygon test network). Therefore, please note that in the following configuration files, "80001" is the chain ID for Mumbai.
### Prerequisites
@@ -51,8 +51,8 @@ services:
backend:
environment:
ARTIFACTS_PATH: "/ocean-contracts/artifacts"
- NETWORK_URL: '{"5":"https://goerli.infura.io/v3/","80001":"https://polygon-mumbai.infura.io/v3/"}'
- PROVIDER_PRIVATE_KEY: '{"5":"","80001":""}'
+ PROVIDER_PRIVATE_KEY: '{"80001":"","80001":"https://polygon-mumbai.infura.io/v3/"}
+ {"80001":"https://polygon-mumbai.infura.io/v3/"}
- name: PROVIDER_PRIVATE_KEY
value: |
{"5":"","80001":""}