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

Is the whole polkadot-sdk supports dynamic block durations? #3635

Closed
xlc opened this issue Mar 10, 2024 · 3 comments
Closed

Is the whole polkadot-sdk supports dynamic block durations? #3635

xlc opened this issue Mar 10, 2024 · 3 comments

Comments

@xlc
Copy link
Contributor

xlc commented Mar 10, 2024

Related: #3268

Do we know if all the pallets and all other related code in pokladot-sdk supports dynamic block durations? Otherwise we cannot say polkadot-sdk is async backing / coretime ready and it reduces the confidences of migrating an existing parachain as this could introduce security risk.

Please close this issue if the answer is a confident YES and that will be great. Otherwise we need to list out the pallets and other related tasks that needs to be done before we can say YES here.

@bkchr
Copy link
Member

bkchr commented Mar 10, 2024

Not sure why we need a second issue for this?

@xlc
Copy link
Contributor Author

xlc commented Mar 10, 2024

we maybe able to close this right now without #3268

Acala is dynamic block time ready like a year ago but not really if for example one of the OpenGov pallet we use from polkadot-sdk is not.

@bkchr
Copy link
Member

bkchr commented Mar 11, 2024

I mean for sure not all pallets are ready right now (just a guess, but probably right). I would argue that this should be added to #3268. So, that we fix these pallets directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants