-
Notifications
You must be signed in to change notification settings - Fork 10
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
Polkadot Release v1.5.0 migration #330
Conversation
} | ||
|
||
fn kreivo_live_genesis( | ||
fn genesis( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this produce the same genesis we used to launch the chain?
.build() | ||
} | ||
|
||
pub fn kreivo_kusama_chain_spec() -> ChainSpec { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function should return the "live chainspec" but it's using test data like the "UNIT"
token and the test_genesis
. I believe this should keep returning the same chainspec as the one registered in the relay chain.
node/src/command.rs
Outdated
@@ -94,7 +87,7 @@ macro_rules! construct_async_run { | |||
#[cfg(all(feature = "virto-runtime", not(feature = "kreivo-runtime")))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we remove this including the virto-runtime
feature?
@olanod the PR is still in draft , there are many things that will be fixed once the PR becomes active :) |
- [node/chain_spec:kreivo]: allowed dead_code on unused functions + removed useless .into() calls - [node/chain_spec:service]: comment out unused import - [runtime]: comment out unused imports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving but we should update in a followup PR the chainspec of the live chain to match the one we used to register the parachain(at least change the testnet_genesis
usage and UNIT
token)
No description provided.