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
The Nimbus beacon node requires JSON-encoded blocks to be submitted via the /eth/v2/beacon/blocks endpoint. However, the current implementation of the go-eth2-client library does not support this format for Nimbus, leading to issues when using Nimbus as a beacon node in Kurtosis.
🛠️ Proposed solution
Introduce a feature flag (e.g., --feature-set-enable=json_requests) in Charon to enable JSON-encoded block submission for Nimbus.
Document the requirement for enabling the JSON-encoded block submission feature when using Nimbus as a beacon node in the release notes.
Plan for eventual removal of the feature flag once Nimbus and other beacon nodes support the SSZ-encoded block format natively.
The text was updated successfully, but these errors were encountered:
Add `WithEnforceJSON(true)` parameter when `json_requests` feature is enabled in `featureset`.
This is needed for Nimbus BN to properly handle SubmitProposal requests.
category: feature
ticket: #3108
feature_flag: json_requests
Add `WithEnforceJSON(true)` parameter when `json_requests` feature is enabled in `featureset`.
This is needed for Nimbus BN to properly handle SubmitProposal requests.
category: feature
ticket: #3108
feature_flag: json_requests
🎯 Problem to be solved
The Nimbus beacon node requires JSON-encoded blocks to be submitted via the
/eth/v2/beacon/blocks
endpoint. However, the current implementation of the go-eth2-client library does not support this format for Nimbus, leading to issues when using Nimbus as a beacon node in Kurtosis.🛠️ Proposed solution
--feature-set-enable=json_requests
) in Charon to enable JSON-encoded block submission for Nimbus.The text was updated successfully, but these errors were encountered: