Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load polkadot chainTypes from remote registry #2401

Open
3 tasks
jiqiang90 opened this issue May 10, 2024 · 0 comments
Open
3 tasks

Load polkadot chainTypes from remote registry #2401

jiqiang90 opened this issue May 10, 2024 · 0 comments

Comments

@jiqiang90
Copy link
Contributor

Prerequisites

  • Are you running the latest version(s)?
  • Have you searched the documentation for your issue?
  • 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.

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 :

  1. sdk could load chainTypes dynamiclly, so with chainType changes no need to create new deplpyment.
  2. 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

  1. [First Step]
  2. [Second Step]
  3. [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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant