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

Feature Discussion: Managing Collusion Risk #13

Open
martinthomson opened this issue Apr 7, 2022 · 0 comments
Open

Feature Discussion: Managing Collusion Risk #13

martinthomson opened this issue Apr 7, 2022 · 0 comments

Comments

@martinthomson
Copy link
Collaborator

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:

  1. Different entities with operational control seems necessary (this is the obvious one we always assume)
  2. Different cloud platforms might mitigate the risk of the platform being an attack vector
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant