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 won't be moving to 1.11 in either context until there has been plenty of time and/or patches first. There are major changes and there are likely to be disruptive bugs. However, are we forced to update the module require for the Shanghai hardfork? Or does everything continue to work? There are several EIPs that go into effect in addition to the primary unstaking one. EIP-3855, EIP-3860, and EIP-6049?
personal namespace is deprecated: --rpc.enabledeprecatedpersonal will be needed for the simnet harness. Eventually we'll make our own transaction creator and signer tool for sending bootstrap funds around on the simnet harness.
EDIT: v1.11.5 is a required update before the Shanghai upgrade on April 12, 2023.
The text was updated successfully, but these errors were encountered:
Geth v1.11.5 was released that supports the Shanghai upgrade on April 12, 2023. This upgrade is required. As such, this will be required for v0.6.1 if not v0.6.0.
We need to test geth 1.11 (the app) for running the simnet harness, and we also need to test the imported module in our Go code.
https://github.com/ethereum/go-ethereum/releases/tag/v1.11.0
We won't be moving to 1.11 in either context until there has been plenty of time and/or patches first. There are major changes and there are likely to be disruptive bugs. However, are we forced to update the module require for the Shanghai hardfork? Or does everything continue to work? There are several EIPs that go into effect in addition to the primary unstaking one. EIP-3855, EIP-3860, and EIP-6049?
personal
namespace is deprecated:--rpc.enabledeprecatedpersonal
will be needed for the simnet harness. Eventually we'll make our own transaction creator and signer tool for sending bootstrap funds around on the simnet harness.EDIT: v1.11.5 is a required update before the Shanghai upgrade on April 12, 2023.
The text was updated successfully, but these errors were encountered: