[Feature] Relay Fee to protect spamming attack #10
Conversation
This file contains 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
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.
Summary
Ethereum transaction fee is 100x bigger than Terra transaction fee, so a attacker can easily drain Shuttle fee pool(ETH) with small amount of Terra side asset by spamming transactions to Shuttle.
To prevent this case, we will charge shuttle fee in following equation.
Fee only charged when a user send an asset Terra => Ethereum.
We use various oracle sources to compute $1 value of asset. If a user sends smaller amount asset than $1 value, that tx will not be relayed to Ethereum side.