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

OG-636 obscure revert message in validateRelayCall #706

Merged
merged 1 commit into from
Oct 29, 2021

Conversation

drortirosh
Copy link
Member

unable to decode error from relayCall revert (e.g. "paymaster balance
too low")

unable to decode error from relayCall revert (e.g. "paymaster balance
too low")
@drortirosh drortirosh merged commit 0bec6cc into releases/v2.2.x Oct 29, 2021
@drortirosh drortirosh deleted the OG-636-revert-message-validateRelayCall branch October 29, 2021 15:52
shahafn pushed a commit that referenced this pull request Dec 13, 2021
unable to decode error from relayCall revert (e.g. "paymaster balance
too low")
shahafn added a commit that referenced this pull request Dec 20, 2021
* Fixing selection default mechanism

* OG-636 obscure revert message in validateRelayCall (#706)

unable to decode error from relayCall revert (e.g. "paymaster balance
too low")

* OG-630 - Boosted gasPrice is sometimes lower after boosing than before (#708)

apply our minimum value also to boosted transactions.
(NOTE: we still don't know how a small (e.g. 1 wei) value got into the
DB of old transactions, but in general, current GasPrice is good minimum
not only for new transactions but also for boosted transactions.

* Adding tests

Co-authored-by: Dror Tirosh <[email protected]>
Co-authored-by: Alex Forshtat <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants