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
the constant is consensus critical, so any tx or node that has a different value will have different blob share commitments and different data roots
therefore its safe to panic if a negative value is used, although I don't think we need to add if statements that check for this everywhere given its consensus critical
Summary of Bug
Found by fuzzing in less than 2 minutes and even on CI/CD per https://github.com/celestiaorg/go-square/actions/runs/11515786009/job/32057128298?pr=119, we have a divide by zero at
go-square/inclusion/blob_share_commitment_rules.go
Line 84 in f0bf090
or simply
Please define what happens when we have a subtreeRootThreshold=0
Version
f0bf090
Steps to Reproduce
Please see above.
Kindly cc-ing @cristaloleg @walldiss @Wondertan
For Admin Use
The text was updated successfully, but these errors were encountered: