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
fix: update builder mergemock sim with builder block assertions #5432
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
8cfc530
to
8fa11b3
Compare
await new Promise<void>((resolve, _reject) => { | ||
bn.chain.emitter.on(routes.events.EventType.block, async (blockData) => { | ||
const {data: fullOrBlindedBlock} = (await bn.api.beacon.getBlockV2(blockData.block).catch((_e) => null)) ?? {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there's a block event there must be a block available in the API right? This catch all to null seems dangerous
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is to just update the stats, but nevertheless removed the catch 👍
b49d50f
to
6dd830e
Compare
🎉 This PR is included in v1.9.0 🎉 |
Previously builder sim was running without any validations.
Modified the mergemock builder interaction to enable differentiating by fee recipient and use that to add engine and builder block assertions