Refactor `byte@prove` to use Range Constraints
Closed this issue · 0 comments
DavePearce commented
See also #127
Currently, byte@prove annotations generate large amounts of additional constraints. After various discussions, the conclusion is they should use range proofs. Therefore, this issue is to action that.