You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently fetch networkID via the ethclient's NetworkID method, but we should consider situations in which this could break. Keeping it as an open issue for now.
The text was updated successfully, but these errors were encountered:
rauljordan
changed the title
Consider case when ChainID != NetworkID when signing transactions
Consider Case When ChainID != NetworkID When Signing Transactions
Jul 4, 2018
This should be irrelevant now that we have the beacon chain. There will be no need to have write access to a mainchain node, and no need to consider this case as we will not be signing mainchain transactions.
mdehoog
pushed a commit
to mdehoog/prysm
that referenced
this issue
Oct 4, 2022
On Ethereum Classic, ChainID != NetworkID and the following code would fail when signing the initial contract creation transaction in
vmc.go
:We currently fetch networkID via the ethclient's NetworkID method, but we should consider situations in which this could break. Keeping it as an open issue for now.
The text was updated successfully, but these errors were encountered: