oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-01 07:45:40 +01:00
Code Releases Activity

RemovignGoerli from the docs

Browse Source
This commit is contained in:
Jamie Hewitt 2024-05-21 15:53:37 +03:00
parent 695d8ad802
commit f3eb1e4347
8 changed files with 7 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
data-scientists/ocean.py/remote-setup.md
View File

@ -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

1
developers/retrieve-datatoken-address.md
View File

@ -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"

1
developers/subgraph/README.md
View File

@ -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" %}

2
developers/subgraph/get-veocean-stats.md
View File

@ -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 %}
###

13
discover/networks/README.md
View File

@ -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
<table>
<tbody>
<tr><td>Native token</td></td><td>Görli (fake) ETH</td></tr>
<tr><td>Native token faucet</td><td><a href="https://goerlifaucet.com/">Here</a></td></tr>
<tr><td>OCEAN address</td><td><a href="https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a">0xCfDdA22C9837aE76E0faA845354f33C62E03653a</a></td></tr>
<tr><td>OCEAN faucet</td><td><a href="https://faucet.goerli.oceanprotocol.com">Here</a></td></tr>
<tr><td>Explorer</td><td><a href="https://goerli.etherscan.io"</a></td></tr>
</tbody>
</table>
**Wallet.** To connect with e.g. MetaMask, click on the network name dropdown and select _Goerli_ from the list of available networks.
### Sepolia

1
infrastructure/deploying-aquarius.md
View File

@ -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.

1
infrastructure/deploying-ocean-subgraph.md
View File

@ -479,7 +479,6 @@ Skipping bsc
Skipping energyweb
Skipping moonriver
Skipping mainnet
Skipping goerli
Skipping polygonedge
Skipping gaiaxtestnet
Skipping alfajores

10
infrastructure/deploying-provider.md
View File

@ -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/<your INFURA project id>","80001":"https://polygon-mumbai.infura.io/v3/<your INFURA project id>"}'
PROVIDER_PRIVATE_KEY: '{"5":"<your private key>","80001":"<your private key"}'
NETWORK_URL: '{"80001":"https://polygon-mumbai.infura.io/v3/<your INFURA project id>"}'
PROVIDER_PRIVATE_KEY: '{"80001":"<your private key"}'
LOG_LEVEL: DEBUG
OCEAN_PROVIDER_URL: 'http://0.0.0.0:8030'
OCEAN_PROVIDER_WORKERS: "1"
@ -190,7 +190,7 @@ $ docker logs --follow provider
## Deploying Provider using Kubernetes with Docker Engine
In this example, we will run Provider as a Kubernetes deployment resource. 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 example, we will run Provider as a Kubernetes deployment resource. 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
@ -245,7 +245,7 @@ spec:
value: /ocean-provider/artifacts
- name: NETWORK_URL
value: |
{"5":"https://goerli.infura.io/v3/<your INFURA project id>","80001":"https://polygon-mumbai.infura.io/v3/<your INFURA project id>"}
{"80001":"https://polygon-mumbai.infura.io/v3/<your INFURA project id>"}
- name: PROVIDER_PRIVATE_KEY
value: |
{"5":"<your private key>","80001":"<your private key>"}