Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make runtime tables available to o1js #2079

Closed
Trivo25 opened this issue Mar 13, 2025 · 3 comments
Closed

Make runtime tables available to o1js #2079

Trivo25 opened this issue Mar 13, 2025 · 3 comments
Assignees
Labels
feature-request Issues that specify work that is requested by others

Comments

@Trivo25
Copy link
Member

Trivo25 commented Mar 13, 2025

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

let add_runtime_table_config id first_column =
    add_gate "add_runtime_table_config" (AddRuntimeTableCfg { id; first_column })

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).

@Trivo25 Trivo25 added the feature-request Issues that specify work that is requested by others label Mar 13, 2025
@querolita querolita self-assigned this Mar 19, 2025
@Trivo25
Copy link
Member Author

Trivo25 commented Mar 20, 2025

Note: Accessing elements needs to be done via the lookup constraint

@querolita
Copy link
Member

Current PR

@querolita
Copy link
Member

Related to #1859

@Trivo25 Trivo25 closed this as completed Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Issues that specify work that is requested by others
Projects
None yet
Development

No branches or pull requests

2 participants