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

Missing config for Witti Prysm beacon #11

Closed
handelaar2 opened this issue May 27, 2020 · 4 comments · Fixed by #12
Closed

Missing config for Witti Prysm beacon #11

handelaar2 opened this issue May 27, 2020 · 4 comments · Fixed by #12

Comments

@handelaar2
Copy link
Contributor

handelaar2 commented May 27, 2020

The Prysm beacon config only shows --web3provider ws://127.0.0.1:8546
This is incomplete as currently Prysm uses both ws and http.

Only specifying the above can lead to issues, as the http parameter will default to "https://goerli.prylabs.net"
(resulting in 2 different eth1 sources potentially being different)

So if you specify localhost on port 8546, you also have to specify:
--http-web3provider="http://127.0.0.1:8545" \

Details around issue in Prysm rep : prysmaticlabs/prysm#5826

Below a screen print of the Prysm witti config:

2020-05-27_11-37-28

@q9f
Copy link
Member

q9f commented May 27, 2020

damn, I thought one API is enough. why would it require both??

q9f added a commit that referenced this issue May 27, 2020
@q9f q9f closed this as completed in #12 May 27, 2020
q9f added a commit that referenced this issue May 27, 2020
@handelaar2
Copy link
Contributor Author

handelaar2 commented May 27, 2020

Websocket gives performance issue->switch to http for past logs (prysmaticlabs/prysm#2295)
result:
past logs: http
future logs: ws subscription

#5826 initiates a change (hopefully) to http only.
(see discussion at bottom of that issue)

@handelaar2
Copy link
Contributor Author

handelaar2 commented May 27, 2020

Not sure if this will work. It now says:
--http-web3provider ws://127.0.0.1:8545 \

should be:
--http-web3provider http://127.0.0.1:8545 \

@torfbolt
Copy link

Can confirm that it does not work with ws:// instead of http://

@handelaar2 handelaar2 mentioned this issue May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants