removed unused variable

removed-sequencer

removed-sequencer references

remove sequencer variable

removed unused variable

removed-sequencer

removed-sequencer references

remove sequencer variable

test(integration): withdrawing a fake L2 token

fix(bss,dtl): correctly submit and parse timestamp information for L1 to L2 txs

go/batch-submitter: Downgrade Alpine version

Alpine 3.14 has an issue (https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0#faccessat2) that prevents it from working on CircleCI at this time.

integration-tests: Increase withdrawal timeout

This commit makes sure that the DTL correctly returns timestamps using
the new scheme when the first batch submitter hardfork block is
activated. If the block is not activated, the DTL will operate as it
previously did.

Monotonicity violations were being reported in two locations, once in
the sync service and then later in the worker. Because of recent updates
in the sync service, there's never a case where monotonicity violations
would not be caught first within the sync service. This code path only
triggered within L1 syncing verifiers and caused issues with unintended
timestamp manipulation.

.env files were not being ignored by docker. This meant that any local
environment variable changes you placed into an .env file would be
pulled into docker images built inside of the ops package. Docker images
should only be using environment variables as specified in their
respective environment folders and should not copy over .env files.

This commit fixes a bug in the batch submitter where not all timestamp
information was being correctly rolled up. This has temporarily caused
certain L1 syncing nodes to generate an incorrect state root. This PR
will be followed by a second PR with an update to the DTL to guarantee
that incorrect timestampd data can be corrected.

Add verifier integration tests behind the env var
`RUN_VERIFIER_TESTS`. Note that this depends on the
batch submitter correctly submitting batches because
the verifier syncs from the batches submitted by the
batch submitter.

The verifier is not enabled by default with the
`docker-compose.yml` file. To enable it, the replicas
field must be updated from `0` to `1`.

Version Packages

Develop -> Master PR

go/batch-submitter: HTTP/2 fixes

feat: modify txmgr to send EIP-1559 txns

test: improve test coverage for aliasing

l2geth: Add berlin hardfork

Develop -> Master PR

Removes the MAX_L1_GAS_PRICE_IN_GWEI and GAS_RETRY_INCREMENT env vars,
as well as the MinL1GasPrice, MaxL1GasPrice, and GasRetryIncrement
values from the txmgr config struct.

This commit adds a fallback in case the L1 provider does not support
queries for eth_maxPriorityFeePerGas. Of our infrastructure providers,
i.e. Alchemy, Infura, Quicknode, and Hardhat (in test envs), only
Alchemy suports this call. In production, we will be routing this call
directly to Alchemy, which should work in the general case. However, if
they were to be unavailable the batch submitter would be stalled until
service was restored. This modification also allows the new EIP-1559
batch submitter to pass our integration tests, since the default Hardhat
backend can't support the query either.

Version Packages

Develop -> Master PR

fix(bss): have BSS correctly create new contexts

Revert "l2geth: berlin hardfork"