4 ms·
Churn is when members join and/or leave. This protocol requires a fixed set of participants to start and they must all participate for it to succeed. So If I jo
by Rhapso 12y ago
Churn is when members join and/or leave. This protocol requires a fixed set of participants to start and they must all participate for it to succeed. So If I join late, I have to wait a cycle. If I leave prematurely, the cycle fails. The more participants, the more likely this is to happen.
- onion2k 12y agoCould that be mitigated by having a fixed number of available slots for participants, with each person taking an available slot, and random data submitted for any unused slots? Anyone leaving the cycle could send the same random data as if their slot hadn't been used, and in the next cycle random data would be submitted. Obviously there's a flaw that you'd need to predetermine the number of participants and choose a number of slots higher than that, and it'd be less efficient because you'd be sending data that isn't necessary, but might be worthwhile if the benefit of the communication is great enough.
- valarauca1 12y agoNot exactly. "Neighbor nodes" have to share cryptology data with one another for verification. If you simply join a session and you inherent data from the old seat, how do you know that the data you are being handed is valid? You don't unless you rebuild the cryptology verification with your "neighbor nodes". The problem is the theory and documents kinda of just hand-waves inter-node communication as being "unconditionally secure", which in practice is difficult to obtain.