Our consensus differ from Ethereum's: The proposed block header is incomplete until the preparer/committer bitmaps and signatures are known, where Ethereum's proposed block is already immutable. Ethereum code calls, especially from validator logic, block.Hash() liberally without ill effect, but in our case the validation logic is called before the finalization of committer bitmap, and the block.Hash() calls embedded in the validation fixates and finalizes the block hash prematurely. Until we have a better logic to deal with this, disable block hash caching, and always recompute the block hash using the actual header.pull/839/head
parent
a7ba9a1b67
commit
0782151f75
Loading…
Reference in new issue