Skip to content

[RFC] Engine API: Add block value in response to engine_getPayload #307

@allboxes

Description

@allboxes

Currently the CL is blind to the value of the locally built block and therefore, if configured with a builder, will always propose the remotely built block.

In order to allow the CL to intelligently decide between using the local or remote block, the EL could provide the value of its block in its response to engine_getPayload. The EL can be free to determine the value of its block as it sees fit (summing tx fees, checking feeRecipient balance pre/post execution, etc..).

The change will help to ensure validators propose the highest paying block in general, but more importantly will increase the cost of censorship by builders.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions