Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Always treat parachain that never produced block for a significant amount of time as unlocked. #7539

Closed
xlc opened this issue Jul 24, 2023 · 4 comments · Fixed by polkadot-fellows/RFCs#14
Labels
J2-unconfirmed Issue might be valid, but it's not yet known. It should not be worked on until it is verified.

Comments

@xlc
Copy link
Contributor

xlc commented Jul 24, 2023

Right now one a parathread is promoted to parachain, it is locked and only the parachain sovereign origin can unlock it.

This can be an issue if the parachain wasm/head is broken and can never produce block. Governance is required to fix this.

Alternatively, we can just automatically unlock it if it is unable to produce block for say 7 days. Then the para manager can fix the wasm/head.

@bkchr
Copy link
Member

bkchr commented Jul 24, 2023

This should be RFC before implementing this change.

@bkchr bkchr added the J2-unconfirmed Issue might be valid, but it's not yet known. It should not be worked on until it is verified. label Jul 24, 2023
@bkchr
Copy link
Member

bkchr commented Jul 24, 2023

Sounds like a reasonable idea. However, it also makes the lock avoidable.

We also need to think on how this makes sense with the new scheduling system. (This alone puts up a lot of questions that need thinking)

@bkchr
Copy link
Member

bkchr commented Jul 24, 2023

As said in element. This is more a phylosophical question and not a technical one. From technical side it makes sense and solves the problem at hand. The technical solution also would be really easy.

@xlc
Copy link
Contributor Author

xlc commented Jul 24, 2023

Yeah. This is only a short term solution. We will need to revisit this when parathead is ready.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
J2-unconfirmed Issue might be valid, but it's not yet known. It should not be worked on until it is verified.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants