-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscribing to attestation subnets for aggregating does not work correctly #6681
Comments
povi
changed the title
Subscribing to attestation subnets does not work correctly
Subscribing to attestation subnets for aggregating does not work correctly
Dec 11, 2024
povi
added a commit
to povi/lighthouse
that referenced
this issue
Dec 11, 2024
* Prevent scheduled subnet subscriptions from being overwritten by other subscriptions from same subnet with additional scoping by slot
michaelsproul
pushed a commit
to povi/lighthouse
that referenced
this issue
Dec 11, 2024
* Prevent scheduled subnet subscriptions from being overwritten by other subscriptions from same subnet with additional scoping by slot
michaelsproul
pushed a commit
to povi/lighthouse
that referenced
this issue
Dec 11, 2024
* Prevent scheduled subnet subscriptions from being overwritten by other subscriptions from same subnet with additional scoping by slot
povi
added a commit
to povi/lighthouse
that referenced
this issue
Dec 12, 2024
* Prevent scheduled subnet subscriptions from being overwritten by other subscriptions from same subnet with additional scoping by slot
michaelsproul
pushed a commit
to povi/lighthouse
that referenced
this issue
Dec 12, 2024
* Prevent scheduled subnet subscriptions from being overwritten by other subscriptions from same subnet with additional scoping by slot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
If
[/eth/v1/validator/beacon_committee_subscriptions](https://ethereum.github.io/beacon-APIs/#/Validator/prepareBeaconCommitteeSubnet)
request contains multiple aggregator subscriptions to the same attestation subnet at different slots, it respects only the last subscription per subnet:E.g. if there request contains these subscriptions:
it will only subscribe to attestation subnets for aggregating at slots 7 and 12, ignoring slot 2.
The text was updated successfully, but these errors were encountered: