You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want worstCaseShareIndexes to always use the upper bound for max square size (128) so that celestia-node doesn't have to be stateful when extending the ODS.
If worstCaseShareIndexes uses the max effective square size (64) then celestia-node would have to poll celestia-app for the gov max square size every block.
Also note that celestia-app v1.x used a worstCaseShareIndexes of 128 so it was a consensus breaking change to drop down to 64.
Proposal
Modify the second argument to this function to use the upper bound of 128
The text was updated successfully, but these errors were encountered:
Context
go-square/square/builder.go
Line 414 in a841739
Problem
We want worstCaseShareIndexes to always use the upper bound for max square size (128) so that celestia-node doesn't have to be stateful when extending the ODS.
If
worstCaseShareIndexes
uses the max effective square size (64) then celestia-node would have to poll celestia-app for the gov max square size every block.Also note that celestia-app v1.x used a worstCaseShareIndexes of
128
so it was a consensus breaking change to drop down to64
.Proposal
Modify the second argument to this function to use the upper bound of
128
The text was updated successfully, but these errors were encountered: