You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/pages/ar/arbitrum-faq.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,15 +31,15 @@ Users bridge their GRT and ETH using one of the following methods:
31
31
32
32
To take advantage of using The Graph on L2, use this dropdown switcher to toggle between chains.
33
33
34
-
{/* Insert an image */}
34
+
35
35
36
36
### As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
37
37
38
38
There is no immediate action required.
39
39
40
-
Core developer teams are working to create migration helpers that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect migration helpers to be available in April 2023.
40
+
Core developer teams are working to create migration helpers that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect migration helpers to be available soon.
41
41
42
-
The Graph community can also expect indexing rewards to be enabled on Arbitrum in February or March 2023.
42
+
As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
43
43
44
44
### If I would like to participate in the network on L2, what should I do?
Copy file name to clipboardExpand all lines: website/pages/ar/cookbook/arweave.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ The requirements for Arweave subgraphs are covered by the [existing documentatio
46
46
47
47
This is the logic that determines how data should be retrieved and stored when someone interacts with the data sources you are listening to. The data gets translated and is stored based off the schema you have listed.
48
48
49
-
أثناء تطوير الـ الرسم البياني الفرعي هناك أمران رئيسان:
49
+
أثناء تطوير الـ subgraph ، هناك أمران رئيسيان:
50
50
51
51
```
52
52
$ graph codegen # generates types from the schema file identified in the manifest
The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information.
Copy file name to clipboardExpand all lines: website/pages/ar/cookbook/cosmos.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ There are three key parts when it comes to defining a subgraph:
43
43
44
44
**AssemblyScript Mappings**: [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) code that translates from blockchain data to the entities defined in your schema.
45
45
46
-
### تعريف الفرعية رسم بياني يظهر
46
+
### تعريف Subgraph Manifest
47
47
48
48
The subgraph manifest (`subgraph.yaml`) identifies the data sources for the subgraph, the triggers of interest, and the functions (`handlers`) that should be run in response to those triggers. See below for an example subgraph manifest for a Cosmos subgraph:
49
49
@@ -81,9 +81,9 @@ dataSources:
81
81
82
82
Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graph-ql-schema).
83
83
84
-
### أسيمبلي سكريبت التعيينات
84
+
### AssemblyScript Mappings
85
85
86
-
تمت كتابة المعالجات الخاصة بمعالجة الأحداث بـ[ أسيمبلي سكريبت ](https://www.assemblyscript.org/).
86
+
تمت كتابة المعالجات(handlers) الخاصة بمعالجة الأحداث بـ[ AssemblyScript ](https://www.assemblyscript.org/).
87
87
88
88
Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/assemblyscript-api/).
In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
26
26
@@ -32,7 +32,7 @@ Building subgraphs is an essential part of The Graph, described more in depth [h
32
32
33
33
> Note: The contract used in the subgraph was taken from the following [Hackathon Starterkit](https://github.com/schmidsi/hackathon-starterkit).
34
34
35
-
## تعريف الفرعية رسم بياني يظهر
35
+
## تعريف Subgraph Manifest
36
36
37
37
The subgraph manifest `subgraph.yaml` identifies the data sources for the subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example subgraph manifest that you will use:
0 commit comments