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

Root Cause Analysis of unprocessed tx #105

Closed
rstormsf opened this issue Jun 13, 2018 · 8 comments
Closed

Root Cause Analysis of unprocessed tx #105

rstormsf opened this issue Jun 13, 2018 · 8 comments

Comments

@rstormsf
Copy link
Contributor

https://etherscan.io/tx/0xca1e73891a0634867e14f42ac3c48c50f5b6ce95d51ff3f5c107844f4437f9b4

@yrashk
Copy link
Contributor

yrashk commented Jun 13, 2018

In order to make sure I can do the best job here, can you please provide your specific expectations and how did they fail?

Also, a specific version of the bridge used will be helpful to have.

@rstormsf
Copy link
Contributor Author

1 updated bridge node successfully processed it.

2 other old May 10th bridge rust node missed it.

@yrashk
Copy link
Contributor

yrashk commented Jun 13, 2018

Ok, so you expected old bridge to work, but it didn't. You also expected the new bridge to work, and it did. Correct?

@rstormsf
Copy link
Contributor Author

Looking more into it,
looks like it is problem with new bridge rust node

@yrashk
Copy link
Contributor

yrashk commented Jun 13, 2018

Please specify what seems to be the problem, as precisely as reasonably possible.

@rstormsf
Copy link
Contributor Author

CollectedSignatures event was fired and the node that was responsible for it - send a tx to Home bridge which failed
https://poaexplorer.com/tx/0x669b271f4526ea44fc3a62986604a9105c00d8a739554eef45c0a4f0ad1de7fb

@yrashk
Copy link
Contributor

yrashk commented Jun 13, 2018

Problem was resolved. Relaying the analysis by @rstormsf: default gas limit for withdraw_relay was set to 100k in the configuration, updating it to 300k resolved the issue.

@rstormsf
Copy link
Contributor Author

yes, also if the bridge was using estimateGas without relying on those hard coded values, we wouldn't have this issue as well

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

2 participants