Open artree222 opened 1 month ago
What version was this and what flags were you using?
What version was this and what flags were you using? prysm v5.0.2 geth v1.13.15
how about flags?
I do see a warning here could not find tracked proposer index
which makes me believe there's a chance the fee recipient wasn't set here ( defaulting to beacon node's) but it doesn't look like it was set and resulted in 0x0000000000000000000000000000000000000000
.
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 1.if you get a reorg in the last second you will produce a block without txs 2.if you have a proposer id miss because the FCU with the attributes was never sent. This happens if your validator is not tracked and is unable to send meta data to the local execution client.
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: