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

About supporting Raft consensus #28

Open
shiqinfeng1 opened this issue May 8, 2020 · 2 comments
Open

About supporting Raft consensus #28

shiqinfeng1 opened this issue May 8, 2020 · 2 comments

Comments

@shiqinfeng1
Copy link

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?

@benediamond
Copy link
Collaborator

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.

@shiqinfeng1
Copy link
Author

shiqinfeng1 commented May 25, 2020

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!

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

No branches or pull requests

2 participants