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
Pickles and Kimchi both support runtime tables. Runtime tables give us access to dynamic (not hard coded) values at proving time. Unlike static lookup tables (which are predefined and baked into the circuit), runtime tables allow circuits to work with data that changes per proof instance. Exposing this feature through a nice API will allow developers to build complex wrappers, data types and cirucits.
(Optional) Describe the solution
As mentioned, Pickles and Kimchi both support runtime tables. We do already have a way to configure runtime tables in o1js
However, we have no nice way (API) of populating these tables with values and passing them through to the proof system layer.
The goal is to define an API which developers can interact with to configure and populate runtime tables in their circuit as well as finish any remaining integration work in the bindings layer (TBD).
The text was updated successfully, but these errors were encountered:
Describe the feature or improvement
Pickles and Kimchi both support runtime tables. Runtime tables give us access to dynamic (not hard coded) values at proving time. Unlike static lookup tables (which are predefined and baked into the circuit), runtime tables allow circuits to work with data that changes per proof instance. Exposing this feature through a nice API will allow developers to build complex wrappers, data types and cirucits.
(Optional) Describe the solution
As mentioned, Pickles and Kimchi both support runtime tables. We do already have a way to configure runtime tables in o1js
However, we have no nice way (API) of populating these tables with values and passing them through to the proof system layer.
The goal is to define an API which developers can interact with to configure and populate runtime tables in their circuit as well as finish any remaining integration work in the bindings layer (TBD).
The text was updated successfully, but these errors were encountered: