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

Canonical fee-based relay decision #336

Open
cam-schultz opened this issue Jun 17, 2024 · 0 comments
Open

Canonical fee-based relay decision #336

cam-schultz opened this issue Jun 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@cam-schultz
Copy link
Collaborator

Context and scope
The existing relay decision logic is solely concerned with correctness, and not profitablility. For example, the teleporter package MessageHandler implementation relays the message if 1) it is an allowed relayer and 2) the message has not been delivered already. Otherwise, it always spends the compute, networking, and gas to aggregate a Warp signature and deliver the message to the destination.

Alonside architectural changes to aid in implementing custom profitability logic, we should provide a basic example of how the relayer can parse a Teleporter message and make a profit-based decision. Since it's meant only as an example, using a free tier API should suffice.

Discussion and alternatives
We should wait until #335 to implement this, and aim to have it fit into the new archtecture.

@cam-schultz cam-schultz added the enhancement New feature or request label Jun 17, 2024
@cam-schultz cam-schultz added this to the Relayer extensibility milestone Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog 🗄️
Development

No branches or pull requests

1 participant