Replies: 3 comments 4 replies
-
Good catch - Dan and I spoke about this a little last week in reference to this story. Capping the number of parties that are voted for probably makes sense on-chain, where if you vote for over I am pretty sure that it only makes sense to vote for 50 nodes maximum, since if you're voting for more than that, you're effectively attesting tot he fact that any signature generation would be impossible, right? |
Beta Was this translation helpful? Give feedback.
-
I think |
Beta Was this translation helpful? Give feedback.
-
So I'm assuming this logic will be implemented on State Chain? (i.e. we don't need to limit the numer of nodes CFE can report?) |
Beta Was this translation helpful? Give feedback.
-
Something I've seen more than once on testnet is that nodes reported all participants (including themselves) due to a software bug. I think
N
nodes being reported in a ceremony is almost certainly a result of a bug (or possibly an exploit). If something like this happens once, there is a very good chance that it will keep happening for subsequent ceremonies until all nodes lose their funds/validator status. Perhaps we should stall the network insted in cases like this, so we could manually interfere? (Instead of stalling the network, we could retry the ceremony w/o slashing anyone.) More generally, should there be thresholdT
(say 2/3 of all nodes) such that ifT
nodes are simultaneously reported in a ceremony, we should handle this failure differently?Beta Was this translation helpful? Give feedback.
All reactions