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

Move multi-pow primitives into own crate #59

Open
JoshOrndorff opened this issue Jan 11, 2024 · 0 comments
Open

Move multi-pow primitives into own crate #59

JoshOrndorff opened this issue Jan 11, 2024 · 0 comments

Comments

@JoshOrndorff
Copy link
Collaborator

Currently if we change something about the client-side multi-pow logic (like a fork height for example) then we have to recompile the runtime too. If we split multi-pow into two crates, the runtime will only have to depend on the primitives and then the incremental re-compiles during the workshop will be client-side only and therefore faster.

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