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
Discussed in #3977, there are cases in which there could be a forked chain and committees might be different from the point of view of a node. If a state root can be passed in as a request parameter, the ListBeaconCommittees function can verify it and the client can have peace of mind the committees being returned are from the same chain it is requesting. This would be an enhancement on top of #3977,
The text was updated successfully, but these errors were encountered:
What should the behavior be if the state root does not match @shayzluf@nisdas, should we be returning an error or some sort of response that mentions the chain is forked?
Discussed in #3977, there are cases in which there could be a forked chain and committees might be different from the point of view of a node. If a state root can be passed in as a request parameter, the
ListBeaconCommittees
function can verify it and the client can have peace of mind the committees being returned are from the same chain it is requesting. This would be an enhancement on top of #3977,The text was updated successfully, but these errors were encountered: