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
As for testing, we can have the initialization handle much of the repetitive boilerplate. Afterward, there may be room for a macro to easily define tests, especially MPC-specific macros that often store keys locally using a call ID, and that call ID needs to be funneled into the next job (e.g., keygen -> signing) in order to retrieve data from the local store.
The text was updated successfully, but these errors were encountered:
I would rather build this as a custom MPC context @tbraun96, we shouldn't add too many things directly on the env.
tbraun96
changed the title
[TASK] MPC refactor: gadget_sdk::mpc module and test-utils::mpc module
[TASK] MPC refactor: add common functions to context derive
Nov 22, 2024
Now that we've built multiple MPCs, duplicated code can be abstracted away inside the SDK and test utils.
Various MPC-related functions could be added as auto-generated context functions
e.g.,
As for testing, we can have the initialization handle much of the repetitive boilerplate. Afterward, there may be room for a macro to easily define tests, especially MPC-specific macros that often store keys locally using a call ID, and that call ID needs to be funneled into the next job (e.g., keygen -> signing) in order to retrieve data from the local store.
The text was updated successfully, but these errors were encountered: