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

consensus: add Istanbul BFT #166

Closed
wants to merge 16 commits into from

Conversation

yutelin
Copy link

@yutelin yutelin commented Aug 31, 2017

This PR is the implementation of Istanbul BFT protocol in ethereum/EIPs#650

@joelburget
Copy link
Contributor

If you could rebase to the latest geth1.6 that would be great. The merge conflicts are very easy.

I plan to test using quorum-tools on this branch.

@yutelin
Copy link
Author

yutelin commented Sep 2, 2017

@joelburget done.

@patrickmn
Copy link
Contributor

This is really great work!

Please execute the CLA which is required for merging: https://github.com/jpmorganchase/cla

@yutelin
Copy link
Author

yutelin commented Sep 8, 2017

Just done with latest rebasing and sending CLA. @patrickmn

@patrickmn
Copy link
Contributor

Received--thank you!

@markya0616 markya0616 force-pushed the feature/istanbul branch 2 times, most recently from ee4564e to c913474 Compare September 12, 2017 06:37
@@ -124,7 +124,7 @@ var (
}
NetworkIdFlag = cli.Uint64Flag{
Name: "networkid",
Usage: "Network identifier (integer, 1=Frontier, 2=Morden (disused), 3=Ropsten, 4=Rinkeby)",
Usage: "Network identifier (integer, 1=Frontier, 2=Morden (disused), 3=Ropsten, 4=Rinkeby, 5=Ottoman)",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like we might want to use another (higher) number that's less likely to cause a conflict in the future?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It depends on the upstream codebase. We submit the same code to geth, so if that gets merged, we are going to grab network id 5. If we eventually get a larger number, I think we can update it here accordingly.

@markya0616 markya0616 force-pushed the feature/istanbul branch 2 times, most recently from 2df6174 to 7c30f7c Compare September 15, 2017 07:20
@yutelin
Copy link
Author

yutelin commented Oct 12, 2017

We've created a PR review guide document.
https://github.com/getamis/quorum/wiki/PR-Review-Guide
Please see if that helps.

@joelburget joelburget force-pushed the geth1.6 branch 3 times, most recently from 587ae3b to a218568 Compare October 17, 2017 14:58
Protocol() Protocol
}

// Handler should be implemented is the consensus needs to handle and send peer's message

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo? Should "is" be "if"?

@patrickmn
Copy link
Contributor

Ok to close this?

@AUQIB92
Copy link

AUQIB92 commented Jul 17, 2019

@yutelin

please help
I m getting this error
Block sealing failed err=unauthorized
ERROR[07-17|22:08:43] Failed to decode message from payload address=0x80A13E1aa941569081c696525e38B6a65d1c8603 err="unauthorized address"

My environment

Geth
Version: 1.8.3-unstable
Git Commit: c7547381b2ea8999e423970d619835c662176790
Architecture: amd64
Network Id: 1
Go Version: go1.10.4
Operating System: linux ubuntu 16.04
GOPATH=
GOROOT=/usr/lib/go-1.10

@prd-fox
Copy link
Contributor

prd-fox commented Jul 17, 2019

@AUQIB92 please don't commit on closed issues. Please open a new issue with your problem and one of the team will look into it.

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

Successfully merging this pull request may close these issues.

9 participants