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
At the moment verifiers do not know the size of the domain to use when verifying blobs. This can be fixed by either going fixed size (which is the ongoing conversations) or doing it dynamically (which adds extra problems and complexity but solves overload for smaller network sizes).
Size was fixed to pass the tests in logos-co/nomos-node#664 but we need to modify it and change it accordingly once we move from VID to Sampling and we decide on the static vs dynamic choice.
The text was updated successfully, but these errors were encountered:
By dynamic, do you mean that verifier function should take the row and column sizes as input based on the data size once the data is known?
Verifier receives a column so domain size can be derived from there. But it do not really know what is the row size, either we decide is fixed size hence can be statically encoded or we need to provide it somehow.
At the moment verifiers do not know the size of the domain to use when verifying blobs. This can be fixed by either going fixed size (which is the ongoing conversations) or doing it dynamically (which adds extra problems and complexity but solves overload for smaller network sizes).
Size was fixed to pass the tests in logos-co/nomos-node#664 but we need to modify it and change it accordingly once we move from VID to Sampling and we decide on the static vs dynamic choice.
The text was updated successfully, but these errors were encountered: