Mining upon a base with early block cause " weight draw", is this expected? #6685
Replies: 1 comment
-
Hi @ricktian1226 , do you still need help with this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
miner tried to mine on 904463 as follow:
2021-07-05T07:11:11.247+0800 ^[[34mINFO^[[0m miner miner/miner.go:646 completed mineOne {"tookMilliseconds": 5164, "forRound": 904463, "baseEpoch": 904461, "baseDeltaSeconds": 36, "nullRounds": 1, "lateStart": false, "beaconEpoch": 1000307, "lookbackEpochs": 900, "networkPowerAtLookback": "8095175825230954496", "minerPowerAtLookback": "1396792084135936", "isEligible": true, "isWinner": true, "error": null}
Attention to "baseDeltaSeconds": 36 . When miner mine 904463, the base it calculate on is 904461. And lotus encouters "weight draw", block was abandoned...
2021-07-05T07:11:30.125+0800 ^[[31mERROR^[[0m chainstore store/store.go:414 weight draw {"currTs": "[bafy2bzaceaxvae7ubj2k7stanbtax64wgou7vvdqyjgm7msuolkq2x7suyd4i]", "ts": "[bafy2bzacea7gtbjewlomps3c7tn5puw7hrx7cqedyq67zebooqqrzgu5h7p34]"}
The question is : Is it correct to mine 904463 base on 904461? I think the result will always be abandoned.
Beta Was this translation helpful? Give feedback.
All reactions