ceyonur
commented
2 months ago Could you provide your full logs?
Seems they have enabled a new upgrade: (response of eth_getChainConfig from their public API):
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"byzantiumBlock": 0,
"cancunTime": 253431244800,
"chainId": 10849,
"constantinopleBlock": 0,
"durangoTimestamp": 1709740800,
"eUpgradeTimestamp": 253431244800,
"eip150Block": 0,
"eip155Block": 0,
"eip158Block": 0,
"feeConfig": {
"gasLimit": 12000000,
"targetBlockRate": 2,
"minBaseFee": 25000000000,
"targetGas": 25000000,
"baseFeeChangeDenominator": 36,
"minBlockGasCost": 0,
"maxBlockGasCost": 1000000,
"blockGasCostStep": 200000
},
"feeManagerConfig": {
"adminAddresses": [
"0x3a62e34417d02cc6f641feae0b3f6c140457e6dc",
"0x562605473d28ed711e14673e6642d59ef7644827"
],
"blockTimestamp": 0
},
"homesteadBlock": 0,
"istanbulBlock": 0,
"muirGlacierBlock": 0,
"petersburgBlock": 0,
"subnetEVMTimestamp": 0,
"warpConfig": {
"blockTimestamp": 1715625920,
"quorumNumerator": 0
},
"upgrades": {
"precompileUpgrades": [
{
"rewardManagerConfig": {
"adminAddresses": [
"0x444b4a012a240bc0b898e91c70152caee8be26fb"
],
"blockTimestamp": 1721779200
}
}
]
}
}
}See latest rewardManagerConfig under upgrades. Did you include that upgrade on your end? More info here.
xinzhongyoumeng
Describe the bug A clear and concise description of what the bug is. env: subnet-evm version: v0.6.7 avalanchegoversion: v1.11.9 the node log:
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen. the node can sync normally if there is any Node Snapshot?or how to skip the bad block? Screenshots If applicable, add screenshots to help explain your problem.
Logs If applicable, please include the relevant logs that indicate a problem and/or the log directory of your node. By default, this can be found at
~/.avalanchego/logs/.Metrics If applicable, please include any metrics gathered from your node to assist us in diagnosing the problem.
Operating System Which OS you used to reveal the bug. OS:Ubuntu 22.04 Additional context Add any other context about the problem here.
To best protect the Avalanche community security bugs should be reported in accordance to our Security Policy