You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2021. It is now read-only.
The operator tracks the status of challenge response transactions and logs an error if a transaction fails. Currently we do not log the failure reason because it is unclear how failure information can be extracted from go-ethereum.
Ideally we would like to log an error with the error reason (e.g., "out of gas") if a challenge response transaction fails.
The text was updated successfully, but these errors were encountered:
Not sure if this will also cover "out of gas", but #54 should cover other revert reasons.
In most cases it should detect an "out of gas" error but since ethereum has no canonical way of detecting this, there are some cases where it will return with a generic reason.
The operator tracks the status of challenge response transactions and logs an error if a transaction fails. Currently we do not log the failure reason because it is unclear how failure information can be extracted from go-ethereum.
Ideally we would like to log an error with the error reason (e.g., "out of gas") if a challenge response transaction fails.
The text was updated successfully, but these errors were encountered: