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

Better error handling of an arbitrary number of different RPC providers and their varied responses #561

Open
shanefontaine opened this issue Feb 14, 2024 · 0 comments

Comments

@shanefontaine
Copy link
Member

With the decentralized bonder role, anyone can use any RPC provider. This means the bonder will receive errors that it has never seen. Handle these, or ensure they're covered by a fallback.

Additionally, our current error handling is very ethers specific. Given a possible upgrade in the future, try to head towards a more generalized error handling system.

Reference Conversation

maybe it would be good to determine what kind of errors to expect and see if ethers already handles them with a custom error type or create a wrapper to throw custom error types for any that ethers doesn't handle. errors such as:

- server error
- network error
- timeout
- tx failure
- nonce too low
- insufficient funds
- unprediable gas limit
- log range error
- onchain revert
- onchain call exception
etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant