Skip to content

Commit 8799270

Browse files
Merge branch 'main' into Update-tokenomics
2 parents d8f59e4 + 56d0d0c commit 8799270

File tree

2 files changed

+18
-18
lines changed

2 files changed

+18
-18
lines changed

website/pages/en/billing.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
1414

1515
## Query Payments with credit card
1616

17-
- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
17+
- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
1818
1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
1919
2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
2020
3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
6969

7070
1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
7171
2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
72-
3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
72+
3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
7373
4. Enter the amount of GRT you would like to withdraw.
7474
5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
7575
6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
8383
- For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
8484
5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
8585
6. Select the number of months you would like to prepay.
86-
- Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
86+
- Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
8787
7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
8888
- If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
8989
8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
127127
7. Review your purchase and click "Buy GRT".
128128
8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
129129
9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
130-
- [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
130+
- [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
131131
- Click on the "wallet" button, click withdraw, and select GRT.
132132
- Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
133133
- Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
198198

199199
### How many queries will I need?
200200

201-
You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
201+
You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
202202

203203
We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
204204

@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
208208

209209
Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
210210

211-
### What happens when my billing balance runs? Will I get a warning?
211+
### What happens when my billing balance runs out? Will I get a warning?
212212

213213
You will receive several email notifications before your billing balance runs out.

website/pages/en/glossary.mdx

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ title: Glossary
1010

1111
- **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
1212

13-
- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
13+
- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
1414

15-
- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
15+
- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
1616

1717
- **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
1818

@@ -22,17 +22,17 @@ title: Glossary
2222

2323
- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
2424

25-
- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
25+
- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
2626

27-
- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
27+
- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
2828

2929
- **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
3030

31-
- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
31+
- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
3232

3333
- **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
3434

35-
- **Subgraph Consumer**: Any application or user that queries a subgraph.
35+
- **Data Consumer**: Any application or user that queries a subgraph.
3636

3737
- **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
3838

@@ -44,11 +44,11 @@ title: Glossary
4444

4545
1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
4646

47-
2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
47+
2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
4848

4949
- **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
5050

51-
- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
51+
- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
5252

5353
- **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
5454

@@ -60,11 +60,11 @@ title: Glossary
6060

6161
- **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
6262

63-
- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
63+
- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
6464

65-
- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
65+
- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
6666

67-
- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
67+
- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
6868

6969
- **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
7070

@@ -76,6 +76,6 @@ title: Glossary
7676

7777
- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
7878

79-
- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
79+
- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
8080

8181
- **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).

0 commit comments

Comments
 (0)