Implement read-only provider #749
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for basin canceled.
|
✅ Deploy Preview for beanstalk-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
uncoolzero
approved these changes
Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a read only provider to the beanstalk SDK which allows the UI (or other consumers) to implement a different provider for read-only operations.
Specifically, this allows us to configure the UI to read silo balances using this provider, and this provider will be set to use BeanstalkFarms' Alchemy account... meaning no more RPC limit errors for users who have wallets/providers with low limits.