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

Absorb https://github.com/ordian/kuddelmuddel #64

Open
sandreim opened this issue Aug 3, 2022 · 2 comments
Open

Absorb https://github.com/ordian/kuddelmuddel #64

sandreim opened this issue Aug 3, 2022 · 2 comments
Labels

Comments

@sandreim
Copy link
Collaborator

sandreim commented Aug 3, 2022

AFAIK we have to options:

  • continue to use subscan and actually implement some infrastructure so we can use it in other tools
  • switch to subxt and implement similar subscan functionality we need
@sandreim
Copy link
Collaborator Author

A really neat PoV runner has been implemented in that repo, but before we can move that here we need to tackle paritytech/polkadot-sdk#777 so we don't bloat the build here.

@ordian
Copy link
Member

ordian commented Sep 16, 2022

I'm not sure it's a good idea for polkadot-introspector to copy the design of kuddelmuddel.

A design decision of kuddelmuddel is to rely on centralized sources of data in order to be able to collect information about the past.

For example, subscan indexes all events in the past for many networks. In polkadot-introspector you collect the events only from the moment it starts. RPC nodes do not index that data. Another example is PoV storage.

For PVF executor, maybe it's better to add it to the polkadot directly as a cli command as @pepyakin suggested.

@AndreiEres AndreiEres added stale and removed stale labels Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants