change: integrate Beefy into the demo runtime and node #1098
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AmbientTea
force-pushed
the
beefy-cleaned-up
branch
7 times, most recently
from
fe890d3 to
46d98dc
Compare
AmbientTea
force-pushed
the
beefy-cleaned-up
branch
3 times, most recently
from
0c69b23 to
1fdef92
Compare
AmbientTea
force-pushed
the
beefy-cleaned-up
branch
from
1fdef92 to
05b3cdb
Compare
AmbientTea
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Integrates Beefy into our node demo node to demonstrate how it can be done.
This is a long-running work started by @Klapeyron and it depends on his changes to polkadot-sdk, which are still unmerged upstream (PR: paritytech/polkadot-sdk#8964).
I tested these changes by upgrading a local chain running our current node+runtime to the versions from this PR. The upgrade path requires a storage migration and is described in a user guide in this PR: #1116
Checklist
changelog.mdfor affected crate