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
I am developing on the main branch. While executing a deposit transaction using Optimism’s EVM, a panic occurs due to an issue with tx_type: “Custom tx not supported.”
Description
When using the Optimism crate and executing load_accounts, the function mainnet::load_accounts is called.
pubfnload_accounts<EvmWiringT:OptimismWiring,SPEC:OptimismSpec>(context:&mutContext<EvmWiringT>,) -> EVMResultGeneric<(),EvmWiringT>{// the L1-cost fee is only computed for Optimism non-deposit transactions.if context.evm.env.tx.tx_type() != OpTransactionType::Deposit{let l1_block_info =
super::L1BlockInfo::try_fetch(&mut context.evm.inner.db,SPEC::OPTIMISM_SPEC_ID).map_err(EVMError::Database)?;// storage l1 block info for later use.*context.evm.chain.l1_block_info_mut() = Some(l1_block_info);}
mainnet::load_accounts::<EvmWiringT,SPEC>(context)// <-}
executing the load_accounts method calls the access_list method
Issue
I am developing on the main branch. While executing a deposit transaction using Optimism’s EVM, a panic occurs due to an issue with tx_type: “Custom tx not supported.”
Description
When using the Optimism crate and executing load_accounts, the function mainnet::load_accounts is called.
executing the load_accounts method calls the access_list method
but during this process, the deposit transaction is matched as a custom transaction when converting it via into,
which causes a panic in the
access_list
function.This seems to be a consistent issue.
Any guidance or support would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: