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

ECIP-1060: Specify the Cliquey proof-of-authority engine. #72

Merged
merged 1 commit into from
Apr 21, 2019

Conversation

soc1c
Copy link
Contributor

@soc1c soc1c commented Apr 21, 2019

I propose to upgrade the Kotti testnet to Cliquey (a.k.a. "Clique v2") to make it more robust and prevent it from getting stuck in future.

References ethereum/EIPs#1955 goerli/eips-poa#12

@YazzyYaz YazzyYaz requested a review from kimisan April 21, 2019 11:34
@realcodywburns realcodywburns merged commit aee4aa9 into ethereumclassic:master Apr 21, 2019
@soc1c soc1c deleted the patch-2 branch April 21, 2019 12:25

For a detailed specification of the block authorization logic, please refer to EIP-225 by honoring the constants defined above. However, the following changes should be highlighted:

* Each singer is **allowed to sign any number of consecutive blocks**. The order is not fixed, but in-turn signing weighs more (**`DIFF_INTURN`**) than out-of-turn one (**`DIFF_NOTURN`**). In case an out-of-turn block is received, an **in-turn signer should continue to publish their block** to ensure the chain always prefers in-turn blocks in any case. This strategy prevents in-turn validators from being hindered from publishing their block and potential network halting.
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes! We ran into issues of offline validator nodes hindering the whole network, so allowing in-turn signer to continue seems like a blessing.

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.

None yet

3 participants