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 a general topic, there are a number of things we might want to consider when it comes to managing the risk of collusion in any multi-party system. (This need not be MPC strictly, as a TEE-based system also involves multiple parties, as Nigel Smart was so good to point out.)
Things that have come up in the discussion thus far:
Different entities with operational control seems necessary (this is the obvious one we always assume)
Different cloud platforms might mitigate the risk of the platform being an attack vector
Different implementations might mitigate the risk of supply chain attacks
There are also supplementary things, like auditing, open source code, and physical controls, all of which might be used to strengthen such a system.
It's very easy to get into irrelevant details here, so we should probably not belabour any particular point.
The text was updated successfully, but these errors were encountered:
Feature Discussion
As a general topic, there are a number of things we might want to consider when it comes to managing the risk of collusion in any multi-party system. (This need not be MPC strictly, as a TEE-based system also involves multiple parties, as Nigel Smart was so good to point out.)
Things that have come up in the discussion thus far:
There are also supplementary things, like auditing, open source code, and physical controls, all of which might be used to strengthen such a system.
It's very easy to get into irrelevant details here, so we should probably not belabour any particular point.
The text was updated successfully, but these errors were encountered: