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
Did you search for an existing issue or pull request?
Description
Substrate Sdk are often facing difficulties decode a historical block, especially when polkadot dependencies upgrade and chainTypes changes.
With fixed chainTypes require user republish their project, and might reindex on the subquery network.
sdk could load chainTypes dynamiclly, so with chainType changes no need to create new deplpyment.
Reduce the chance of deployment break with change of different version sdk.
Details
These details can help to reproduce the environment the issue is occurring
Local Environment: [You can get this information from executing subql version.] Query Version: [What is the version of the query service?] Indexer Version: [What is the version of the indexer service?] Network Details:
[Network]
[Block height, a block height where the issue is happening]
[Dictionary endpoint, if used]
Steps to Reproduce
[First Step]
[Second Step]
[and so on...]
Example project: [A link to a minimal example that can reproduce the issue]
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Any other information
Is there any other information you would like to add?
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
Substrate Sdk are often facing difficulties decode a historical block, especially when polkadot dependencies upgrade and chainTypes changes.
With fixed chainTypes require user republish their project, and might reindex on the subquery network.
We propose to include a remote chainTypes registry, similar to https://github.com/polkadot-js/apps/tree/e9103aa8096bde20ccd4397aab2265f3e338d6d3/packages/apps-config/src/api/spec, but apply with different version of polkadotjs. In this way :
Details
These details can help to reproduce the environment the issue is occurring
Local Environment: [You can get this information from executing
subql version
.]Query Version: [What is the version of the query service?]
Indexer Version: [What is the version of the indexer service?]
Network Details:
Steps to Reproduce
Example project: [A link to a minimal example that can reproduce the issue]
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Any other information
Is there any other information you would like to add?
The text was updated successfully, but these errors were encountered: