-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Parachain Onboarding | Slot Request] ParaId: 4577 #121
Comments
Hi @ArneilPaulPolican I believe Xode is already assigned to one core. Should we substitute the asignation with this chain and discard the old one ? |
Hi @al3mart, thank you for reaching out. The new Xode is based on a different codebase, so if possible, we would need to replace the existing Xode on the current core with the new version. Additionally, we would need to reset the blocks to zero to ensure the new chain starts fresh. Please let me know if this approach works for you. |
hey @ArneilPaulPolican , you need to provide the compact.compressed wasm which should be around 1.5MB ... the wasm you have provided is just too big to upload. In the wbuild folder you should be able to find this comptact.compressed file. |
Hey @hbulgarini , thanks for pointing that out. For your reference, please check the updated link below: |
The code and state have been udpated as requested for the para id 4577. Please wipe your collators DB and make sure you are starting the collators with a fresh state |
HI @hbulgarini . Our team is monitoring the logs, and we are encountering this error.
|
Just in case i have pushed the state listed in the link in the description again. |
Hi @hbulgarini, I noticed that there are still no entries listed under the parathreads for Para Id 4577. |
Just in case, we have purchased a coretime via onDemand since we couldn't proceed with buying a coretime through RegionX. The onDemand purchase was successful and verified at blocks 4,924,283–42. |
Hi @hbulgarini, we deregistered Parathread ID 4577 because we were having issues, it did not produce blocks despite the configuration. Would it be possible to register it again on your end using the following files? These files were generated based on the recommendations from our provider, Zeeve. I apologize for this, and I hope you understand.
You can also check the chain specs in this link. |
I have re-onboarded the parachain with the content provided. Please wipe your collators and resync everything from scratch. |
Parachain Name
Xode
ParaID
4577
Parachain Manager Account
5CJz4Eah6P6xWaXRZpkyAKqSk1gFzvEuswyW7xDwc1ebfr5P
Upload your Genesis State - Do not submit a compressed file.
https://github.com/Xode-DAO/xode-blockchain/releases/download/v0.1.0-beta.0/paseo4577-xode-genesis
Upload your Validation Code (genesis runtime Wasm) - Do not submit a compressed file.
https://github.com/Xode-DAO/xode-blockchain/releases/download/v0.1.0-beta.0/paseo4577-xode-wasm
The text was updated successfully, but these errors were encountered: