[$5,000] Cross Chain Indexing (SubQuery Project Composability)
Closed this issue · 0 comments
ianhe8x commented
Background
Let's start with what it is not about. This feature isn't about enabling a subql-node to index more than one chain at the same time. The job of a subql-node is always clear. Extract data from one single chain and transform & store in a database for query purposes.
Challenge
Cross-chain indexing is different in regards to the data source. It should use two or more SubQuery projects (the graphql endpoint or something else) as input, trigger a mapping function provided by a user, and eventually finish the whole indexing process for a particular business purpose.
You could implement this similar to an existing data processor like our Substrate EVM implementation.
Judging Criteria
- Does this allow a user to index two seperate SubQuery projects into one data set
- How well does your solution handle when the two projects are synced to different heights
- When indexing two parachains, does your project account for the differences between blockheights on the different parachains (due to different lease starts)
- Does your solution enable the following possible use cases
- Polkadot XCM cases like cross-chain token transfer.
- Isomeric chain bridge-like wormhole