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: docs/indexer/build/datasource-processors/introduction.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# Intrtoduction
1
+
# Introduction
2
2
3
3
Many blockchains have different VMs or runtimes that allow execution of smart contracts. Some of these are wide spread such as EVM, while others are more niche such as WASM. To make it easier to index these runtimes we have created a number of datasource processors that can be used in your SubQuery project.
4
4
These processors make it easier to filter and extract the data from these runtimes.
5
5
6
6
We have a number of processors available in the [datasource-processors repository](https://github.com/subquery/datasource-processors). There is specific documentation for the following processors:
7
-
*[Substrate EVM]('./substrate-evm.md') - Also know as Frontier EVM
8
-
*[Substrate Wasm]('./substrate-wasm.md')
9
-
*[Cosmos EVM]('./cosmos-evm.md')
7
+
*[Substrate EVM](./substrate-evm.md) - Also known as Frontier EVM
8
+
*[Substrate Wasm](./substrate-wasm.md)
9
+
*[Cosmos EVM](./cosmos-evm.md)
10
10
11
11
::: note
12
12
These processors are good when you need data from within the runtime as well as data from the base chain. If you just need EVM data you can use the Ethereum SDK for more features, better performance and easier development.
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/concordium.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Concordium Manifest File
2
2
3
-
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Algorand, please refer to the [toplevel manifest documentation](../introduction.md) for more general details.
3
+
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. The following details are for Concordium, please refer to the [top-level manifest documentation](../introduction.md) for more general details.
4
4
5
5
Below is a standard example of a basic Concordium `project.ts`.
6
6
@@ -130,10 +130,10 @@ The following table explains filters supported by different handlers.
`type` is type of transaction, transaction event, or special event to filter by (case sensitive). The `values` filter is a map where the keys correspond to the keys found in a transaction, transaction event, or special event. This filter allows you to search for transactions or events that have specific values for these keys. The `values` filter matches the keys in the filter against the keys in the data object. If a match is found, the corresponding transaction, event, or special event is included in the query result. For example:
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/cosmos.md
+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
@@ -11,7 +11,7 @@ import {
11
11
CosmosProject,
12
12
} from"@subql/types-cosmos";
13
13
14
-
// Can expand the Datasource processor types via the genreic param
14
+
// Can expand the Datasource processor types via the generic param
15
15
const project:CosmosProject= {
16
16
specVersion: "1.0.0",
17
17
version: "0.0.1",
@@ -145,7 +145,7 @@ dataSources:
145
145
146
146
:::
147
147
148
-
###Tested and Supported networks
148
+
## Tested and Supported networks
149
149
150
150
We expect that SubQuery will work with all Ethermint and CosmWasm Cosmos chains with the import of the correct protobuf definitions. We have tested this with the [chains in the cosmos-subql-starter repository](https://github.com/subquery/cosmos-subql-starter). However, please feel free to make a pull request to non-supported chains when you are able to test and confirm them.
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/ethereum.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# EVM Manifest File
2
-
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Algorand, please refer to the [top level manifest documentation](../introduction.md) for more general details.
2
+
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Ethereum and other EVM-compatible chains, please refer to the [top level manifest documentation](../introduction.md) for more general details.
3
3
4
4
Below is a standard example of a basic EVM `project.ts`.
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/near.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# NEAR Manifest File
2
2
3
-
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Algorand, please refer to the [top level manifest documentation](../introduction.md) for more general details.
3
+
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for NEAR, please refer to the [top level manifest documentation](../introduction.md) for more general details.
4
4
5
5
Below is a standard example of a basic Near `project.ts`.
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/polkadot.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Polkadot/Substrate Manifest File
2
2
3
-
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Algorand, please refer to the [top level manifest documentation](../introduction.md) for more general details.
3
+
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the Polkadot chain data. Please refer to the [top level manifest documentation](../introduction.md) for more general details.
4
4
5
5
Below is a standard example of a basic Polkadot `project.ts`.
6
6
@@ -11,7 +11,7 @@ import {
11
11
SubstrateProject,
12
12
} from"@subql/types";
13
13
14
-
// Can expand the Datasource processor types via the genreic param
14
+
// Can expand the Datasource processor types via the generic param
You can see the suggested method for connecting and retrieving custom chain types in [SubQuery's Official Dictionary repository](https://github.com/subquery/subql-dictionary). Here you will find a dictionary project for each network with all the chain types correct inserted. We retrieve these definitions from the [official Polkadot.js repo](https://github.com/polkadot-js/apps/tree/master/packages/apps-config/src/api/spec), where each network lists their their chaintypes.
252
252
253
-
For example, Acala publish an [offical chain type definition to NPM](https://www.npmjs.com/package/@acala-network/type-definitions). This is imported in your project's `package.json` like so:
253
+
For example, Acala publish an [official chain type definition to NPM](https://www.npmjs.com/package/@acala-network/type-definitions). This is imported in your project's `package.json` like so:
254
254
255
255
```json
256
256
{
@@ -319,12 +319,12 @@ To enable this feature, you must ensure that your project has the [--unfinalized
319
319
320
320
Custom Data Sources provide network specific functionality that makes dealing with data easier. They act as a middleware that can provide extra filtering and data transformation.
321
321
322
-
A good example of this is EVM support, having a custom data source processor for EVM means that you can filter at the EVM level (e.g. filter contract methods or logs) and data is transformed into structures farmiliar to the Ethereum ecosystem as well as parsing parameters with ABIs.
322
+
A good example of this is EVM support, having a custom data source processor for EVM means that you can filter at the EVM level (e.g. filter contract methods or logs) and data is transformed into structures familiar to the Ethereum ecosystem as well as parsing parameters with ABIs.
323
323
324
324
Custom Data Sources can be used with normal data sources.
| [substrate/FrontierEvm](../../datasource-processors/substrate-evm.md) | [substrate/FrontierEvmEvent](../../datasource-processors/substrate-evm#event-handlers), [substrate/FrontierEvmCall](../../dataspirce-processors/substrate-evm#call-handlers) | See filters under each handlers | Provides easy interaction with EVM transactions and events on the Frontier EVM (widely used across Polkadot including in Moonbeam and Astar networks) |
330
+
| [substrate/FrontierEvm](../../datasource-processors/substrate-evm.md) | [substrate/FrontierEvmEvent](../../datasource-processors/substrate-evm#event-handlers), [substrate/FrontierEvmCall](../../datasource-processors/substrate-evm#call-handlers) | See filters under each handlers | Provides easy interaction with EVM transactions and events on the Frontier EVM (widely used across Polkadot including in Moonbeam and Astar networks) |
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/solana.md
+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
@@ -1,6 +1,6 @@
1
1
# Solana Manifest File
2
2
3
-
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Algorand, please refer to the [top level manifest documentation](../introduction.md) for more general details.
3
+
The Manifest `project.ts` file can be seen as an entry point of your project and it defines most of the details on how SubQuery will index and transform the chain data. This is the specific details for Solana, please refer to the [top level manifest documentation](../introduction.md) for more general details.
4
4
5
5
Below is a standard example of a basic Solana `project.ts`.
6
6
@@ -11,7 +11,7 @@ import {
11
11
SolanaProject,
12
12
} from"@subql/types-solana";
13
13
14
-
// Can expand the Datasource processor types via the genreic param
14
+
// Can expand the Datasource processor types via the generic param
Copy file name to clipboardExpand all lines: docs/indexer/build/manifest/chain-specific/starknet.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,6 +161,7 @@ Defines the data that will be filtered and extracted and the location of the map
161
161
| **endBlock** | Integer | This sets a end block for processing on the datasource. After this block is processed, this datasource will no longer index your data. <br><br>Useful when your contracts change at a certain block height, or when you want to insert data at genesis. For example, setting both the `startBlock` and `endBlock` to 320, will mean this datasource only operates on block 320 |
162
162
| **mapping** | Mapping Spec | |
163
163
| **options** | { abi: string; address: string; } | The name of the abi in assets to use for decoding data and an address for the contract to filter |
164
+
164
165
| **assets** | Map<string, { file: string }> | A map of contract names to abi file paths |
0 commit comments