-
Notifications
You must be signed in to change notification settings - Fork 78
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
Comments
damn, I thought one API is enough. why would it require both?? |
Websocket gives performance issue->switch to http for past logs (prysmaticlabs/prysm#2295) #5826 initiates a change (hopefully) to http only. |
Not sure if this will work. It now says: should be: |
Can confirm that it does not work with ws:// instead of http:// |
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:
The text was updated successfully, but these errors were encountered: