From d6d4034b5d0787e56a9933d277b6a0eff5285de3 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 3 Oct 2024 12:15:51 -0700 Subject: [PATCH 1/9] Managing --- website/pages/en/managing/_meta.js | 3 ++- .../en/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ ...a-subgraph.mdx => transfer-a-subgraph.mdx} | 23 +----------------- 3 files changed, 27 insertions(+), 23 deletions(-) create mode 100644 website/pages/en/managing/deprecate-a-subgraph.mdx rename website/pages/en/managing/{transfer-and-deprecate-a-subgraph.mdx => transfer-a-subgraph.mdx} (58%) diff --git a/website/pages/en/managing/_meta.js b/website/pages/en/managing/_meta.js index 98e3d20f9911..14fbab89118e 100644 --- a/website/pages/en/managing/_meta.js +++ b/website/pages/en/managing/_meta.js @@ -1,3 +1,4 @@ export default { - 'transfer-and-deprecate-a-subgraph': '', + 'transfer-a-subgraph': '', + 'deprecate-a-subgraph': '', } diff --git a/website/pages/en/managing/deprecate-a-subgraph.mdx b/website/pages/en/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/en/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/en/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/en/managing/transfer-a-subgraph.mdx similarity index 58% rename from website/pages/en/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/en/managing/transfer-a-subgraph.mdx index c4060284d5d9..594d1b565e51 100644 --- a/website/pages/en/managing/transfer-and-deprecate-a-subgraph.mdx +++ b/website/pages/en/managing/transfer-a-subgraph.mdx @@ -1,5 +1,5 @@ --- -title: Transfer and Deprecate a Subgraph +title: Transfer a Subgraph --- ## Transferring ownership of a subgraph @@ -42,24 +42,3 @@ To transfer ownership of a subgraph, do the following: Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea: ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png) - -## Deprecating a subgraph - -Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. - -### Step-by-Step - -To deprecate your subgraph, do the following: - -1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). -2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. -3. Your subgraph will no longer appear in searches on Graph Explorer. - -**Please note the following:** - -- The owner's wallet should call the `deprecateSubgraph` function. -- Curators will not be able to signal on the subgraph anymore. -- Curators that already signaled on the subgraph can withdraw their signal at an average share price. -- Deprecated subgraphs will show an error message. - -> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. From e0f6ed9ca60124283cc72c3013d9320ef6c92479 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 3 Oct 2024 12:23:33 -0700 Subject: [PATCH 2/9] adding page --- .../ar/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../cs/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../de/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../es/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../fr/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ha/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../hi/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../it/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ja/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ko/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../mr/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../nl/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../pl/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../pt/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ro/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ru/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../sv/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../tr/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../uk/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../ur/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../vi/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../yo/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ .../zh/managing/deprecate-a-subgraph.mdx | 24 +++++++++++++++++++ 23 files changed, 552 insertions(+) create mode 100644 website/pages/ar/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/cs/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/de/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/es/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/fr/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ha/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/hi/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/it/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ja/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ko/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/mr/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/nl/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/pl/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/pt/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ro/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ru/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/sv/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/tr/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/uk/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/ur/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/vi/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/yo/managing/deprecate-a-subgraph.mdx create mode 100644 website/pages/zh/managing/deprecate-a-subgraph.mdx diff --git a/website/pages/ar/managing/deprecate-a-subgraph.mdx b/website/pages/ar/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ar/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/cs/managing/deprecate-a-subgraph.mdx b/website/pages/cs/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/cs/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/de/managing/deprecate-a-subgraph.mdx b/website/pages/de/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/de/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/es/managing/deprecate-a-subgraph.mdx b/website/pages/es/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/es/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/fr/managing/deprecate-a-subgraph.mdx b/website/pages/fr/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/fr/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ha/managing/deprecate-a-subgraph.mdx b/website/pages/ha/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ha/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/hi/managing/deprecate-a-subgraph.mdx b/website/pages/hi/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/hi/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/it/managing/deprecate-a-subgraph.mdx b/website/pages/it/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/it/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ja/managing/deprecate-a-subgraph.mdx b/website/pages/ja/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ja/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ko/managing/deprecate-a-subgraph.mdx b/website/pages/ko/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ko/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/mr/managing/deprecate-a-subgraph.mdx b/website/pages/mr/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/mr/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/nl/managing/deprecate-a-subgraph.mdx b/website/pages/nl/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/nl/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/pl/managing/deprecate-a-subgraph.mdx b/website/pages/pl/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/pl/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/pt/managing/deprecate-a-subgraph.mdx b/website/pages/pt/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/pt/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ro/managing/deprecate-a-subgraph.mdx b/website/pages/ro/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ro/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ru/managing/deprecate-a-subgraph.mdx b/website/pages/ru/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ru/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/sv/managing/deprecate-a-subgraph.mdx b/website/pages/sv/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/sv/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/tr/managing/deprecate-a-subgraph.mdx b/website/pages/tr/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/tr/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/uk/managing/deprecate-a-subgraph.mdx b/website/pages/uk/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/uk/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/ur/managing/deprecate-a-subgraph.mdx b/website/pages/ur/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/ur/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/vi/managing/deprecate-a-subgraph.mdx b/website/pages/vi/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/vi/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/yo/managing/deprecate-a-subgraph.mdx b/website/pages/yo/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/yo/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. diff --git a/website/pages/zh/managing/deprecate-a-subgraph.mdx b/website/pages/zh/managing/deprecate-a-subgraph.mdx new file mode 100644 index 000000000000..034db6a1c8ee --- /dev/null +++ b/website/pages/zh/managing/deprecate-a-subgraph.mdx @@ -0,0 +1,24 @@ +--- +title: Deprecate a Subgraph +--- + +## Deprecating a Subgraph + +Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. + +### Step-by-Step + +To deprecate your subgraph, do the following: + +1. Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract). +2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. +3. Your subgraph will no longer appear in searches on Graph Explorer. + +**Please note the following:** + +- The owner's wallet should call the `deprecateSubgraph` function. +- Curators will not be able to signal on the subgraph anymore. +- Curators that already signaled on the subgraph can withdraw their signal at an average share price. +- Deprecated subgraphs will show an error message. + +> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively. From e42461c0e814e92c70a76ef7ba3cb6262cbba0a4 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Fri, 4 Oct 2024 12:42:32 -0700 Subject: [PATCH 3/9] redirects --- nginx.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 5c622a5541fa..487c6ea9ec6f 100644 --- a/nginx.conf +++ b/nginx.conf @@ -94,7 +94,8 @@ http { rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent; rewrite ^/docs/en/substreams/(?!index\.).+$ https://substreams.streamingfast.io permanent; rewrite ^/docs/en/firehose/(?!index\.).+$ https://firehose.streamingfast.io permanent; - + rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-and-deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/transfer-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-and-deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/deprecate-a-subgraph/ permanent; # Temporary redirects (302) rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/querying/graph-client/README/ redirect; rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/developing/graph-ts/README/ redirect; From 8883cf34927823c4b3a7f49eae9c64419097b492 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 8 Oct 2024 15:16:35 -0700 Subject: [PATCH 4/9] updated --- nginx.conf | 1 - website/pages/en/managing/deprecate-a-subgraph.mdx | 6 ++---- website/pages/en/managing/transfer-a-subgraph.mdx | 8 +++----- 3 files changed, 5 insertions(+), 10 deletions(-) diff --git a/nginx.conf b/nginx.conf index 487c6ea9ec6f..9821fce0bf42 100644 --- a/nginx.conf +++ b/nginx.conf @@ -95,7 +95,6 @@ http { rewrite ^/docs/en/substreams/(?!index\.).+$ https://substreams.streamingfast.io permanent; rewrite ^/docs/en/firehose/(?!index\.).+$ https://firehose.streamingfast.io permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-and-deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/transfer-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-and-deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/deprecate-a-subgraph/ permanent; # Temporary redirects (302) rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/querying/graph-client/README/ redirect; rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/developing/graph-ts/README/ redirect; diff --git a/website/pages/en/managing/deprecate-a-subgraph.mdx b/website/pages/en/managing/deprecate-a-subgraph.mdx index 034db6a1c8ee..79ebbab02ee9 100644 --- a/website/pages/en/managing/deprecate-a-subgraph.mdx +++ b/website/pages/en/managing/deprecate-a-subgraph.mdx @@ -2,11 +2,9 @@ title: Deprecate a Subgraph --- -## Deprecating a Subgraph - Although you cannot delete a subgraph, you can deprecate it on Graph Explorer. -### Step-by-Step +## Step-by-Step To deprecate your subgraph, do the following: @@ -14,7 +12,7 @@ To deprecate your subgraph, do the following: 2. Call `deprecateSubgraph` with your `SubgraphID` as your argument. 3. Your subgraph will no longer appear in searches on Graph Explorer. -**Please note the following:** +## Reminders - The owner's wallet should call the `deprecateSubgraph` function. - Curators will not be able to signal on the subgraph anymore. diff --git a/website/pages/en/managing/transfer-a-subgraph.mdx b/website/pages/en/managing/transfer-a-subgraph.mdx index 594d1b565e51..9d4c1bc1f2b4 100644 --- a/website/pages/en/managing/transfer-a-subgraph.mdx +++ b/website/pages/en/managing/transfer-a-subgraph.mdx @@ -2,18 +2,16 @@ title: Transfer a Subgraph --- -## Transferring ownership of a subgraph - Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network. -**Please note the following:** +## Reminders - Whoever owns the NFT controls the subgraph. - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network. - You can easily move control of a subgraph to a multi-sig. - A community member can create a subgraph on behalf of a DAO. -### View your subgraph as an NFT +## View your subgraph as an NFT To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**: @@ -27,7 +25,7 @@ Or a wallet explorer like **Rainbow.me**: https://rainbow.me/your-wallet-addres ``` -### Step-by-Step +## Step-by-Step To transfer ownership of a subgraph, do the following: From 7d4cd56f7a163b3d652f4fe8357e1f7491bb0e03 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 8 Oct 2024 16:17:22 -0700 Subject: [PATCH 5/9] fixing --- nginx.conf | 1 - 1 file changed, 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 9821fce0bf42..6a9a3e2d538a 100644 --- a/nginx.conf +++ b/nginx.conf @@ -94,7 +94,6 @@ http { rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent; rewrite ^/docs/en/substreams/(?!index\.).+$ https://substreams.streamingfast.io permanent; rewrite ^/docs/en/firehose/(?!index\.).+$ https://firehose.streamingfast.io permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-and-deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/transfer-a-subgraph/ permanent; # Temporary redirects (302) rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/querying/graph-client/README/ redirect; rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/developing/graph-ts/README/ redirect; From b812d1decb39bf85889d25c9ad897b7dd60eeb3b Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 8 Oct 2024 17:06:48 -0700 Subject: [PATCH 6/9] page rename --- .../managing/transfer-a-subgraph.mdx} | 2 +- .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 .../managing/transfer-a-subgraph.mdx} | 0 23 files changed, 1 insertion(+), 1 deletion(-) rename website/pages/{zh/managing/transfer-and-deprecate-a-subgraph.mdx => ar/managing/transfer-a-subgraph.mdx} (98%) rename website/pages/{ar/managing/transfer-and-deprecate-a-subgraph.mdx => cs/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{cs/managing/transfer-and-deprecate-a-subgraph.mdx => de/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{de/managing/transfer-and-deprecate-a-subgraph.mdx => es/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{es/managing/transfer-and-deprecate-a-subgraph.mdx => fr/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{fr/managing/transfer-and-deprecate-a-subgraph.mdx => ha/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ha/managing/transfer-and-deprecate-a-subgraph.mdx => hi/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{hi/managing/transfer-and-deprecate-a-subgraph.mdx => it/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{it/managing/transfer-and-deprecate-a-subgraph.mdx => ja/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ja/managing/transfer-and-deprecate-a-subgraph.mdx => ko/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ko/managing/transfer-and-deprecate-a-subgraph.mdx => mr/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{mr/managing/transfer-and-deprecate-a-subgraph.mdx => nl/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{nl/managing/transfer-and-deprecate-a-subgraph.mdx => pl/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{pl/managing/transfer-and-deprecate-a-subgraph.mdx => pt/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{pt/managing/transfer-and-deprecate-a-subgraph.mdx => ro/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ro/managing/transfer-and-deprecate-a-subgraph.mdx => ru/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ru/managing/transfer-and-deprecate-a-subgraph.mdx => sv/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{sv/managing/transfer-and-deprecate-a-subgraph.mdx => tr/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{tr/managing/transfer-and-deprecate-a-subgraph.mdx => uk/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{uk/managing/transfer-and-deprecate-a-subgraph.mdx => ur/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{ur/managing/transfer-and-deprecate-a-subgraph.mdx => vi/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{vi/managing/transfer-and-deprecate-a-subgraph.mdx => yo/managing/transfer-a-subgraph.mdx} (100%) rename website/pages/{yo/managing/transfer-and-deprecate-a-subgraph.mdx => zh/managing/transfer-a-subgraph.mdx} (100%) diff --git a/website/pages/zh/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ar/managing/transfer-a-subgraph.mdx similarity index 98% rename from website/pages/zh/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ar/managing/transfer-a-subgraph.mdx index c4060284d5d9..dc0a1d63936e 100644 --- a/website/pages/zh/managing/transfer-and-deprecate-a-subgraph.mdx +++ b/website/pages/ar/managing/transfer-a-subgraph.mdx @@ -1,5 +1,5 @@ --- -title: Transfer and Deprecate a Subgraph +title: Transfer a Subgraph --- ## Transferring ownership of a subgraph diff --git a/website/pages/ar/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/cs/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ar/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/cs/managing/transfer-a-subgraph.mdx diff --git a/website/pages/cs/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/de/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/cs/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/de/managing/transfer-a-subgraph.mdx diff --git a/website/pages/de/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/es/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/de/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/es/managing/transfer-a-subgraph.mdx diff --git a/website/pages/es/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/fr/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/es/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/fr/managing/transfer-a-subgraph.mdx diff --git a/website/pages/fr/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ha/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/fr/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ha/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ha/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/hi/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ha/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/hi/managing/transfer-a-subgraph.mdx diff --git a/website/pages/hi/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/it/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/hi/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/it/managing/transfer-a-subgraph.mdx diff --git a/website/pages/it/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ja/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/it/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ja/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ja/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ko/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ja/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ko/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ko/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/mr/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ko/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/mr/managing/transfer-a-subgraph.mdx diff --git a/website/pages/mr/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/nl/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/mr/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/nl/managing/transfer-a-subgraph.mdx diff --git a/website/pages/nl/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/pl/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/nl/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/pl/managing/transfer-a-subgraph.mdx diff --git a/website/pages/pl/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/pt/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/pl/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/pt/managing/transfer-a-subgraph.mdx diff --git a/website/pages/pt/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ro/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/pt/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ro/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ro/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ru/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ro/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ru/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ru/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/sv/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ru/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/sv/managing/transfer-a-subgraph.mdx diff --git a/website/pages/sv/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/tr/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/sv/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/tr/managing/transfer-a-subgraph.mdx diff --git a/website/pages/tr/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/uk/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/tr/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/uk/managing/transfer-a-subgraph.mdx diff --git a/website/pages/uk/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/ur/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/uk/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/ur/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ur/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/vi/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ur/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/vi/managing/transfer-a-subgraph.mdx diff --git a/website/pages/vi/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/yo/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/vi/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/yo/managing/transfer-a-subgraph.mdx diff --git a/website/pages/yo/managing/transfer-and-deprecate-a-subgraph.mdx b/website/pages/zh/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/yo/managing/transfer-and-deprecate-a-subgraph.mdx rename to website/pages/zh/managing/transfer-a-subgraph.mdx From c68615ecee76c0417177f104ca1bf8a9f1fa55a2 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 8 Oct 2024 17:40:33 -0700 Subject: [PATCH 7/9] updating links --- website/pages/en/developing/developer-faqs.mdx | 2 +- website/pages/en/network/developing.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/pages/en/developing/developer-faqs.mdx b/website/pages/en/developing/developer-faqs.mdx index c8906615c081..60751eec69e1 100644 --- a/website/pages/en/developing/developer-faqs.mdx +++ b/website/pages/en/developing/developer-faqs.mdx @@ -80,7 +80,7 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -It is not possible to delete subgraphs once they are created. However, you can [transfer and deprecate your subgraph](/managing/transfer-and-deprecate-a-subgraph/). +It is not possible to delete subgraphs once they are created. However, you can [transfer](/managing/transfer-a-subgraph/) and [deprecate](/managing/deprecate-a-subgraph/) your subgraph. ## Network Related diff --git a/website/pages/en/network/developing.mdx b/website/pages/en/network/developing.mdx index 81231c36ad59..ce71f6da30da 100644 --- a/website/pages/en/network/developing.mdx +++ b/website/pages/en/network/developing.mdx @@ -59,7 +59,7 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. - This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers. -- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-and-deprecate-a-subgraph/) by sending the NFT. +- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT. - Published subgraphs have associated metadata, which provides other network participants with useful context and information. ### Add Curation Signal for Indexing @@ -86,4 +86,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deprecating & Transferring Subgraphs -If you no longer need a published subgraph, you can [deprecate or transfer a subgraph](/managing/transfer-and-deprecate-a-subgraph/). Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [deprecate](/managing/deprecate-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/). From 6f14627cf8889f99d760a8f5fc41225c4b5a49d5 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 10 Oct 2024 10:09:37 -0700 Subject: [PATCH 8/9] removing redirects --- nginx.conf | 2 -- 1 file changed, 2 deletions(-) diff --git a/nginx.conf b/nginx.conf index 6a9a3e2d538a..c5b8f185f22b 100644 --- a/nginx.conf +++ b/nginx.conf @@ -90,8 +90,6 @@ http { rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/deprecating-a-subgraph/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/ permanent; rewrite ^/docs/en/substreams/(?!index\.).+$ https://substreams.streamingfast.io permanent; rewrite ^/docs/en/firehose/(?!index\.).+$ https://firehose.streamingfast.io permanent; # Temporary redirects (302) From 00a18d3245a641d78536afb30777ca7023829110 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 10 Oct 2024 11:33:57 -0700 Subject: [PATCH 9/9] caps --- website/pages/en/managing/transfer-a-subgraph.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/en/managing/transfer-a-subgraph.mdx b/website/pages/en/managing/transfer-a-subgraph.mdx index 9d4c1bc1f2b4..7a88c4c598a5 100644 --- a/website/pages/en/managing/transfer-a-subgraph.mdx +++ b/website/pages/en/managing/transfer-a-subgraph.mdx @@ -11,7 +11,7 @@ Subgraphs published to the decentralized network have an NFT minted to the addre - You can easily move control of a subgraph to a multi-sig. - A community member can create a subgraph on behalf of a DAO. -## View your subgraph as an NFT +## View Your Subgraph as an NFT To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**: