-
Notifications
You must be signed in to change notification settings - Fork 165
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
cmd: Remove default values for -ethUrl #1448
Conversation
Curious, will users have a convenient way to discover or acquire an Ethereum JSON-RPC endpoint? Should that be documented somewhere? This is going to require that mainnet users upgrading to the next release make changes to their CLI flags, right? |
Users will still be able to use a hosted node service like Infura or Alchemy if they don't want to run their own node they'll just have to sign up for an account themselves. livepeer/docs#58 updates RTD with a section on connecting either to hosted node service or a self-hosted node. Side note: I was thinking about whether this information should go into this repo or in the RTD and decided to update RTD since some of that information was already there. Would be interested in just rendering go-livepeer specific docs from this repo at some point and having RTD linking to the "go-livepeer guide".
Yeah. We're removing the default Infura endpoints because we're going to only allow requests from the explorer soon for those endpoints (I believe this is in response to updates to Infura's pricing plan). |
70c2315: Add development docs with notes on running tests and specifying mainnet/Rinkeby Ethereum node JSON-RPC API URLs in order to run certain tests. |
Maybe also include a link to the RTD docs for those trying to figure out how to obtain an Ethereum JSON-RPC URL? I know this has been forewarned a few times on Discord, the forums, etc, but I'd also make sure this change is prominently called out in the release notes and announcement as something that requires user action in order to complete the upgrade. Also doesn't hurt to explain the reason for it, eg Infura pricing, so users feel a little more informed and it seems a little less arbitrary, because registering with a RPC service or setting up a node is going to be a point of friction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Added in c808bb4. The link to RTD doesn't actually go to the relevant section, but this will be fixed once livepeer/docs#58 is merged.
👍 Definitely. Planning on calling this out in the release notes + Discord announcement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after a fixup
Looks good, let's squash the fixup commit 👍 |
ef463ef
to
0f04ae4
Compare
What does this pull request do? Explain your changes. (required)
This PR removes the default values for the
-ethUrl
flag. After this PR, whenever the node connects to an on-chain network, an Ethereum node JSON-RPC URL will need to be explicitly provided using the-ethUrl
flag.Specific updates (required)
-ethUrl
flagtest_args.sh
if theMAINNET_ETH_URL
env variable is settest_args.sh
if theRINKEBY_ETH_URL
env variable is set-ethUrl
in README commandsValues for
MAINNET_ETH_URL
andRINKEBY_ETH_URL
are set via CircleCI.How did you test each of these updates (required)
Updated tests in
test_args.sh
.Does this pull request close any open issues?
Fixes #1434
Checklist:
./test.sh
pass