-
Notifications
You must be signed in to change notification settings - Fork 1.1k
eip7732: enforce self build header signature to point of infinity #4552
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
Conversation
@terencechain, wouldn't the BN still need to cache the payload through the block production lifecycle? so that the cached payload could be used to formulate the envelope right after the beacon block is gossiped? |
ya i think that is correct, i meant between get header and get block call but sounds like there's no way around this so ignore what I said there |
gotcha! and if I'm understanding correctly, this basically kills the need to call a |
604b98d
to
98854c2
Compare
This PR enforces that signed self build's execution payload bid signatures to be point of inf. This decision was made during the EIP-7732 breakout:ethereum/pm#1696. Teams generally agreed that this simplifies the beacon node and validator client workflow by removing an extra call and reducing server/client api implementations, while also eliminating the need for the beacon node to cache the payload through block proposing life cycle