Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bridge relayer did not pick up a message #17466

Closed
1 task done
dantaik opened this issue Jun 3, 2024 · 3 comments
Closed
1 task done

bridge relayer did not pick up a message #17466

dantaik opened this issue Jun 3, 2024 · 3 comments

Comments

@dantaik
Copy link
Contributor

dantaik commented Jun 3, 2024

Describe the bug

I sent two messages from L1 to L2, the first one got picked up by the relayer so it shows up in the UI, but the second one did not.

tx1: https://etherscan.io/tx/0x77c61b3dfb0d226181e5a69ff0d611a4bec832b6e08fda691f6765ad25fcf163
tx2: https://etherscan.io/tx/0x12c12ef08bdf7ee87bf6c10fa3cefd32ad132590682dd3ca636badb34907bd08

Steps to reproduce

The message's to address is 0x08c82ab90f86BF8d98440b96754a67411D656130, which is not a vault.

Spam policy

  • I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.
@cyberhorsey
Copy link
Contributor

Will take a look.

Copy link
Contributor

github-actions bot commented Jul 4, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jul 4, 2024
Copy link
Contributor

This issue was closed because it has been inactive for a week since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment