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

Wiki Reorg: Sharding and Asynchronous Backing #4782

Closed
wants to merge 3 commits into from

Conversation

filippoweb3
Copy link
Contributor

@filippoweb3 filippoweb3 commented May 11, 2023

See this issue and this google doc for more information about the Wiki reorg.

Refine Page learn-parachains-protocol Content using https://polkadot.network/blog/polkadot-v1-0-sharding-and-economic-security

Add an explanation about asynchronous backing and diagrams explaining the difference between the current situation and async backing.

Some useful material:

@filippoweb3 filippoweb3 added the A1 - In Progress Not ready for review yet. label May 11, 2023
@filippoweb3 filippoweb3 changed the title Asynchronous Backing Wiki Reorg: Sharding and Asynchronous Backing May 11, 2023
@CrackTheCode016
Copy link
Contributor

CrackTheCode016 commented Jun 1, 2023

@filippoweb3 @DrW3RK how much detail are we looking to include here? We could go into the implications that this change will bring.

As a sidenote - maybe a page for "Future Polkadot Upgrades" could be warranted? As this is not yet implemented, but still important to highlight and cover IMO.

I have covered all main factors at a high level. The following could be considered a rough TODO on how to expand it:

TODO

  • Elaborate on contextual execution and how various contexts relate to it
  • Further define the problem of "relay_parent"(s), and reference more exact changes
  • Define the possibility of a hard fork, as block time could theoretically be reduced by a change like this on the relay chain?
  • Improve the diagram to also show before async backing

@CrackTheCode016
Copy link
Contributor

CrackTheCode016 commented Jun 2, 2023

I'm going to open a new PR which adds this new content under "Future Implementations", meaning this one can likely be closed.

Can be found here: #4871

@CrackTheCode016
Copy link
Contributor

Closed in favor of #4871

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A1 - In Progress Not ready for review yet.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants