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 shares are returned twice, in the Shares field and in the Proof.data field. This doubles the amount of information transmitted
the proof verification is completely disjoint from the shares itself. Proof is self contained thus user needs to remember to additionally compare returned Shares with the ones proven in proof
Expected result
some of those should probably be split into separate issues, but wanted to check if you aware of those and consider them being actual issues
Actual result
Relevant log output
No response
Is the node "stuck"? Has it stopped syncing?
No response
Notes
No response
The text was updated successfully, but these errors were encountered:
Celestia Node version
0.15
OS
Install tools
No response
Others
No response
Steps to reproduce it
Hey, when integrating Share.GetRange API I found some potential inconsistencies / inefficiencies:
Shares
field and in theProof.data
field. This doubles the amount of information transmittedExpected result
some of those should probably be split into separate issues, but wanted to check if you aware of those and consider them being actual issues
Actual result
Relevant log output
No response
Is the node "stuck"? Has it stopped syncing?
No response
Notes
No response
The text was updated successfully, but these errors were encountered: