-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: add new paseo runtime #3013
Conversation
…84-integrate-with-passeo
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.
So it's a fresh new runtime, right?
The paseo chain will start from block #0 with genesis state?
There are still quite many new changes containing "rococo" text. They need to be adapted, as well as the conflicts. |
Signed-off-by: Faisal Ahmed <42486737+felixfaisal@users.noreply.github.com>
…entry-parachain into p-884-integrate-with-passeo
Signed-off-by: Faisal Ahmed <42486737+felixfaisal@users.noreply.github.com>
* fix paseo chain spec * add paseo
@@ -83,6 +83,7 @@ mod constants { | |||
|
|||
pub const LITENTRY_PARA_ID: u32 = 2013; | |||
pub const ROCOCO_PARA_ID: u32 = 2106; // will be replaced by paseo | |||
pub const PASEO_PARA_ID: u32 = 2106; // will be replaced by paseo |
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.
"2106" will remain same? So once paseo is merged into dev, rococo needs to be removed immediately, right?
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.
I'm not aware about the strategy for removing rococo, So I can't really comment on that.
…o p-884-integrate-with-passeo
Co-authored-by: BillyWooo <BillyWooo@users.noreply.github.com>
This PR is ready to be reviewed, Meanwhile I will be resolving conflicts and check the CI.