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
Currently, if execution_optimistic is false, It is not included in the json response. To make it consistent with the attester and sync duties endpoints, It would be preferred to include it.
As you mentioned and according to the spec the ExecutionOptimistic is assumed to be false when not present. So not really an issue on our side but on the caller side...
Being consistent with the other endpoints could be considered a good reason so I guess it's ok to include it in any case
As you mentioned and according to the spec the ExecutionOptimistic is assumed to be false when not present. So not really an issue on our side but on the caller side... Being consistent with the other endpoints could be considered a good reason so I guess it's ok to include it in any case
Yup, I agree. I wouldn't have changed it, but then saw for the other endpoints is required field so decided to be consistent.
Currently, if
execution_optimistic
is false, It is not included in the json response. To make it consistent with the attester and sync duties endpoints, It would be preferred to include it.https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/ValidatorRequiredApi/getProposerDuties
The text was updated successfully, but these errors were encountered: