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

temporal fix to workaround EIP155 issue with chainid > 255 #1921

Conversation

hackmod
Copy link
Contributor

@hackmod hackmod commented Jun 23, 2018

@hackmod hackmod force-pushed the ledger-eip155-chainid255 branch 3 times, most recently from 802fbfc to edebdc6 Compare June 25, 2018 09:34
@hackmod
Copy link
Contributor Author

hackmod commented Jun 25, 2018

802fbfc commit does not work with web3 at all

@gamalielhere
Copy link
Collaborator

We can't allow this, this pretty much opens up replay attack, since it is no longer using EIP155

@hackmod
Copy link
Contributor Author

hackmod commented Jun 25, 2018

@gamalielhere // thank you for your reply.

ClassicalEtherWallet already use similar method for their CLO ledger support.
EthereumCommonwealth@f1e6423#diff-6e71ea384f1daaf034cc00196569e772R216

anyway, I've separated previous PR into two commit.

  • ef32de7 use EIP155 settings for customRPC case. in this case, user can use EIP155 disabled at his own risk. (but this logic is not needed. since eip155 == false cases rawTx.chainId == 0)
  • 49d5674 temporally disable EIP155 support for chainId < 256 case (similar method for CLO with ClassicalEtherWallet)

@ghost
Copy link

ghost commented Jun 27, 2018

@hackmod ClassicEtherWallet decided to support Callisto Ledger patch for enabling their Callisto deposit. It is very dangerous for using the patch widely

@hackmod
Copy link
Contributor Author

hackmod commented Jul 29, 2018

finally, the latest ledger support EIP155 + 32bits chainid.

@hackmod hackmod closed this Jul 29, 2018
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.

2 participants