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
This has resulted in a workaround in this codebase:
read deposit transactions from the payload passed to the engine API from op-node
use anvil_setBalance to increase the balance, according to the deposit tx's mint value
use anvil_impersonateAccount + eth_sendTransaction to send the deposit transaction as a legacy tx in anvil
op-node also expects deposit transactions to be returned on the RPC, so we also:
rewrite any requests that include the deposit tx hash, and replace them with the hash of the legacy tx we created
rewrite any responses that include the legacy tx, and replace them with the deposit tx
This is hacky and flaky. The ideal path is to upstream support for op-stack deposit transactions in anvil itself (probably behind a flag). This would mean we submit deposit txs directly to anvil, and remove the request / response rewriting.
The text was updated successfully, but these errors were encountered:
anvil currently does not support the op-stack's deposit transaction.
This has resulted in a workaround in this codebase:
anvil_setBalance
to increase the balance, according to the deposit tx'smint
valueanvil_impersonateAccount
+eth_sendTransaction
to send the deposit transaction as a legacy tx in anvilop-node
also expects deposit transactions to be returned on the RPC, so we also:This is hacky and flaky. The ideal path is to upstream support for op-stack deposit transactions in anvil itself (probably behind a flag). This would mean we submit deposit txs directly to anvil, and remove the request / response rewriting.
The text was updated successfully, but these errors were encountered: