-
Notifications
You must be signed in to change notification settings - Fork 103
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
[Guardrails] Data Collection - Block Size #1503
Comments
Analysis on how much required data can fit in a block. If using probabilistic proofs, that needs to be a variable to determine what block size can be scaled to. |
Edited to include tx bot directory link @iajrz hope that helps! |
Do we have contacts over the tendermint side who can lean in and provide implications of increasing block size.. Top of mind, obviously it would increase overhead on consensus since we're gossiping larger blocks. But any gotchas that tendermint devs have came across? |
Given that Tendermint has a 100MB block size (source), I am hopeful but need to validate. |
As part of the RC 0.10 release guide and probabilistic proof work, this work was completed. Block DataThis GitHub gist shows the block composition. Block Size ValidationThese instructions can be used to validate Block size increases locally.
|
Objective
To measure the efficacy of pocket-score scalability efforts, we should experiment with different block sizes against standard node configurations to understand the impact of increasing block size on how many transactions can be processed in a block.
Origin Document
Guardrails Projects
Guardrails Recommendations
Goal
Deliverable
Non-goals / Non-deliverables
General issue deliverables
Creator: @jessicadaugherty
The text was updated successfully, but these errors were encountered: