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
So far, we have focused mainly types that are mainly relevant for MPC computation. However, in going through our example applications, it's becoming clear that we may want a few blockchain specific types as well. These will mainly aid in reading and writing from the MPC nodes for an application and help with keeping on-chain data in sync with what's stored by the MPC nodes.
A tenative list of types to support:
Addresses: Pretty self-explanatory.
Contract IDs: Having some form of IDs for the contracts makes sense in that the nodes will always know which contract a particular set of computations are for. Might possibly just br subsumed by the Address type
Notes: in many applications, we will want to shield basic on-chain data (amounts, addresses). As such, these won't be in an easily accessible form for the user. Common designs rely on notes that only the user has in order to prove ownership of some data in zero-knowledge. Obviously, we can't store the notes directly with the MPC nodes.
The text was updated successfully, but these errors were encountered:
Yup, this is a good idea. Probably helpful to have a look at other rust libraries to get an inspiration for all the types which might be interesting in blockchain context.
So far, we have focused mainly types that are mainly relevant for MPC computation. However, in going through our example applications, it's becoming clear that we may want a few blockchain specific types as well. These will mainly aid in reading and writing from the MPC nodes for an application and help with keeping on-chain data in sync with what's stored by the MPC nodes.
A tenative list of types to support:
The text was updated successfully, but these errors were encountered: