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

Malicious node operator controlling (n - t) + 1 of the signers set can hold network to ransom #1144

Open
ameba23 opened this issue Nov 4, 2024 · 2 comments

Comments

@ameba23
Copy link
Contributor

ameba23 commented Nov 4, 2024

Since entropy-tss is run in a TDX enclave, node operators are unable to read keyshares or modify the the behaviour of entropy-tss, which mitigates many possible attacks from malicious node operators.

However, they can stop the virtual machine process of the TDX guest from running. If they control more than n - t members of the current signer set, and stop all their nodes from running, it will be impossible for the network to sign messages or do a reshare. At this point the entropy network can only continue with cooperation from the node operator.

Of course they can be slashed for this, but it may be the case that their combined stake is sufficiently smaller than the network's total value to make a ransom attack worthwhile.

@mixmix
Copy link
Contributor

mixmix commented Nov 5, 2024

is it possible to move knowledge of whether a node is an active signer to inside the enclave? I guess you could infer a lot from the network traffic still...

@ameba23
Copy link
Contributor Author

ameba23 commented Nov 5, 2024

Thats a really good idea which would help with a whole bunch of possible attacks. But it would mean deep changes to our current setup, and make public verification and slashing etc much more complicated. And yes, i think node operators could figure it out pretty easily from traffic analysis.

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

No branches or pull requests

2 participants