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

Introduction of revert error codes #494

Open
akolotov opened this issue Sep 12, 2020 · 0 comments
Open

Introduction of revert error codes #494

akolotov opened this issue Sep 12, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@akolotov
Copy link
Collaborator

Currently the bridge contracts do not use the revert messages to clarify the reason of reverts. That's why sometimes it is hard to guess the exact reason why the bridge operations were reverted. At the same time, the revert reasons started supporting by the block explorers like etherscan and blockscout that's why it makes sense to provide the messages to the users there, explaining why the revert happened.

Since introduction of the string messages as the revert reasons could require intensive storage usage, it is worth to consider to use error codes that could consume less gas.

@akolotov akolotov added the enhancement New feature or request label Sep 12, 2020
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
None yet
Development

No branches or pull requests

1 participant