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

research: Investigate "commitment-based" extractors #23

Open
devloper opened this issue Aug 14, 2024 · 1 comment
Open

research: Investigate "commitment-based" extractors #23

devloper opened this issue Aug 14, 2024 · 1 comment
Labels
question Further information is requested research Asking to dive into an unknown

Comments

@devloper
Copy link

Today the extractor circuit does all parsing and extraction in a single circuit client side. This offers selective disclosure of bytes of data by parsing the JSON object and only extracting the required keys.

One possible path to improved optimization is to split the problem into two problems one client side and one server side. Instead of parsing on the client, can we commit the data into a structure in which the user can identify the fields they want to reveal without fully parsing the object?

It's possible that these two problems are synonymous and there is not optimization to be gained.

@devloper devloper added this to the EXTRACTOR P R O O F milestone Aug 14, 2024
@devloper devloper changed the title research: Investigate "commitment" oriented extractors research: Investigate "commitment-based" extractors Aug 14, 2024
@Autoparallel Autoparallel added question Further information is requested research Asking to dive into an unknown labels Aug 15, 2024
@Autoparallel
Copy link
Contributor

@devloper thoughts on this at this point? Tempted to close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested research Asking to dive into an unknown
Projects
None yet
Development

No branches or pull requests

2 participants