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

chore: update max block weight comment #774

Merged
merged 1 commit into from
Nov 16, 2022

Conversation

gregdhill
Copy link
Member

Signed-off-by: Gregory Hill gregorydhill@outlook.com

I found the following definition on the maximum block weight here:

Maximum Block Weight

The maximum block weight should be equivalent to one-third of the target block time, allocating one third for block construction, one third for network propagation, and one third for import and verification.

We can see that polkadot does allow for 2 seconds of compute time here:

MAXIMUM_BLOCK_WEIGHT = WEIGHT_PER_SECOND * 2

However, it would seem most parachains (including statemine & statemint) are limited to 0.5 seconds of compute time (for example). The only reference I can find to this limitation is the "asynchronous backing" tracking issue:

This implicitly creates a requirement for a parachain block to be authored, submitted to relay-chain validators, executed, and backed all within a 6-second window. Practically, this leaves only around 0.5 seconds for the collator to author a block, which is not enough time to include a meaningful amount of transactions.

Signed-off-by: Gregory Hill <gregorydhill@outlook.com>
@sander2 sander2 merged commit 4372cd9 into interlay:master Nov 16, 2022
@sander2 sander2 added this to the Release 1.20 milestone Dec 7, 2022
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

Successfully merging this pull request may close these issues.

2 participants