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.

Sign up for GitHub

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

Jump to bottom

[TASK] Give the ability to use a dedicated RPC URL at the SDK level #866

Open
alainncls opened this issue Dec 17, 2024 · 2 comments
Open

[TASK] Give the ability to use a dedicated RPC URL at the SDK level #866

alainncls opened this issue Dec 17, 2024 · 2 comments
Labels
Good first issue Tech Task

Comments

@alainncls
Copy link
Collaborator

Right now, the SDK relies on the default endpoints for the supported networks.
While this is sufficient for a small-scale dApp or service, this might lead to reaching rate limits on larger scale projects.

The goal of this ticket is to let anyone instantiate the SDK with a new optional parameter: an RPC URL.
This can be done by adding a new field in the Conf type, passing it when instantiating the SDK.
@alainncls alainncls moved this to Ready for development in Verax Attestation Registry Dec 17, 2024
@futaruz1
Copy link

how to get sepolia arb

@alainncls
Copy link
Collaborator Author

how to get sepolia arb

What's the point for this ticket?
In any case, the easiest is probably to bridge some ETH to Arbitrum 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Good first issue Tech Task
Projects
Verax Attestation Registry
Status: Ready for development
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alainncls @futaruz1