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
Describe what you want implemented
Constraint are builder structures that will allow the user to specify the circuits without using complicated method arguments where the order of the selectors isn't concise or uniform.
Describe "Why" this is needed
Currently the API is over-complicated and misleading because many gates have different implementations that are not always documented correctly or even implemented securely.
Centralizing the circuit description is a major improvement in terms of usability and security since a single implementation of the selectors will either always be correct or always be wrong, not depending on methods provided by the composer itself.
Describe alternatives you've considered
Refactoring all the functions of the composer to achieve uniformity is a viable alternative, but it will not solve the problem of the complexity of the arguments of the gates
Additional context
This improvement will facilitate future API refactoring to build the circuit using DSLs.
The text was updated successfully, but these errors were encountered:
`Constraint` will introduce a fail-safe type that can be used to
describe a circuit. It will replace any composer argument that takes the
circuit description/selector polynomials.
`Selector` will allow the user to extract specific coefficients from the
constraint representation.
Resolves#608
`Constraint` will introduce a fail-safe type that can be used to
describe a circuit. It will replace any composer argument that takes the
circuit description/selector polynomials.
Resolves#608
`Constraint` will introduce a fail-safe type that can be used to
describe a circuit. It will replace any composer argument that takes the
circuit description/selector polynomials.
Resolves#608
`Constraint` will introduce a fail-safe type that can be used to
describe a circuit. It will replace any composer argument that takes the
circuit description/selector polynomials.
Resolves#608
Describe what you want implemented
Constraint are builder structures that will allow the user to specify the circuits without using complicated method arguments where the order of the selectors isn't concise or uniform.
Describe "Why" this is needed
Currently the API is over-complicated and misleading because many gates have different implementations that are not always documented correctly or even implemented securely.
Centralizing the circuit description is a major improvement in terms of usability and security since a single implementation of the selectors will either always be correct or always be wrong, not depending on methods provided by the composer itself.
Describe alternatives you've considered
Refactoring all the functions of the composer to achieve uniformity is a viable alternative, but it will not solve the problem of the complexity of the arguments of the gates
Additional context
This improvement will facilitate future API refactoring to build the circuit using DSLs.
The text was updated successfully, but these errors were encountered: