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
I can see a lot of errors due to the exporter calling /eth/v1/beacon/blocks/{block_id}.
Jan-30 16:13:19.233[rest] warn: Route GET:/eth/v1/beacon/blocks/finalized not found
Jan-30 16:13:19.236[rest] warn: Route GET:/eth/v1/beacon/blocks/head not found
Jan-30 16:13:19.242[rest] warn: Route GET:/eth/v1/beacon/blocks/finalized not found
Jan-30 16:13:19.244[rest] warn: Route GET:/eth/v1/beacon/blocks/head not found
Jan-30 16:13:23.248[rest] warn: Route GET:/eth/v1/beacon/blocks/0x9544f7f9...b6fd069dff not found
We have removed this api more than 6 months ago from Lodestar and it's not part of the latest beacon api spec release given those were removed almost 3 years ago ethereum/beacon-APIs#218 there.
I would be surprised if other clients still support this api, likely just nobody noticed these errors before but I know that all clients support getBlockV2 so it's probably best to start using that api instead.
The text was updated successfully, but these errors were encountered:
When running Kurtosis with the following setting
I can see a lot of errors due to the exporter calling
/eth/v1/beacon/blocks/{block_id}
.We have removed this api more than 6 months ago from Lodestar and it's not part of the latest beacon api spec release given those were removed almost 3 years ago ethereum/beacon-APIs#218 there.
I would be surprised if other clients still support this api, likely just nobody noticed these errors before but I know that all clients support getBlockV2 so it's probably best to start using that api instead.
The text was updated successfully, but these errors were encountered: