-
Notifications
You must be signed in to change notification settings - Fork 107
feat: Use Custom RPC for Sends #357
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
Conversation
🟡 Heimdall Review Status
|
|
Review Error for ginalw @ 2025-08-05 00:35:41 UTC |
7b579a8 to
a17c07a
Compare
10034e1 to
712365b
Compare
|
7e19e65 to
fe43273
Compare
2f6646b to
eb71ded
Compare
1b6f9a7 to
91f9994
Compare
4ec4091 to
8b91981
Compare
|
Review Error for ginalw @ 2025-08-19 23:25:26 UTC |
Description
Map chain id resovled from RPC URL to a CDP network identifier (e.g. chain id 8453 resolves to "base"). This will be used to determine if the API should be used for sends, or Web3.py
Builder should be able to pass in their own RPC URL, which will result in tx sends to go to that RPC URL instead of CDP API, and tx waits to also use that RPC URL
If a builder passes an RPC URL for base or base sepolia, the CDP API should still be used for sends, but waits will use their RPC URL
Tests
Checklist
A couple of things to include in your PR for completeness: