I can't bridge custom base token as a first transaction after deploying new ecosystem and zkchain on the sepolia testnet.

[sugarbody]

Team or Project

No response

ZK chain

Revo

Environment

Testnet

L2 block number

No response

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

I deployed a new ecosystem and zkChain on the Sepolia network. However, after deployment, I attempted to bridge a custom base token as the first transaction, but encountered an error. Despite multiple deployments and extensive troubleshooting, I have yet to resolve the issue. This matter is urgent and requires an immediate solution.

L1 Transactions
https://sepolia.etherscan.io/tx/0xdfd2f9fac6a0f42603fa41c442dff20bed9b99c9fd886be4a907078206206a02
https://sepolia.etherscan.io/tx/0x13e5b2d23d41fca1714f6a48dd3b58e29fde01337972fde267f7c3163e494d36

Caused by:
VM must not fail when finalizing block: Halt {
reason: UnexpectedVMBehavior(
"Failed to publish pubdata via L1Messenger for: Error function_selector = 0x, data = 0x",
),
}

2025-03-10T15:49:36.952362Z INFO zksync_state_keeper::keeper: There is a new upgrade tx to be executed in batch #1 2025-03-10T15:49:36.958884Z DEBUG access_storage{l1_batch_number=L1BatchNumber(0)}: zksync_state::storage_factory: Catching up RocksDB synchronously 2025-03-10T15:49:36.964806Z DEBUG access_storage{l1_batch_number=L1BatchNumber(0)}: zksync_state::rocksdb: Loading storage for l1 batch number 0 2025-03-10T15:49:36.964830Z INFO access_storage{l1_batch_number=L1BatchNumber(0)}: zksync_state::rocksdb: Secondary storage for L1 batch #0 initialized, size is 76 2025-03-10T15:49:36.964959Z DEBUG access_storage{l1_batch_number=L1BatchNumber(0)}: zksync_state::storage_factory: Using RocksDB-based storage rocksdb_l1_batch_number=1 2025-03-10T15:49:36.965007Z INFO zksync_vm_executor::batch::factory: Starting executing L1 batch #1 2025-03-10T15:49:37.430179Z WARN zksync_base_token_adjuster::base_token_ratio_provider: No latest price found in the database. Using default ratio. 2025-03-10T15:49:37.991216Z DEBUG process_l1_batch{l1_batch=1}:wait_for_new_l2_block_params{l1_batch=1 l2_block=1}: zksync_health_check: Changed health of state_keeperfrom {"status":"ready","details":{"l1_batch":1,"next_l2_block":1,"prev_l2_block_hash":"0xe8e77626586f73b955364c7b4bbf0bb7f7685ebd40e852b164633a4acbd3244c","prev_l2_block_timestamp":0}} to {"status":"ready","details":{"l1_batch":1,"next_l2_block":2,"prev_l2_block_hash":"0x2705502820ad493d4e9eca3271fe31405786bf4ce7af3d72ed8d9cb8b1a47634","prev_l2_block_timestamp":1741621776}} 2025-03-10T15:49:37.991257Z INFO zksync_state_keeper::io::seal_logic: Sealing L2 block 1 with timestamp 2025-03-10 15:49:36 UTC (L1 batch 1) with 2 (1 L2 + 1 L1) txs, 36 events 2025-03-10T15:49:38.312895Z INFO zksync_state_keeper::io::seal_logic: Transaction spent >600s in mempool before being included in an L2 block tx_hash="7fd7695b36116881c0cd7fd72010b0c68cfab0d9642fdf5d3a75da2db5b4ab82" inclusion_delay_ms=2185646 received_timestamp_ms=1741619592666 2025-03-10T15:49:39.400409Z INFO zksync_node_framework::service: Task state_keeper/l2_block_sealer finished 2025-03-10T15:49:39.400435Z INFO zksync_node_framework::service: One of the task has exited, shutting down the node 2025-03-10T15:49:39.400463Z INFO zksync_contract_verification_server: Stop signal received, contract verification server is shutting down 2025-03-10T15:49:39.400541Z INFO zksync_contract_verification_server: Contract verification handler server shut down 2025-03-10T15:49:39.400558Z INFO zksync_house_keeper::periodic_job: Stop signal received; periodic job L1BatchMetricsReporter is shut down 2025-03-10T15:49:39.400561Z DEBUG zksync_health_check: Changed health ofhttp_apifrom {"status":"ready"} to {"status":"shutting_down"} 2025-03-10T15:49:39.400574Z INFO zksync_node_api_server::web3: Stop signal received, HTTP JSON-RPC server is shutting down 2025-03-10T15:49:39.400592Z INFO zksync_node_api_server::healthcheck: Stop signal received, healthcheck server is shutting down 2025-03-10T15:49:39.400675Z INFO zksync_node_api_server::healthcheck: Healthcheck server shut down 2025-03-10T15:49:39.400711Z INFO zksync_node_api_server::execution_sandbox: VM concurrency limiter closed 2025-03-10T15:49:39.400720Z INFO zksync_proof_data_handler: Stop signal received, proof data handler server is shutting down 2025-03-10T15:49:39.400726Z INFO zksync_node_framework::implementations::layers::postgres: Stop signal received, Postgres metrics scraping is shutting down 2025-03-10T15:49:39.400741Z DEBUG zksync_health_check: Changed health ofws_apifrom {"status":"ready"} to {"status":"shutting_down"} 2025-03-10T15:49:39.400746Z INFO zksync_node_api_server::web3: Stop signal received, WS JSON-RPC server is shutting down 2025-03-10T15:49:39.400757Z INFO zksync_circuit_breaker: received a stop signal; circuit breaker is shut down 2025-03-10T15:49:39.400764Z INFO zksync_proof_data_handler: Proof data handler server shut down 2025-03-10T15:49:39.400764Z INFO zksync_base_token_adjuster::base_token_ratio_provider: Stop signal received, base_token_ratio_provider is shutting down 2025-03-10T15:49:39.400783Z DEBUG zksync_health_check: Changed health ofprometheus_exporterfrom {"status":"ready"} to {"status":"shut_down"} 2025-03-10T15:49:39.400789Z INFO zksync_metadata_calculator::updater: Stop signal received, metadata_calculator is shutting down 2025-03-10T15:49:39.400801Z DEBUG zksync_health_check: Changed health oftreefrom {"status":"ready","details":{"leaf_count":75,"min_l1_batch_number":0,"mode":"full","next_l1_batch_number":1,"root_hash":"0x025f5dbd1ac1b87be9d80858b70c10146aca7cdd4a20371723d988b9ba7a1b74","stage":"main_loop"}} to {"status":"shut_down"} 2025-03-10T15:49:39.400847Z DEBUG zksync_health_check: Changed health ofstate_keeperfrom {"status":"ready","details":{"l1_batch":1,"next_l2_block":2,"prev_l2_block_hash":"0x2705502820ad493d4e9eca3271fe31405786bf4ce7af3d72ed8d9cb8b1a47634","prev_l2_block_timestamp":1741621776}} to {"status":"shut_down"} 2025-03-10T15:49:39.405897Z INFO zksync_commitment_generator: Stop signal received, commitment generator is shutting down 2025-03-10T15:49:39.405949Z DEBUG zksync_health_check: Changed health ofcommitment_generatorfrom {"status":"ready"} to {"status":"shut_down"} 2025-03-10T15:49:39.407061Z INFO zksync_vm_runner::process: VM runner was interrupted 2025-03-10T15:49:39.409164Z INFO zksync_vm_runner::storage:StorageSyncTaskwas interrupted 2025-03-10T15:49:39.419502Z INFO zksync_vm_runner::process: VM runner was interrupted 2025-03-10T15:49:39.430166Z INFO zksync_node_api_server::web3::pubsub: Stop signal received, pubsub_tx_notifier is shutting down 2025-03-10T15:49:39.432658Z INFO zksync_vm_runner::storage:StorageSyncTaskwas interrupted 2025-03-10T15:49:39.434100Z INFO zksync_vm_runner::output_handler:ConcurrentOutputHandlerFactoryTaskwas interrupted 2025-03-10T15:49:39.436287Z INFO zksync_state_keeper::mempool_actor: Stop signal received, mempool is shutting down 2025-03-10T15:49:39.445562Z INFO zksync_vm_runner::output_handler:ConcurrentOutputHandlerFactoryTaskwas interrupted 2025-03-10T15:49:39.493052Z INFO zksync_node_api_server::web3::pubsub: Stop signal received, pubsub_logs_notifier is shutting down 2025-03-10T15:49:39.495731Z INFO zksync_node_api_server::web3::pubsub: Stop signal received, pubsub_block_notifier is shutting down 2025-03-10T15:49:39.501049Z INFO zksync_eth_watch: Stop signal received, eth_watch is shutting down 2025-03-10T15:49:39.822427Z INFO zksync_eth_sender::eth_tx_manager: Stop signal received, eth_tx_manager is shutting down 2025-03-10T15:49:39.822508Z DEBUG zksync_health_check: Changed health ofeth_tx_managerfrom {"status":"ready"} to {"status":"shut_down"} 2025-03-10T15:49:39.901513Z INFO zksync_node_api_server::web3: Stopping serving new HTTP traffic 2025-03-10T15:49:39.901579Z INFO zksync_node_api_server::web3: Stopping serving new WS traffic 2025-03-10T15:49:39.901702Z DEBUG zksync_health_check: Changed health ofhttp_apifrom {"status":"shutting_down"} to {"status":"shut_down"} 2025-03-10T15:49:39.901731Z INFO zksync_node_api_server::web3: HTTP JSON-RPC server stopped 2025-03-10T15:49:39.902308Z DEBUG zksync_health_check: Changed health ofws_apifrom {"status":"shutting_down"} to {"status":"shut_down"} 2025-03-10T15:49:39.902322Z INFO zksync_node_api_server::web3: WS JSON-RPC server stopped 2025-03-10T15:49:40.388240Z INFO zksync_eth_sender::eth_tx_aggregator: Stop signal received, eth_tx_aggregator is shutting down 2025-03-10T15:49:40.389347Z DEBUG zksync_health_check: Changed health ofeth_tx_aggregator` from {"status":"ready"} to {"status":"shut_down"}
2025-03-10T15:49:41.777735Z INFO zksync_node_fee_model::l1_gas_price::gas_adjuster: Stop signal received, gas_adjuster is shutting down
2025-03-10T15:49:41.777895Z INFO zksync_node_framework::service: Task sigint_handler finished
2025-03-10T15:49:41.777925Z INFO zksync_node_framework::service: Task circuit_breaker_checker finished
2025-03-10T15:49:41.777932Z INFO zksync_node_framework::service: Task healthcheck_server finished
2025-03-10T15:49:41.777938Z INFO zksync_node_framework::service: Task prometheus_exporter finished
2025-03-10T15:49:41.777943Z INFO zksync_node_framework::service: Task gas_adjuster finished
2025-03-10T15:49:41.777949Z INFO zksync_node_framework::service: Task contract_verification_api finished
2025-03-10T15:49:41.777954Z INFO zksync_node_framework::service: Task metadata_calculator finished
2025-03-10T15:49:41.777959Z INFO zksync_node_framework::service: Task eth_watch finished
2025-03-10T15:49:41.777965Z INFO zksync_node_framework::service: Task eth_tx_aggregator finished
2025-03-10T15:49:41.777984Z INFO zksync_node_framework::service: Task eth_tx_manager finished
2025-03-10T15:49:41.777989Z INFO zksync_node_framework::service: Task base_token_ratio_provider finished
2025-03-10T15:49:41.777996Z INFO zksync_node_framework::service: Task oneshot_runner finished
2025-03-10T15:49:41.778001Z INFO zksync_node_framework::service: Task state_keeper/mempool_fetcher finished
2025-03-10T15:49:41.778009Z ERROR zksync_node_framework::service: Task state_keeper failed: state_keeper failed

