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
To close#1066
One of non-deterministic pk/vk came from PubIoTable fixed commitment
length.
Previously in key-setup time there is no public io, thus PubIoTable addr
is hardcode as 16 byte -> 2 word
In prove step once setup public io, then the PubIoTable addr will be
dynamic extend to cover new public io, thus the fixed commitment are not
identical, cause transcript challenge got different.
To fixed the root cause, we pass public io size in key setup time, and
then in "prove" phase we check public io data <= public io size.
0 commit comments