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
We has detected that validators are not receiving MEV rewards and are instead using locally built blocks.
2. Logs Analysis
Lighthouse Logs:
0:38:12.403 INFO New block received root: 0x294131c1e4320dbe6dea0c63175b81cc84c8417b171b16f8199a51e89f13c6c3, slot: 10636989
Dec 17 20:38:13.234 INFO Prepared beacon proposer parent_root: ..., validator: 1001548, prepare_slot: 10636990, service: beacon
Dec 17 20:38:23.230 INFO Requesting blinded header from connected builder, parent_hash: ..., pubkey: ..., slot: Slot(10636990), service: exec
Dec 17 20:38:24.232 INFO Requested blinded execution payload ..., relay_response_ms: 1001, relay_fee_recipient: request failed, service: exec
Dec 17 20:38:24.233 WARN Builder error when requesting payload ..., relay_error: HttpClient(url: http://127.0.0.1:18550/, kind: timeout, detail: operation timed out), info: falling back to local execution client, service: exec
...
Key Points:
Timeout Errors: Lighthouse attempts to request blinded execution payload from the local MEV-Boost service (http://127.0.0.1:18550/) but encounters a timeout (operation timed out).
Fallback to Local Execution: Due to the timeout, Lighthouse falls back to the local execution client, bypassing MEV-Boost and thus not receiving MEV rewards.
We seek assistance from the MEV-Boost community to:
Beacon to MEV-Boost Request Time
There is a discrepancy in request times between Beacon and MEV-Boost, potentially indicating underlying latency issues.
20:38:23.230 - (Lighthouse) Requesting blinded header from connected builder
20:38:23.317 - (Mev-boost) method=getHeader
MEV-Boost Log Gaps
Short intervals between MEV-Boost logs suggest rapid processing, but overall latency remains an issue..
20:38:23.317 - (Mev-boost) method=getHeader
20:38:23.364 - (Mev-boost) getHeader request start
Thank you for your support and assistance in resolving this matter.
The text was updated successfully, but these errors were encountered:
1. Problem Description
We has detected that validators are not receiving MEV rewards and are instead using locally built blocks.
2. Logs Analysis
Lighthouse Logs:
Key Points:
http://127.0.0.1:18550/
) but encounters a timeout (operation timed out
).MEV-Boost Logs:
3. Request for Community Assistance
We seek assistance from the MEV-Boost community to:
Beacon to MEV-Boost Request Time
There is a discrepancy in request times between Beacon and MEV-Boost, potentially indicating underlying latency issues.
20:38:23.230 - (Lighthouse) Requesting blinded header from connected builder
20:38:23.317 - (Mev-boost) method=getHeader
MEV-Boost Log Gaps
Short intervals between MEV-Boost logs suggest rapid processing, but overall latency remains an issue..
20:38:23.317 - (Mev-boost) method=getHeader
20:38:23.364 - (Mev-boost) getHeader request start
Thank you for your support and assistance in resolving this matter.
The text was updated successfully, but these errors were encountered: