About supporting Raft consensus
shiqinfeng1 opened this issue · comments
Hi, there ,
Mentioned in README.md, "The reason is that Raft reports block time differently (in nanoseconds, as opposed to milliseconds), an idiosyncrasy which interferes with epoch measurements."
---- Does it mean that if the block timestamp is changed to milliseconds, can it support zether?
hi @shiqinfeng1, sorry I didn't see this earlier.
It can still support Zether (in fact, we used to run on Raft). It just requires a few things to be adjusted in the smart contracts and JS client. Since it's sort of a pain, we just decided to stick with IBFT. If you're interested I could sketch what needs to be changed. Thanks.
hi, @benediamond ,
I am not very clear about the complete process of zether's zero-knowledge proof. If you can tell me a clear modification, maybe I can change it myself. Otherwise, can you provide a modified version of the fork for reference? I think it is very helpful for people who also want to run the zether protocol on the Raft consensus. Of course, I don't want to increase your workload. Thank you!