You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey all, I've been having some issues on spinning up mev-boost on a goerli testnet machine with two validators (64 goETH) being staked. Both the validators can be seen using the following links:
I see the following logs on my machine running geth v1.10.23 / prysm v3.0:
koala@koala:~$ mev-boost -goerli -relay-check -relays https://0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110@builder-relay-goerli.flashbots.net
INFO[2022-08-31T04:55:44-04:00] mev-boost v0.7.10 module=cli
INFO[2022-08-31T04:55:44-04:00] Using genesis fork version: 0x00001020 module=cli
INFO[2022-08-31T04:55:44-04:00] using 1 relays module=cli relays="[{0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110 https://0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110@builder-relay-goerli.flashbots.net}]"
INFO[2022-08-31T04:55:44-04:00] Checking relay module=service relay="https://0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110@builder-relay-goerli.flashbots.net"
INFO[2022-08-31T04:55:45-04:00] listening on localhost:18550 module=cli
INFO[2022-08-31T04:56:09-04:00] http: GET / 200 duration=0.000114296 method=GET module=service path=/ status=200
INFO[2022-08-31T04:56:15-04:00] http: GET / 200 duration=4.6419e-05 method=GET module=service path=/ status=200
INFO[2022-08-31T04:56:38-04:00] http: GET /eth/v1/builder/status 200 duration=0.049115153 method=GET module=service path=/eth/v1/builder/status status=200
WARN[2022-08-31T04:59:12-04:00] error calling registerValidator on relay error="HTTP error response: 400 / {\"code\":400,\"message\":\"failed to verify validator signature for 0xa26f92f0a0482db5b2d5c697058599587045b522a31ed22f392bb4d1be58b840cc5f66af8032db5723672a733d1593a0\"}\n" method=registerValidator module=service numRegistrations=2 ua=Go-http-client/1.1 url="https://builder-relay-goerli.flashbots.net/eth/v1/builder/validators"
INFO[2022-08-31T04:59:12-04:00] http: POST /eth/v1/builder/validators 502 duration=0.20179482 method=POST module=service path=/eth/v1/builder/validators status=502
My validator routinely shows this upon each epoch:
Aug 31 05:18:24 koala validator[10757]: time="2022-08-31 05:18:24" level=warning msg="Failed to update proposer settings" error="could not submit signed registrations to beacon node: rpc error: code = InvalidArgument desc = Could not register block builder: could not register validator(s): Post "http://127.0.0.1:18550/eth/v1/builder/validators": dial tcp 127.0.0.1:18550: connect: connection refused: Builder API validator registration unsuccessful" prefix=validator slot=3785792
Any thoughts?
The text was updated successfully, but these errors were encountered:
@metachris What could be causing this error? Apologies if I'm not getting the whole picture of this. I have been using the Flashbots & bloXroute relay and they appear to be still producing the error.
It appears that I was missing the "--goerli" flag on my validator. It may be useful for people to note that you must have this flag if you are using somer-esat's testnet systemd settings for prysm.
Hey all, I've been having some issues on spinning up mev-boost on a goerli testnet machine with two validators (64 goETH) being staked. Both the validators can be seen using the following links:
https://prater.beaconcha.in/validator/0xa26f92f0a0482db5b2d5c697058599587045b522a31ed22f392bb4d1be58b840cc5f66af8032db5723672a733d1593a0
https://prater.beaconcha.in/validator/0x8fe2fd7a550ef84b8abc725c4b2044f95a2a8815c6f6b0ed7ade5aef509a678926fc5243eef226fa94a26d8b92092d2d
I see the following logs on my machine running geth v1.10.23 / prysm v3.0:
My validator routinely shows this upon each epoch:
Any thoughts?
The text was updated successfully, but these errors were encountered: