-
Notifications
You must be signed in to change notification settings - Fork 997
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
Propose a block that does not contain any transactions #14126
Comments
What version was this and what flags were you using? |
|
how about flags? this could indicate a few things, either your validator was connected to a new beacon node and didn't call the push proposer settings endpoint yet, or a validator was added after the start of the epoch and proposed immediately ( we have some improvements coming to resolve this edge case) this doesn't answer why no transactions were included though ... |
After some conversation with the team, it seems like the transactions missed can happen in 2 situations what must has happened is something has caused your validator to not register with the mev boost/ call the push proposer settings endpoint on the beacon node which missed the tracked validators, because the validator was not registered with the mevbuilder it must have defaulted to local build but local didn't have the validator tracked either resulting the above. The push proposer settings/validator registration happens at the start of every epoch, is there more context on how that validator may have not been updated when being added? |
On the mainnet, we are using the Prysm client to connect to the validator, but the validator proposed a block at slot 9297851 that did not contain any transactions. We hope the community can help us look into the reason for this.
The following is Prysm log:
The following is Geth log:
The following is Mev log:
The text was updated successfully, but these errors were encountered: