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

Refactor RPC Provider Configuration to Support Multiple Services #790

Open
evandrosaturnino opened this issue Dec 10, 2024 · 0 comments
Open
Assignees
Labels
☁️ infrastructure CI, Infrastructure, Workflows

Comments

@evandrosaturnino
Copy link
Collaborator

The PR #785 introduces an implementation which is tightly coupled to Alchemy, making it difficult to integrate alternative RPC providers. To improve flexibility and future-proof the code, introduce a generic configuration structure. For example, use an API_SERVICE_NAME and API_KEY along with a mapping of service names to their respective configurations. This will allow adding or switching RPC providers by simply updating the mapping rather than modifying core logic.

@evandrosaturnino evandrosaturnino added the ☁️ infrastructure CI, Infrastructure, Workflows label Dec 10, 2024
@evandrosaturnino evandrosaturnino self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☁️ infrastructure CI, Infrastructure, Workflows
Projects
None yet
Development

No branches or pull requests

1 participant