You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The present implementation only fills the block with the transactions, but it doesn’t build it and submit it to the relay. While building a block from the filled transaction is trivial, submitting a valid block to the relay involves obtaining certain beacon chain arguments that are challenging to fetch from the Forge environment.
To build blocks from MEVM, the object BuildBlockArgs needs to be sent to the suave-execution-geth node. Some of the object's arguments can only be obtained by subscribing to events emitted by a private beacon node, which complicates obtaining the necessary arguments for building a block from Forge. An approach to mitigate this issue is to capture these arguments inside suave-geth instead.
The text was updated successfully, but these errors were encountered:
The present implementation only fills the block with the transactions, but it doesn’t build it and submit it to the relay. While building a block from the filled transaction is trivial, submitting a valid block to the relay involves obtaining certain beacon chain arguments that are challenging to fetch from the Forge environment.
To build blocks from MEVM, the object BuildBlockArgs needs to be sent to the suave-execution-geth node. Some of the object's arguments can only be obtained by subscribing to events emitted by a private beacon node, which complicates obtaining the necessary arguments for building a block from Forge. An approach to mitigate this issue is to capture these arguments inside suave-geth instead.
The text was updated successfully, but these errors were encountered: