Conversation
Also fixes a linter error that wasn't caught while the CI was broken.
feat: fix teleportr ci, and lint target
This avoids having l2geth as a dependency for other projects building on bss-core. Speicifically this avoids having to copy l2geth into docker builds.
Less casting.
Currently the teleportr database supports a LatestDeposit method, which returns the highest block number observed, if any. The intent was to use this as the starting point for syncing, however, this isn't super useful as there may be long periods of inactivity that we have already scanned. Instead, we now store the last processed block in a separate table, and pass the end of the ingestion block range as argument to UpsertDeposits. The list of deposits and last processed block are written atomically to avoid consistency issues. The value can be retrieved using the LastProcessedBlock getter.
Update the batch serialization to allow for typed batches. Also include logic for type 0 batches, which are compressed with zlib.
Enable typed batch support in the batch submitter. Type 0 batches (zlib compressed) can be enabled with the env var `BATCH_SUBMITTER_SEQUENCER_BATCH_TYPE=zlib` or via the flag `--sequencer-batch-type zlib`.
The data transport layer will now be able to index typed batches. A typed batch has the first batch context have a timestamp of 0 and the blocknumber is used as an enum to determine the type of the batch. It is not possible to have a timestamp of 0 in realistic conditions. Batches that have a non zero timestamp as the first batch context are considered a legacy batch. The first typed batch is type 0 where the blocknumber is 0 and the transaction data is compressed with zlib.
Allow the go batch submitter to submit typed batches. The env var `BATCH_SUBMITTER_SEQUENCER_BATCH_TYPE=zlib` can be set to enable the submission of zlib compressed batches. If that env var is not set, then legacy batches will be submitted instead.
Update the docker compose config such that the batch submitters submit type 0 batches (zlib compressed) and then add an integration test for that functionality.
This commit updates the config so that the CI can run the batch submitters in each mode so that we continue to test each of the batch types. It also lints the yaml files
feat: add Teleportr service
ci: Update nightly address manager addr, notify on itest failures
The current methodology only attempts to run unit tests when changes to the package paths are detected. However, this is brittle and most notably doesn't capture when changes are made to the workflow itself. As a result, a green build in a PR doesn't neccessarily correlate to a green build after merge. Unit tests are cheap, so this should prevent needless false positives.
This commit increases the statement and branch coverage of the contracts package. More specificall the contracts that were covered are: - AddressDictator - ChugSplashDictator - L1CrossDomainMessenger - L1StandardBridge - CanonicalTransactionChain - ChainStorageContainer - StateCommitmentChain - L2CrossDomainMessenger - L2StandardBridge - WETH9 - Lib_OVMCode - Lib_RLPWriter - Lib_SecureMerkleTrie - Lib_Buffer - Lib_MerkleTree
…ackage increase coverage of contracts package
contracts: fetch batches hardhat task
fix(rhc): fix dockerfile bug
fix(bridge): Corrected a comment
Adds a function to the SDK (waitForMessageStatus) which will wait until the status of a particular message matches the target status. waitForMessageStatus also handles certain special cases where different status messages are incompatible (e.g., the RELAYED and FAILED_L1_TO_L2_MESSAGE status for L1 to L2 messages). Useful to avoid including looping logic in your own application.
Removes yargs as a dependency from the contracts package since it wasn't being used. Always good to cut unused dependencies.
feat: remove packages/batch-submitter
feat(sdk): add fn to wait for message status
fix(ct): remove yargs as unused dep
Adds support for system addresses. To deploy to a system address, the deployer must either be in the list of hardcoded addresses described in `SystemAddressDeployers`, or be specified via the `SYSTEM_ADDRESS_0_DEPLOYER`/`SYSTEM_ADDRESS_1_DEPLOYER` environment variables. The hardcoded system addresses deployers will always override those placed in the environment, so specifying the `SYSTEM_ADDRESS_*` env vars on mainnet, Kovan, or Goerli is a no-op. The env vars are available primarily for testing purposes. The contract deployment **must** be the first transaction from the deployment address - i.e., it must have nonce zero. In order to make the tests work, I had to change the integration tests chain ID to no longer conflict with Goerli. The new integration tests chain ID is `987`. Co-Authored-By: @Inphi
l2geth: Add support for system addresses
🦋 Changeset detectedLatest commit: 82465db The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
2-reviewers
A-op-batcher
Codecov Report
@@ Coverage Diff @@
## master #2264 +/- ##
==========================================
+ Coverage 74.42% 80.08% +5.66%
==========================================
Files 79 77 -2
Lines 2545 2460 -85
Branches 397 450 +53
==========================================
+ Hits 1894 1970 +76
+ Misses 651 490 -161
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
theochap
pushed a commit
that referenced
this pull request
Dec 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
toJSONmethods on batch primitives