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

Merge pull request #1441 from oceanprotocol/remove-gorli

Browse Source 
Removing Goerli from the docs
This commit is contained in:
mihaisc 2024-06-04 15:28:10 +02:00 committed by GitHub
commit 07e763121b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
9 changed files with 59 additions and 95 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -6,14 +6,14 @@ description: Remote setup for running & testing ocean.py
This setup does not use barge and uses a remote chain to do the transactions. When the network URL is specified & configured, ocean.py will use components (such as Provider, Aquarius, C2D) according to the expected blockchain. This setup does not use barge and uses a remote chain to do the transactions. When the network URL is specified & configured, ocean.py will use components (such as Provider, Aquarius, C2D) according to the expected blockchain.
Here, we do setup for Mumbai, the testnet for Polygon. It's similar for other remote chains. Here, we do setup for Sepolia. It's similar for other remote chains.
Here, we will: Here, we will:
1. Configure Networks 1. Configure Networks
2. Create two accounts - `REMOTE_TEST_PRIVATE_KEY1` and `2` 2. Create two accounts - `REMOTE_TEST_PRIVATE_KEY1` and `2`
3. Get test MATIC on Mumbai 3. Get test ETH on Sepolia
4. Get test OCEAN on Mumbai 4. Get test OCEAN on Sepolia
5. Set envvars 5. Set envvars
6. Set up Alice and Bob wallets in Python 6. Set up Alice and Bob wallets in Python
@ -32,7 +32,7 @@ In order to obtain API keys for blockchain access, follow up [this document](htt
**If you do have an Infura account** **If you do have an Infura account**
Use the full RPC URL including the base and API key, e.g. for mumbai: `https://polygon-mumbai.infura.io/v3/<API-KEY>` Use the full RPC URL including the base and API key, e.g. for sepolia: `https://sepolia.infura.io/v3/<API-KEY>`
### 2. Create EVM Accounts (One-Time) ### 2. Create EVM Accounts (One-Time)
@ -61,35 +61,32 @@ 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. 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 Sepolia. Here, we'll use them for Sepolia.
### 3. Get (test) MATIC on Mumbai ### 3. Get (test) ETH on Sepolia
We need the a network's native token to pay for transactions on the network. [ETH](https://ethereum.org/en/get-eth/) is the native token for Ethereum mainnet; [MATIC](https://polygon.technology/matic-token/) is the native token for Polygon, and [(test) MATIC](https://faucet.polygon.technology/) is the native token for Mumbai. We need the a network's native token to pay for transactions on the network. [ETH](https://ethereum.org/en/get-eth/) is the native token for Ethereum mainnet; [MATIC](https://polygon.technology/matic-token/) is the native token for Polygon, and [(test) ETH](https://www.alchemy.com/faucets/ethereum-sepolia) is the native token for Sepolia.
To get free (test) MATIC on Mumbai: To get free (test) ETH on Sepolia:
1. Go to the faucet [https://faucet.polygon.technology/](https://faucet.polygon.technology/). Ensure you've selected "Mumbai" network and "MATIC" token. 1. Go to the faucet [https://www.alchemy.com/faucets/ethereum-sepolia](https://www.alchemy.com/faucets/ethereum-sepolia). Login or create an account on Alchemy.
2. Request funds for ADDRESS1 2. Request funds for ADDRESS1
3. Request funds for ADDRESS2 3. Request funds for ADDRESS2
You can confirm receiving funds by going to the following url, and seeing your reported MATIC balance: `https://mumbai.polygonscan.com/address/<ADDRESS1 or ADDRESS2>`
### 4. Get (test) OCEAN on Mumbai ### 4. Get (test) OCEAN on Sepolia
[OCEAN](https://oceanprotocol.com/token) can be used as a data payment token, and locked into veOCEAN for Data Farming / curation. The READMEs show how to use OCEAN in both cases. [OCEAN](https://oceanprotocol.com/token) can be used as a data payment token, and locked into veOCEAN for Data Farming / curation. The READMEs show how to use OCEAN in both cases.
* OCEAN is an ERC20 token with a finite supply, rooted in Ethereum mainnet at address [`0x967da4048cD07aB37855c090aAF366e4ce1b9F48`](https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48). * (Test) OCEAN is on each testnet. Test OCEAN on Sepolia is at [`0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985`](https://sepolia.etherscan.io/address/0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985).
* OCEAN on other production chains derives from the Ethereum mainnet OCEAN. OCEAN on Polygon (mOCEAN) is at [`0x282d8efce846a88b159800bd4130ad77443fa1a1`](https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1).
* (Test) OCEAN is on each testnet. Test OCEAN on Mumbai is at [`0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8`](https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8).
To get free (test) OCEAN on Mumbai: To get free (test) OCEAN on Sepolia:
1. Go to the faucet [https://faucet.mumbai.oceanprotocol.com/](https://faucet.mumbai.oceanprotocol.com/) 1. Go to the faucet [https://faucet.sepolia.oceanprotocol.com/](https://faucet.sepolia.oceanprotocol.com/)
2. Request funds for ADDRESS1 2. Request funds for ADDRESS1
3. Request funds for ADDRESS2 3. Request funds for ADDRESS2
You can confirm receiving funds by going to the following url, and seeing your reported OCEAN balance: `https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8?a=<ADDRESS1 or ADDRESS2>` You can confirm receiving funds by going to the following url, and seeing your reported OCEAN balance: `https://sepolia.etherscan.io/address/0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985?a=<ADDRESS1 or ADDRESS2>`
### 5. Set envvars ### 5. Set envvars

2
developers/subgraph/README.md
View File

@ -33,8 +33,6 @@ When it comes to fetching valuable information about [Data NFTs](../contracts/da
| Ethereum | [Subgraph](https://v4.subgraph.mainnet.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) | | Ethereum | [Subgraph](https://v4.subgraph.mainnet.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
| Polygon | [Subgraph](https://v4.subgraph.polygon.oceanprotocol.com/) | [GraphiQL](https://v4.subgraph.polygon.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) | | 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) | | 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) | | Sepolia | [Subgraph](https://v4.subgraph.sepolia.oceanprotocol.com) | [GraphiQL](https://v4.subgraph.sepolia.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql) |
{% hint style="warning" %} {% hint style="warning" %}

8
developers/subgraph/get-datatoken-buyers.md
View File

@ -6,7 +6,7 @@ description: Query the Subgraph to see the buyers of a datatoken.
The result of the following GraphQL query returns the list of buyers for a particular datatoken. Here, `0xc22bfd40f81c4a28c809f80d05070b95a11829d9` is the address of the datatoken. The result of the following GraphQL query returns the list of buyers for a particular datatoken. Here, `0xc22bfd40f81c4a28c809f80d05070b95a11829d9` is the address of the datatoken.
_PS: In this example, the query is executed on the Ocean subgraph deployed on the **Mumbai** network. If you want to change the network, please refer to_ [_this table_](README.md#ocean-subgraph-deployments)_._ _PS: In this example, the query is executed on the Ocean subgraph deployed on the **Sepolia** network. If you want to change the network, please refer to_ [_this table_](README.md#ocean-subgraph-deployments)_._
{% tabs %} {% tabs %}
{% tab title="JavaScript" %} {% tab title="JavaScript" %}
@ -42,7 +42,7 @@ const query = `{
} }
}` }`
const network = "mumbai" const network = "sepolia"
var config = { var config = {
method: 'post', method: 'post',
url: `https://v4.subgraph.${network}.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph`, url: `https://v4.subgraph.${network}.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph`,
@ -105,7 +105,7 @@ query = """
datatoken_address datatoken_address
) )
base_url = "https://v4.subgraph.mumbai.oceanprotocol.com" base_url = "https://v4.subgraph.sepolia.oceanprotocol.com"
route = "/subgraphs/name/oceanprotocol/ocean-subgraph" route = "/subgraphs/name/oceanprotocol/ocean-subgraph"
url = base_url + route url = base_url + route
@ -127,7 +127,7 @@ python datatoken_buyers.py
{% endtab %} {% endtab %}
{% tab title="Query" %} {% tab title="Query" %}
Copy the query to fetch the list of buyers for a datatoken in the Ocean Subgraph [GraphiQL interface](https://v4.subgraph.mumbai.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph). Copy the query to fetch the list of buyers for a datatoken in the Ocean Subgraph [GraphiQL interface](https://v4.subgraph.sepolia.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph).
```graphql ```graphql

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: 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" %} {% 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 %} {% endhint %}
### ###

29
discover/networks/README.md
View File

@ -31,7 +31,6 @@ Here are the networks that Ocean is deployed to.
**Test Networks:** **Test Networks:**
- Görli - Görli
- Sepolia - Sepolia
- Mumbai
- Oasis Sapphire testnet - Oasis Sapphire testnet
- Optimism (OP) Sepolia - Optimism (OP) Sepolia
@ -149,19 +148,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. 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 ### Sepolia
@ -178,21 +164,6 @@ Unlike production networks, tokens on test networks do not hold real economic va
**Wallet.** To connect with e.g. MetaMask, select "Sepolia" from the network dropdown list(enable "Show test networks"). **Wallet.** To connect with e.g. MetaMask, select "Sepolia" from the network dropdown list(enable "Show test networks").
### Mumbai
<table>
<tbody>
<tr><td>Native token</td><td>Mumbai (fake) MATIC</td></tr>
<tr><td>Native token faucet</td><td><a href="https://faucet.matic.network/">Here</a></td></tr>
<tr><td>OCEAN address</td><td><a href="https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8">0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</a></td></tr>
<tr><td>OCEAN faucet</td><td><a href="https://faucet.mumbai.oceanprotocol.com/">Here</a></td></tr>
<tr><td>Explorer</td><td><a href="https://mumbai.polygonscan.com">https://mumbai.polygonscan.com</a></td></tr>
</tbody>
</table>
**Wallet.** To connect with e.g. MetaMask, select "Görli" from the network dropdown list. If it's not listed as a predefined network, follow [Polygon's guide](https://polygon.technology/blog/getting-started-with-metamask-on-polygon).
### Oasis Sapphire Testnet ### Oasis Sapphire Testnet
[Ocean Predictoor](../../predictoor/README.md) is deployed on Oasis Sapphire testnet. This deployment does do not currently support ocean.js, ocean.py, or Ocean Market. [Ocean Predictoor](../../predictoor/README.md) is deployed on Oasis Sapphire testnet. This deployment does do not currently support ocean.js, ocean.py, or Ocean Market.

29
infrastructure/deploying-aquarius.md
View File

@ -286,8 +286,7 @@ 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: 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 * Mainnet
* Goerli * Sepolia
* Mumbai
a. Create a YAML file for Aquarius configuration. a. Create a YAML file for Aquarius configuration.
@ -396,9 +395,9 @@ spec:
terminationGracePeriodSeconds: 30ya terminationGracePeriodSeconds: 30ya
``` ```
Example deployment for _Mumbai_ (Polygon testnet): Example deployment for Sepoia (Polygon testnet):
* [aquarius-events-mumbai-deployment.yaml](https://github.com/oceanprotocol/aquarius/blob/update-deploy-docs/deployment/aquarius-events-mumbai-deployment.yaml) (annotated) - this deployment will be responsible for indexing the block and storing the metadata published on-chain: * [aquarius-events-sepolia-deployment.yaml](https://github.com/oceanprotocol/aquarius/blob/update-deploy-docs/deployment/aquarius-events-sepolia-deployment.yaml) (annotated) - this deployment will be responsible for indexing the block and storing the metadata published on-chain:
```yaml ```yaml
apiVersion: apps/v1 apiVersion: apps/v1
@ -406,15 +405,15 @@ kind: Deployment
metadata: metadata:
annotations: annotations:
labels: labels:
app: aquarius-events-mumbai app: aquarius-events-sepolia
name: aquarius-events-mumbai name: aquarius-events-sepolia
spec: spec:
progressDeadlineSeconds: 600 progressDeadlineSeconds: 600
replicas: 1 replicas: 1
revisionHistoryLimit: 5 revisionHistoryLimit: 5
selector: selector:
matchLabels: matchLabels:
app: aquarius-events-mumbai app: aquarius-events-sepolia
strategy: strategy:
rollingUpdate: rollingUpdate:
maxSurge: 25% maxSurge: 25%
@ -424,7 +423,7 @@ spec:
metadata: metadata:
creationTimestamp: null creationTimestamp: null
labels: labels:
app: aquarius-events-mumbai app: aquarius-events-sepolia
spec: spec:
containers: containers:
- env: - env:
@ -459,9 +458,9 @@ spec:
- name: ALLOWED_PUBLISHERS - name: ALLOWED_PUBLISHERS
value: '[""]' value: '[""]'
- name: NETWORK_NAME - name: NETWORK_NAME
value: mumbai value: sepolia
- name: EVENTS_RPC - name: EVENTS_RPC
value: https://polygon-mumbai.infura.io/v3/< INFURA ID > => or another RPC service for this network value: https://polygon-sepolia.infura.io/v3/< INFURA ID > => or another RPC service for this network
- name: METADATA_UPDATE_ALL - name: METADATA_UPDATE_ALL
value: "0" value: "0"
- name: ASSET_PURGATORY_URL - name: ASSET_PURGATORY_URL
@ -474,7 +473,7 @@ spec:
value: 0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8 value: 0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8
- name: SUBGRAPH_URLS - name: SUBGRAPH_URLS
value: | value: |
{"80001": "https://v4.subgraph.mumbai.oceanprotocol.com"} => or your own deployed Ocean Subgraph service for this network {"80001": "https://v4.subgraph.sepolia.oceanprotocol.com"} => or your own deployed Ocean Subgraph service for this network
- name: BLOCKS_CHUNK_SIZE - name: BLOCKS_CHUNK_SIZE
value: "3500" value: "3500"
- name: EVENTS_HTTP - name: EVENTS_HTTP
@ -491,7 +490,7 @@ spec:
periodSeconds: 10 periodSeconds: 10
successThreshold: 1 successThreshold: 1
timeoutSeconds: 1 timeoutSeconds: 1
name: aquarius-events-mumbai name: aquarius-events-sepolia
ports: ports:
- containerPort: 5000 - containerPort: 5000
protocol: TCP protocol: TCP
@ -535,9 +534,9 @@ kubectl get pods -l app=aquarius
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
aquarius-6fd9cc975b-fxr4d 1/1 Running 0 1d aquarius-6fd9cc975b-fxr4d 1/1 Running 0 1d
kubectl get pods -l app=aquarius-events-mumbai kubectl get pods -l app=aquarius-events-sepolia
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
aquarius-events-mumbai-8748976c4-mh24n 1/1 Running 0 1d aquarius-events-sepolia-8748976c4-mh24n 1/1 Running 0 1d
``` ```
Check the logs for newly deployed Aquarius by running the following command: Check the logs for newly deployed Aquarius by running the following command:
@ -545,7 +544,7 @@ Check the logs for newly deployed Aquarius by running the following command:
```bash ```bash
$ kubectl logs aquarius-6fd9cc975b-fxr4d [--follow] $ kubectl logs aquarius-6fd9cc975b-fxr4d [--follow]
$ kubectl logs aquarius-events-mumbai-8748976c4-mh24n [--follow] $ kubectl logs aquarius-events-sepolia-8748976c4-mh24n [--follow]
``` ```
c. Create a Kubernetes service c. Create a Kubernetes service

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

@ -27,7 +27,7 @@ Ocean Subgraph is deployed on top of [graph-node](https://github.com/graphprotoc
From a terminal console, create the _/etc/docker/compose/graph-node/docker-compose.yml_ file, then copy and paste the following content to it (. Check the comments in the file and replace the fields with the specific values of your implementation. From a terminal console, create the _/etc/docker/compose/graph-node/docker-compose.yml_ file, then copy and paste the following content to it (. Check the comments in the file and replace the fields with the specific values of your implementation.
_/etc/docker/compose/graph-node/docker-compose.yml_ (annotated - example for `mumbai` network) _/etc/docker/compose/graph-node/docker-compose.yml_ (annotated - example for `sepolia` network)
```yaml ```yaml
version: '3' version: '3'
@ -48,9 +48,9 @@ services:
postgres_host: postgres-graph postgres_host: postgres-graph
postgres_user: graph-node postgres_user: graph-node
postgres_pass: < password > postgres_pass: < password >
postgres_db: mumbai postgres_db: sepolia
ipfs: 'ipfs:5001' ipfs: 'ipfs:5001'
ethereum: 'mumbai:https://polygon-mumbai.infura.io/v3/< INFURA ID >' ethereum: 'sepolia:https://sepolia.infura.io/v3/<API-KEY>'
GRAPH_LOG: info GRAPH_LOG: info
ipfs: ipfs:
image: ipfs/go-ipfs:v0.4.23 image: ipfs/go-ipfs:v0.4.23
@ -70,7 +70,7 @@ services:
environment: environment:
POSTGRES_USER: graph-node POSTGRES_USER: graph-node
POSTGRES_PASSWORD: < password > POSTGRES_PASSWORD: < password >
POSTGRES_DB: mumbai POSTGRES_DB: sepolia
volumes: volumes:
- pgdata-graph-node:/var/lib/postgresql/data - pgdata-graph-node:/var/lib/postgresql/data
volumes: volumes:
@ -196,7 +196,7 @@ It is recommended to deploy PostgreSQL as helm chart.
References: [https://github.com/bitnami/charts/tree/main/bitnami/postgresql/#installing-the-chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql/#installing-the-chart) References: [https://github.com/bitnami/charts/tree/main/bitnami/postgresql/#installing-the-chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql/#installing-the-chart)
Once PostgreSQL pods are running, a database must be created: eg. `mumbai.` Once PostgreSQL pods are running, a database must be created: eg. `sepolia.`
#### 2. Deploy IPFS #### 2. Deploy IPFS
@ -317,15 +317,15 @@ kind: Deployment
metadata: metadata:
annotations: annotations:
labels: labels:
app: mumbai-graph-node app: sepolia-graph-node
name: mumbai-graph-node name: sepolia-graph-node
spec: spec:
progressDeadlineSeconds: 600 progressDeadlineSeconds: 600
replicas: 1 replicas: 1
revisionHistoryLimit: 10 revisionHistoryLimit: 10
selector: selector:
matchLabels: matchLabels:
app: mumbai-graph-node app: sepolia-graph-node
strategy: strategy:
rollingUpdate: rollingUpdate:
maxSurge: 25% maxSurge: 25%
@ -335,7 +335,7 @@ spec:
metadata: metadata:
creationTimestamp: null creationTimestamp: null
labels: labels:
app: mumbai-graph-node app: sepolia-graph-node
spec: spec:
containers: containers:
- env: - env:
@ -350,7 +350,7 @@ spec:
- name: postgres_db - name: postgres_db
value: < postgresql database > value: < postgresql database >
- name: ethereum - name: ethereum
value: mumbai:https://polygon-mumbai.infura.io/v3/< INFURA ID> value: sepolia:https://sepolia.infura.io/v3/< INFURA ID>
- name: GRAPH_KILL_IF_UNRESPONSIVE - name: GRAPH_KILL_IF_UNRESPONSIVE
value: "true" value: "true"
image: graphprotocol/graph-node:v0.28.2 image: graphprotocol/graph-node:v0.28.2
@ -365,7 +365,7 @@ spec:
periodSeconds: 10 periodSeconds: 10
successThreshold: 1 successThreshold: 1
timeoutSeconds: 1 timeoutSeconds: 1
name: mumbai-graph-node name: sepolia-graph-node
ports: ports:
- containerPort: 8000 - containerPort: 8000
name: graphql name: graphql
@ -407,8 +407,8 @@ apiVersion: v1
kind: Service kind: Service
metadata: metadata:
labels: labels:
app: mumbai-graph-node app: sepolia-graph-node
name: mumbai-graph-node name: sepolia-graph-node
spec: spec:
clusterIP: clusterIP:
clusterIPs: clusterIPs:
@ -426,7 +426,7 @@ spec:
- name: metrics - name: metrics
port: 8040 port: 8040
selector: selector:
app: mumbai-graph-nodeyam app: sepolia-graph-nodeyam
``` ```
## Deploy Ocean Subgraph ## Deploy Ocean Subgraph
@ -460,26 +460,25 @@ npm i
#### 4. Deploy Ocean Subgraph #### 4. Deploy Ocean Subgraph
In the following example, we are deploying on Ocean Subgraph on graph-node running for `mumbai` testnet. In the following example, we are deploying on Ocean Subgraph on graph-node running for `sepolia` testnet.
Note: for `ocean-subgraph` deployment in the Kubernetes environment, both `graph-node` and `ipfs` services must be locally forwarded using `kubectl port-forward` command. Note: for `ocean-subgraph` deployment in the Kubernetes environment, both `graph-node` and `ipfs` services must be locally forwarded using `kubectl port-forward` command.
Run the following command: Run the following command:
```bash ```bash
$ npm run quickstart:mumbai $ npm run quickstart:sepolia
> ocean-subgraph@3.0.8 quickstart:mumbai > ocean-subgraph@3.0.8 quickstart:sepolia
> node ./scripts/generatenetworkssubgraphs.js mumbai && npm run codegen && npm run create:local && npm run deploy:local > node ./scripts/generatenetworkssubgraphs.js sepolia && npm run codegen && npm run create:local && npm run deploy:local
Creating subgraph.yaml for mumbai Creating subgraph.yaml for sepolia
Adding veOCEAN Adding veOCEAN
Skipping polygon Skipping polygon
Skipping bsc Skipping bsc
Skipping energyweb Skipping energyweb
Skipping moonriver Skipping moonriver
Skipping mainnet Skipping mainnet
Skipping goerli
Skipping polygonedge Skipping polygonedge
Skipping gaiaxtestnet Skipping gaiaxtestnet
Skipping alfajores 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 ## 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 Sepolia (Eth test network). Therefore, please note that in the following configuration files, "11155111" is the chain ID for Sepolia.
### Prerequisites ### Prerequisites
@ -51,8 +51,8 @@ services:
backend: backend:
environment: environment:
ARTIFACTS_PATH: "/ocean-contracts/artifacts" 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>"}' NETWORK_URL: '{"80001":"https://sepolia.infura.io/v3/<your INFURA project id>"}'
PROVIDER_PRIVATE_KEY: '{"5":"<your private key>","80001":"<your private key"}' PROVIDER_PRIVATE_KEY: '{"80001":"<your private key"}'
LOG_LEVEL: DEBUG LOG_LEVEL: DEBUG
OCEAN_PROVIDER_URL: 'http://0.0.0.0:8030' OCEAN_PROVIDER_URL: 'http://0.0.0.0:8030'
OCEAN_PROVIDER_WORKERS: "1" OCEAN_PROVIDER_WORKERS: "1"
@ -190,7 +190,7 @@ $ docker logs --follow provider
## Deploying Provider using Kubernetes with Docker Engine ## 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 Sepolia (Eth test network). Therefore, please note that in the following configuration files, "11155111" is the chain ID for Sepolia.
### Prerequisites ### Prerequisites
@ -245,7 +245,7 @@ spec:
value: /ocean-provider/artifacts value: /ocean-provider/artifacts
- name: NETWORK_URL - name: NETWORK_URL
value: | value: |
{"5":"https://goerli.infura.io/v3/<your INFURA project id>","80001":"https://polygon-mumbai.infura.io/v3/<your INFURA project id>"} {"80001":"https://sepolia.infura.io/v3/<your INFURA project id>"}
- name: PROVIDER_PRIVATE_KEY - name: PROVIDER_PRIVATE_KEY
value: | value: |
{"5":"<your private key>","80001":"<your private key>"} {"5":"<your private key>","80001":"<your private key>"}

2
user-guides/publish-data-nfts.md
View File

@ -30,7 +30,7 @@ Don't enjoy reading? Watch the video tutorial!
<figure><img src="../.gitbook/assets/market/connect-wallet.png" alt=""><figcaption><p>Connect your wallet</p></figcaption></figure> <figure><img src="../.gitbook/assets/market/connect-wallet.png" alt=""><figcaption><p>Connect your wallet</p></figcaption></figure>
In this tutorial, we will be using the Polygon Mumbai test network. In this tutorial, we will be using the Sepolia test network.
4\. Click on the Publish link on the top left corner of the page. 4\. Click on the Publish link on the top left corner of the page.