-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Autoconfigured web3 #302
Comments
This issue now has a funding of 0.01 ETH (3.02 USDT) attached to it. To view or claim this funding, click here. |
@gitcoinbot 🏩 this is gonna be interesting. |
@Sebohe just in case you didn't notice, once you've got #344 done and merged there is a bounty you can collect: https://gitcoin.co/funding/details?url=https://github.com/pipermerriam/web3.py/issues/302 |
It looks like this issue has been merged in already, so the issue can be closed out. |
@owocki I tried to "accept funding claim" and got:
I closed the issue first and tried it, then reopened and tried it. Both with the same result. Can you pay it out (or tell me how to do it correctly?). |
@carver sorry. that error message is wrong. its erroring out because i submitted the bounty from one of my wallet accounts and only the submitter can accept the bounty. im accepting it now (and will update the error copy by EOW) |
also @Sebohe i just made an executive decision that you work here is worth more than 0.01 ETH ( we funded the bounty very early in the project, before the real funding came in), so i'm going to tip you more than the bounty amount to close this out. |
⚡️ A tip worth 0.05 ETH has been granted to @Sebohe for this issue. ⚡️ Nice work @Sebohe, check your email for further instructions. | Send a Tip |
What was wrong?
In code examples, and short scripts, it's a real PITA to show the ramp-up needed to get web3 working. It conveys that things are going to be tedious (an unfair first impression, I hope):
How can it be fixed?
Instead, I would love to have an autoconfigured web3, especially for some default cases, like localhost on 8545, and the geth IPC file.
This could try to connect to IPC in common locations and then localhost:8545
Or if you are running both IPC and HTTP, and want to give it a hint, that might look like:
The text was updated successfully, but these errors were encountered: