This commit reinstates a custom l1 cost function which always returns zero.
We thought we could get rid of this by simply setting the l1 fee scalars to zero, but we missed the l1 blob fee scalars on alfajores so removing our custom l1 cost function causes a hardfork while syncing alfajores.
In order to remove our l1 cost function without introducing an unintentional hardfork, we'll need to have a hardfork so that we can switch off the use of the cost function at a certain point. But for now reinstating our custom cost function means that we can use this branch for our alfajores deployment. It will cause some tests in the optimism repo to fail but that seems like a reasonable trade off for not having to manage two separate branches (one for local development and one to be deployed on alfajores).
This reverts commit e6a34232c02327efd6de781633cea6314df43432.
This is actually reverting a commit from another branch (celo8) so don't be confused if you can't find the reverted commit in this branch.
This commit reinstates a custom l1 cost function which always returns zero.
We thought we could get rid of this by simply setting the l1 fee scalars to zero, but we missed the l1 blob fee scalars on alfajores so removing our custom l1 cost function causes a hardfork while syncing alfajores.
In order to remove our l1 cost function without introducing an unintentional hardfork, we'll need to have a hardfork so that we can switch off the use of the cost function at a certain point. But for now reinstating our custom cost function means that we can use this branch for our alfajores deployment. It will cause some tests in the optimism repo to fail but that seems like a reasonable trade off for not having to manage two separate branches (one for local development and one to be deployed on alfajores).
This reverts commit e6a34232c02327efd6de781633cea6314df43432.
This is actually reverting a commit from another branch (celo8) so don't be confused if you can't find the reverted commit in this branch.