Caused by:
VM must not fail when finalizing block: Halt {
reason: UnexpectedVMBehavior(
"Failed to publish pubdata via L1Messenger for: Error function_selector = 0x, data = 0x",
),
}
2025-03-10T15:49:41.778034Z INFO zksync_node_framework::service: Task l1_batch_metrics_reporter finished
2025-03-10T15:49:41.778040Z INFO zksync_node_framework::service: Task postgres_metrics_scraping finished
2025-03-10T15:49:41.778045Z INFO zksync_node_framework::service: Task commitment_generator finished
2025-03-10T15:49:41.778050Z INFO zksync_node_framework::service: Task proof_data_handler finished
2025-03-10T15:49:41.778060Z INFO zksync_node_framework::service: Task vm_runner/protective_reads_writer finished
2025-03-10T15:49:41.778066Z INFO zksync_node_framework::service: Task vm_runner/protective_reads_writer/storage_sync finished
2025-03-10T15:49:41.778072Z INFO zksync_node_framework::service: Task vm_runner/protective_reads_writer/output_handler finished
2025-03-10T15:49:41.778077Z INFO zksync_node_framework::service: Task vm_runner/basic_witness_input_producer/output_handler finished
2025-03-10T15:49:41.778085Z INFO zksync_node_framework::service: Task vm_runner/basic_witness_input_producer/storage_sync finished
2025-03-10T15:49:41.778090Z INFO zksync_node_framework::service: Task vm_runner/bwip finished
2025-03-10T15:49:41.778095Z INFO zksync_node_framework::service: Task vm_concurrency_barrier_task finished
2025-03-10T15:49:41.778099Z INFO zksync_node_framework::service: Task postgres_storage_caches finished
2025-03-10T15:49:41.778103Z INFO zksync_node_framework::service: Task mempool_cache_update_task finished
2025-03-10T15:49:41.778106Z INFO zksync_node_framework::service: Task web3_http_server finished
2025-03-10T15:49:41.778111Z INFO zksync_node_framework::service: Task api_task_garbage_collector finished
2025-03-10T15:49:41.778115Z INFO zksync_node_framework::service: Task api_sealed_l2_block_updater_task finished
2025-03-10T15:49:41.778119Z INFO zksync_node_framework::service: Task bridge_addresses_updater_task finished
2025-03-10T15:49:41.778131Z INFO zksync_node_framework::service: Task web3_ws_server finished
2025-03-10T15:49:41.778136Z INFO zksync_node_framework::service: Task api_task_garbage_collector finished
2025-03-10T15:49:41.778140Z INFO zksync_node_framework::service: Task api_sealed_l2_block_updater_task finished
2025-03-10T15:49:41.778144Z INFO zksync_node_framework::service: Task bridge_addresses_updater_task finished
2025-03-10T15:49:41.778189Z INFO zksync_storage::db: All the RocksDB instances are dropped
2025-03-10T15:49:41.778230Z INFO zksync_node_framework::service: Shutdown hook rocksdb_terminaton completed
2025-03-10T15:49:41.778269Z INFO zksync_storage::db: All the RocksDB instances are dropped
2025-03-10T15:49:41.778303Z INFO zksync_node_framework::service: Shutdown hook rocksdb_terminaton completed
2025-03-10T15:49:41.778312Z INFO zksync_node_framework::service: Exiting the service
Error: One or more tasks failed: ["Task state_keeper failed: state_keeper failed: VM must not fail when finalizing block: Halt {\n reason: UnexpectedVMBehavior(\n "Failed to publish pubdata via L1Messenger for: Error function_selector = 0x, data = 0x",\n ),\n}"]
│
■ Command failed to run
│
■ Status:
│ exit status: 1
│ Stdout:
│
│
│ Stderr:
│
│
■ Failed to start server
│
▲ 0: Command failed to run: cargo run --manifest-path ./core/Cargo.toml --release --bin zksync_server -- --genesis-path /root/revo_devb/chains/revoc/configs/genesis.yaml --wallets-path /root/revo_devb/chains/revoc/configs/wallets.yaml --config-path /root/revo_devb/chains/revoc/configs/general.yaml --secrets-path /root/revo_devb/chains/revoc/configs/secrets.yaml --contracts-config-path /root/revo_devb/chains/revoc/configs/contracts.yaml --components=api,tree,eth,state_keeper,housekeeper,commitment_generator,da_dispatcher,proof_data_handler,vm_runner_protective_reads,vm_runner_bwip
│
│ 1: Command failed to run: cargo run --manifest-path ./core/Cargo.toml --release --bin zksync_server -- --genesis-path /root/revo_devb/chains/revoc/configs/genesis.yaml --wallets-path /root/revo_devb/chains/revoc/configs/wallets.yaml --config-path /root/revo_devb/chains/revoc/configs/general.yaml --secrets-path /root/revo_devb/chains/revoc/configs/secrets.yaml --contracts-config-path /root/revo_devb/chains/revoc/configs/contracts.yaml --components=api,tree,eth,state_keeper,housekeeper,commitment_generator,da_dispatcher,proof_data_handler,vm_runner_protective_reads,vm_runner_bwip`

Repo Link (Optional)

No response

Additional Details

No response

[vasyl-ivanchuk]

Hey @sugarbody 👋 ,

Please check this GH discussion where the same problem has been resolved. Most of the time, such errors come from issues that occurred during the chain deployment.

If it's still unclear, could you please try deploying the same era version to the local reth to see if it works?

[sugarbody]

Could you tell me how to calculate the hash of genesis file?

[sugarbody]

I checked it. It was what I tried many times. I had an root hash and batch_commitment mismatch problem but I solved it successfully. However, when I was bridging eth(didn't set custom base token), it is working well but custom token case.

[vasyl-ivanchuk]

It might happen if the fee is incorrect. Please try setting the fee 15% higher than the estimated one.