Message Relayer #116
Open
Message Relayer #116
Conversation
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
fix comment fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In order to abstract away fees / gas limits, we can introduce a third party contract that relays the deposit message and deals with fees. The simple flow is:
claimDepositon behalf of user - receiving the deposited ETHThe relayer profits the difference between the fee and any gas cost incurred by calling
relayMessage. It is up to the relayer to determine if this is a profitable trade for them. The user will always get a determined amount (i.e amount deposited - fee).I suspect other protocols / relayers might deploy their own relayer contract with a more complex fee mechanism.