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

Migration: Basilisk #41

Closed
green-jay opened this issue Apr 8, 2024 · 16 comments
Closed

Migration: Basilisk #41

green-jay opened this issue Apr 8, 2024 · 16 comments
Assignees
Labels
blocked core Support task to be completed by Paseo Core team onboard-para Onboard a new parachain to Paseo Q3 - 2024 3rd Quarter of Paseo Testnet Project Q4 - 2024 RocMigration Migration request from Rococo
Milestone

Comments

@green-jay
Copy link

green-jay commented Apr 8, 2024

Para Id in Rococo

2090

State

basilisk-mainnet-paseo.state.txt

Wasm

basilisk-mainnet-paseo.wasm.txt

Parachain Manager Account

Same as on Rococo

@green-jay green-jay added the RocMigration Migration request from Rococo label Apr 8, 2024
@educlerici-zondax educlerici-zondax added the core Support task to be completed by Paseo Core team label Apr 21, 2024
@al3mart
Copy link
Contributor

al3mart commented Apr 26, 2024

Parathread being onboarded right now

@hbulgarini
Copy link
Contributor

Hello @green-jay ! we see the parachain onboarded but not producing blocks, are the collators up and running? In case they are, do you notice any error in the logs?

@hbulgarini
Copy link
Contributor

@green-jay FYI: After some internal discussions we decided to allow Basilisk parachain temporary until the demand for cores increases. We didn't officialized yet, but the rule will be one core per parachain team in Paseo.

@green-jay
Copy link
Author

@green-jay FYI: After some internal discussions we decided to allow Basilisk parachain temporary until the demand for cores increases. We didn't officialized yet, but the rule will be one core per parachain team in Paseo.

Hi @hbulgarini, ty for making the exception. It makes sense for the canary model. But Basilisk is not the case, it is a separate parachain project with a partially different feature set and partially different group of people working on it compared to Hydra.

Collator onboarding is in the pipeline, I'll keep you updated.

@hbulgarini
Copy link
Contributor

hello @green-jay ! i saw that hydradx is producing blocks already in Paseo, i was wondering if the collators were already onboarded for this one and the block production is not working.

@green-jay
Copy link
Author

green-jay commented May 17, 2024

hello @green-jay ! i saw that hydradx is producing blocks already in Paseo, i was wondering if the collators were already onboarded for this one and the block production is not working.

hi @hbulgarini, yes our collator is producing:
[Parachain] Could not find the header of the genesis block in the database! block_hash=0x4d76327abf28e4823370821763e45fbac5525fbab30a79b0f32112ef7d607938
looks like the genesis block mismatch

@educlerici-zondax
Copy link
Contributor

hey @green-jay Just saw your last update about the genesis block mismatch – sounds like a tricky one! Have you managed to resolve that, or is there anything specific you're trying right now to sort it out? Keen to hear how it's going and if there’s any way I can help!

@educlerici-zondax educlerici-zondax added this to the Q3 - 2024 milestone Jun 3, 2024
@educlerici-zondax educlerici-zondax added the Q3 - 2024 3rd Quarter of Paseo Testnet Project label Jun 3, 2024
@educlerici-zondax
Copy link
Contributor

@green-jay any update regarding this one?

@educlerici-zondax
Copy link
Contributor

We will close this issue for now but will reopen it if there are new updates or submissions. Please feel free to add any further comments or concerns.

@mrq1911
Copy link

mrq1911 commented Jun 11, 2024

please give some slot to basilisk, so we can debug it

@al3mart
Copy link
Contributor

al3mart commented Jun 11, 2024

image

Basilisk has been slotted 🤝

@hbulgarini
Copy link
Contributor

@mrq1911 How is your debugging going? Any estimation for making the parachain to produce blocks?

@hbulgarini hbulgarini reopened this Jun 26, 2024
@educlerici-zondax educlerici-zondax added the onboard-para Onboard a new parachain to Paseo label Jun 26, 2024
@educlerici-zondax educlerici-zondax modified the milestones: Q2 - 2024, Q3 - 2024 Jul 2, 2024
@educlerici-zondax
Copy link
Contributor

@mrq1911 any update? 🙏

@hbulgarini
Copy link
Contributor

Hello @mrq1911 @green-jay, the next week we will be doing a cleanup on Paseo for parachains not producing blocks. This is the last chance in case you want to debug the parachain or otherwise we will have to offboard it.

Thanks.

@green-jay
Copy link
Author

Testing purposes only:

State:
cleanspec.state.txt

Wasm:
cleanspec.wasm.txt

@green-jay
Copy link
Author

green-jay commented Oct 31, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked core Support task to be completed by Paseo Core team onboard-para Onboard a new parachain to Paseo Q3 - 2024 3rd Quarter of Paseo Testnet Project Q4 - 2024 RocMigration Migration request from Rococo
Projects
Status: Done
Development

No branches or pull requests

5 participants