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

Transparent EVM errors #25

Open
Denzel-Haverkamp opened this issue Nov 25, 2023 · 0 comments
Open

Transparent EVM errors #25

Denzel-Haverkamp opened this issue Nov 25, 2023 · 0 comments

Comments

@Denzel-Haverkamp
Copy link

Currently, when an EVM error occurs that is not being parsed yet, the response received is {"code":500,"message":"EVM_ERROR"} (see https://github.com/EnsoFinance/temper/blob/main/src/errors.rs#L81).
In this case, the only way to check which error occurred is to check the Temper CLI logs. It would be nice to have the option to receive the raw EVM error instead of, or in addition to, the parsed error.
A possible way to do this without making it the default behaviour would be to add an optional parameter like "transparent_error": true to the /api/v1/simulate, /api/v1/simulate-bundle and /api/v1/simulate-stateful endpoints.

In addition to getting specific errors for types that are not parsed yet, this would also help users find errors in their transactions more easily, since the raw EVM errors may contain more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant