Closed sauliusgrigaitis closed 2 years ago
I tested this against a different beacon node and it appears to be sending the correct validator indices:
[{"validator_index":"985","slot":"499121","committee_index":"0","committees_at_slot":"1","is_aggregator":false},{"validator_index":"913","slot":"499128","committee_index":"0","committees_at_slot":"1","is_aggregator":false},...]
which suggests that it is an issue with a different call. Please could you run vouch with the following additional configuration:
eth2client:
log-level: trace
and send over the log file? This should give a bit more information to help track down the issue.
Fixed in #94
We testing Grandine Beacon Node API with Vouch and we found that Vouch doesn't set correct
validator_index
when calling/eth/v1/validator/beacon_committee_subscriptions
:Grandine doesn't like it as it checks that the validator is actually in the committee.