Merged
Conversation
tynes
reviewed
Dec 1, 2020
tynes
reviewed
Dec 1, 2020
tynes
reviewed
Dec 1, 2020
| const logs = await layer.provider.getLogs(filter) | ||
| const matches = logs.filter((log: any) => log.data === msgHash) | ||
|
|
||
| // Message was relayed in the past |
Contributor
There was a problem hiding this comment.
This might read a little better if unnested and multiple specific ifs
if matches.length === 1
if matches.length > 1
Contributor
There was a problem hiding this comment.
Will this trigger with more than one if there is a fraud proof that clears the ctc?
tynes
reviewed
Dec 1, 2020
| # @eth-optimism/watcher | ||
|
|
||
| #### Watcher | ||
| Our `Watcher` allows you to retrieve all transaction hashes related to cross domain messages such as deposits and withdrawals. In order to use, first send a transaction which sends a cross domain message, for example a deposit from L1 into L2. After sending the deposit transaction and storing the transaction hash, use `getMessageHashesFromL1Tx(l1TxHash)` to get an array of the message hashes of all of the L1->L2 messages that were sent inside of that L1 tx (This will usually just be a single element array, but it can return multiple if one L1 transaction triggers multiple deposits). `getMessageHashesFromL2Tx(l2TxHash)` does the same for L2->L1 messages. `getL2TransactionReceipt(messageHash)` takes in an L1->L2 message hash and then after 2-5 minutes, returns the receipt of the L2 tx that the message ends up getting relayed in. `getL1TransactionReceipt(messageHash)` does the same for L2->L1 messages, except the delay is 7 days. |
Contributor
There was a problem hiding this comment.
I think replacing personal pronouns with words like the is better for docs. In this case, its Our, the first word
tynes
reviewed
Dec 1, 2020
| # @eth-optimism/watcher | ||
|
|
||
| #### Watcher | ||
| Our `Watcher` allows you to retrieve all transaction hashes related to cross domain messages such as deposits and withdrawals. In order to use, first send a transaction which sends a cross domain message, for example a deposit from L1 into L2. After sending the deposit transaction and storing the transaction hash, use `getMessageHashesFromL1Tx(l1TxHash)` to get an array of the message hashes of all of the L1->L2 messages that were sent inside of that L1 tx (This will usually just be a single element array, but it can return multiple if one L1 transaction triggers multiple deposits). `getMessageHashesFromL2Tx(l2TxHash)` does the same for L2->L1 messages. `getL2TransactionReceipt(messageHash)` takes in an L1->L2 message hash and then after 2-5 minutes, returns the receipt of the L2 tx that the message ends up getting relayed in. `getL1TransactionReceipt(messageHash)` does the same for L2->L1 messages, except the delay is 7 days. |
Contributor
There was a problem hiding this comment.
There is still a large inferential gap here, ie In order to use, first send a transaction which sends a cross domain message, for example a deposit from L1 into L2. isn't technical enough for somebody to just pick up and use. I think specifying SentMessage(bytes) event emitted on the xdomain contract would be useful
tynes
requested changes
Dec 9, 2020
Contributor
tynes
left a comment
tynes
left a comment
There was a problem hiding this comment.
I think run-watcher.js isn't ready yet
tynes
force-pushed
the
feat/updatedWatcher
branch
from
306f50f to
086946a
Compare
tynes
approved these changes
Jan 26, 2021
Contributor
tynes
left a comment
tynes
left a comment
There was a problem hiding this comment.
I rebased and pushed changes to fix the script, the other changes are less important now
snario
pushed a commit
that referenced
this pull request
Apr 14, 2021
serpixel
added a commit
that referenced
this pull request
May 20, 2025
iquidus
pushed a commit
to Layr-Labs/optimism
that referenced
this pull request
Jul 24, 2025
* feat: add mul access lists test (ethereum-optimism#370) * feat: add mul access lists test * chore: polish * chore: pre pr * feat: add more tests * feat: wip to add more tests * fix: multiple msgs tests * fix: semgrep (ethereum-optimism#371) --------- Co-authored-by: Disco <131301107+0xDiscotech@users.noreply.github.com>
theochap
pushed a commit
that referenced
this pull request
Dec 10, 2025
theochap
pushed a commit
that referenced
this pull request
Jan 15, 2026
### Description Removes the optimism-specific protocol crate becoming very bloated with interop types, batching primitives like compressors and decompressors, and derivation-specific data structures.
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
4 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.
Description
Adds the watcher tool, which allows front-ends to watch for cross domain messages and receive the transaction receipt of the cross domain message when it is relayed to its destination.
Questions
Metadata
Fixes
Contributing Agreement