-
Notifications
You must be signed in to change notification settings - Fork 232
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
Cannot connect to blockchain after upgrading node and plugin #177
Comments
@Julian-dev28 Could you help double check if my steps to update subnet-evm are correct? I followed the steps in the Node update document but cannot find the subnet-evm update document. Thanks! |
can you send the |
@bafu Thanks again for bringing this up I've replied on Discord when this issue was first posted and I hope you were able to solve it. Due to inactivity, I will go ahead and close the issue for now 🙂 Please feel free to ping a member of the team on discord if you run into any more trouble. Cheers |
@ceyonur @Julian-dev28 Sorry for the late reply because my testnet vaoidator has become non-bootstrapped with unknown issue. I'm figuring out the root cause and will go back to this issue soon. Thanks for following this issue up! |
We suspect that if you have created your chain before you upgrade your subnet-evm, the chain genesis might have stored incorrectly (without feeConfigManager) with the old version of subnet-evm. After you updated the subnet-evm feeConfigManager gets recognized by the new version and being activated in the genesis, which changes the genesis hash. This could create a |
After re-creating a subnet with
I can get/set fee configs with FeeManager correctly
|
@ceyonur @Julian-dev28 I want to consult you on the last question related to this issue: If I want to mint native coins and config dynamic fees on a subnet whose genesis did not contain the precompile configs, how can I add the precompile functionalities? Many thanks! |
Is https://docs.avax.network/subnets/customize-a-subnet#network-upgrades-enabledisable-precompiles what you are looking for? |
Thanks for your sharing, Yulin. For anyone looking for the details of
|
Describe the bug
After upgrading
avalanchego
(1.7.14 -> 1.7.16) andsubnet-evm
(commit 1a7f57e -> 0.2.7), I cannot connect RPC to one of my two EVMs (on different subnets separately).with the genesis containing
contractNativeMinterConfig
andfeeManagerConfig
cannot connect RPC and
avalanchego
showed the error belowTo Reproduce
Steps to reproduce the behavior.
Download the pre-build
avalanchego
andsubnet-evm
.Copy
subnet-evm
toavalanchego-v1.7.16/plugins/<vmid>
Stop the running
avalanchego
v1.7.14.Run
avalanchego
v1.7.16Expected behavior
MetaMask can connect to both blockchains via RPC and transfer native coins.
Screenshots
N/A
Logs
avalanchego-log.zip
Metrics
N/A
Operating System
Additional context
N/A
The text was updated successfully, but these errors were encountered: