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.

Sign up for GitHub

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

Jump to bottom

Adapt the new Signal Service in Bridge UI/Backend #12960

Closed
dantaik opened this issue Jan 17, 2023 · 2 comments
Closed

Adapt the new Signal Service in Bridge UI/Backend #12960

dantaik opened this issue Jan 17, 2023 · 2 comments
Assignees
@shadab-taiko
Labels
area.bridge
Milestone
eth_getProof call...

Comments

@dantaik
Copy link
Contributor

dantaik commented Jan 17, 2023 •
edited
Loading

Now the MK proof for signals/message are stored in the SignalService address, not the Bridge contract address. We need to change the bridge relayer logics to adapt this change.
@dantaik dantaik changed the title Adopt the new Signal Service in Bridge UI/Backend Adapt the new Signal Service in Bridge UI/Backend Jan 17, 2023
@dantaik
Copy link
Contributor Author

dantaik commented Jan 20, 2023

This can be done once we have an alpha-2 devnet

@shadab-taiko shadab-taiko mentioned this issue Feb 2, 2023
Merged
@shadab-taiko shadab-taiko mentioned this issue Feb 16, 2023
Merged
@shadab-taiko
Copy link
Contributor

Completed in #13170

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shadab-taiko shadab-taiko

Labels
area.bridge
Projects
Taiko Project Board
Status: ✅ Done
Milestone
eth_getProof call to be pointed to Si...
Development

No branches or pull requests
3 participants
@dantaik @shadab-taiko @cyberhorsey