Closed piersy closed 3 weeks ago
Closed in favour of - https://github.com/celo-org/celo-blockchain-planning/issues/744
But https://github.com/celo-org/celo-blockchain-planning/issues/744 won't avoid the hardfork on alfajores. Should we reopen this, or is this handled in a different way?
This commit from #253 introduced an unintentional hardfork in the alfajores network.
When syncing a new node on alfajores with that commit a different block was calculated at 26386370 (see below). This is likely because we didn't set the L1 fees to zero on alfajores see here - https://celo-alfajores.blockscout.com/address/0x4200000000000000000000000000000000000015?tab=read_proxy On alfajores:
The field that changes (apart from hash ) is stateRoot