Jimmy
Jimmy
> > #790 this pr addresses the UT test issue > > I already fixed one by one xD, but thanks! it will be merged for future ones. Good fix!...
close as inactive
close as expired and no longer being maintained.
close as inactive
> Now that @erikzhang pushed BLS12-381. What is the idea for integrating BLS to consensus validators signatures? This is halted for now, along with the random number. Community has concerns...
@vncoelho the problems with BLS are basically: 1. it requires trusted setup process, malicious node may block the DKG process, that is also the major reason why solutions discussed in...
@vncoelho I know what you mean, but validators will change, therefore we need to process BLS setup regularly. Indeed we can detect malicious key, but still, it is possible that...
If you think the validators updating is not a problem, then all issues are gone, we got planty of time to address all problems that may happen.......
Oh BTW, >We can even have all the committee already registered and we just filter the valid keys. After PostPersist we all know which CN are valid. This is impossible,...
> @Liaojinghui, I really do not see this an issue because it has a solution. We know nodes who signed, we can even design with a `m-to-m` scheme and not...