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

feat(relayer): bridge relayer messaging queue #14528

Closed
cyberhorsey opened this issue Aug 16, 2023 · 2 comments · Fixed by #14605
Closed

feat(relayer): bridge relayer messaging queue #14528

cyberhorsey opened this issue Aug 16, 2023 · 2 comments · Fixed by #14605

Comments

@cyberhorsey
Copy link
Contributor

cyberhorsey commented Aug 16, 2023

Describe the feature request

Relayer should be split up into two subcommands, indexer and processor. Indexer indexes the chain and adds messages to a queue (rabbit, Kafka, etc). Processor reads from the queue.

This will enable high fault tolerance and persistence, especially when the chain is backed up and blocks take a very long time to verify.

A refactor should accompany this to use the same urfave cli package as taiko-client, to make it easier to work across both projects, and similiar subcommand/config pattern.

Describe alternatives you've considered

No response

Additional context

No response

@dantaik
Copy link
Contributor

dantaik commented Aug 28, 2023

@cyberhorsey could you provide an ETA for this? I hope to launch alpha-5 ASAP.

@cyberhorsey
Copy link
Contributor Author

cyberhorsey commented Aug 28, 2023

@dantaik this is not something urgent, and can be deployed during alpha-5 if we choose to go down this path. Do not consider it a blocker.

The relayer is already up to date and working with the latest Bridge and Vault changes, including NFT support, which would block alpha-5.

@dantaik dantaik changed the title Bridge relayer messaging queue feat(relayer): bridge relayer messaging queue Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
3 participants