Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

hackiest possible fix for $ETC forkid issue #11746

Closed

Conversation

meowsbits
Copy link
Contributor

@meowsbits meowsbits commented Jun 1, 2020

Please help me fix this, it probably won't even compile.
I am not a Rustacean, I do not know how to write Rust code.

This is intended to be the simplest and fastest possible (and temporary) hotfix for the production ETC issue.

Rel https://github.com/openethereum/openethereum/issues/11744

Please help me fix this, it probably won't even compile.

Signed-off-by: meows <b5c6@protonmail.com>
@vorot93
Copy link

vorot93 commented Jun 1, 2020

We should address the root cause instead of such hacky workarounds.

@vorot93 vorot93 closed this Jun 1, 2020
@meowsbits
Copy link
Contributor Author

Absolutely. But this is a critical issue that is segregating the network right now and I'm trying to get this done yesterday, and I don't think the proposed change would theoretically negatively impact any other concerns as a temporary solution.

trace!(target: "sync", "Peer {} incompatible fork id (fork id: {:#x}/{}, error: {:?})", peer_id, fork_id.hash.0, fork_id.next, reason);
return Err(DownloaderImportError::Invalid);
// 0x9007bfcc/0 <-- Ethereum Classic post-Phoenix fork (core-geth, multi-geth)
if fork_id.hash.0 == 0x9007bfcc && fork_id.next == 0 {
Copy link
Contributor Author

@meowsbits meowsbits Jun 1, 2020

Choose a reason for hiding this comment

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

This is almost certainly not the correct way to compare the desired hash. Must fix?

@sorpaas
Copy link
Collaborator

sorpaas commented Jun 1, 2020

@meowsbits Rest assured I think we've just identified the root cause.

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

Successfully merging this pull request may close these issues.

3 participants