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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: