Starting at:
Prysm uses SSZ to communicate with the remote builder.
If the remote does not support SSZ (example: Commit Boost) when registering a validator, then the remote returns something like:
Expected request with `Content-Type: application/json`" error="The media type in "Content-Type" header is unsupported, and the request has been rejected. This occurs when a HTTP request supplies a payload in a content-type that the server is not able to handle.
and the validator is not registered to the builder.
As a consequence, all eventual blocks are proposed with the local builder.
Workaround:
Add the --disable-builder-ssz flag to the beacon node.
Fix proposal:
When the remote builder does not support SSZ, then fallback on JSON.
Starting at:
Prysm uses SSZ to communicate with the remote builder.
If the remote does not support SSZ (example: Commit Boost) when registering a validator, then the remote returns something like:
and the validator is not registered to the builder.
As a consequence, all eventual blocks are proposed with the local builder.
Workaround:
Add the
--disable-builder-sszflag to the beacon node.Fix proposal:
When the remote builder does not support SSZ, then fallback on JSON.