[ZK Stack] - <failed L1 transaction and cannot restart >

[qiwenzhou]

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.74.0

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

I ran a hyperchain in my server.Something wrong went with L1 and my chain server went down.
There is no heavy work in server.

Expected Behavior

run for a long time

Current Behavior

crushed and cannot restart.

Repository Link (if applicable)

No response

Additional Details

No response

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[qiwenzhou]

Look like some disorder happened but dont know how.

[qiwenzhou]

more info:this error happened when server tried to commit batch4,but batch2,3 is uncommitted because of the transaction nonce is too low. Is is possible that this could be the reason? should batch4 wait until batch2,3 committed?

[qiwenzhou]

I used block_reverter and restarted the server. what is next move to fix it according to the log?

[qiwenzhou]

I ran：zk f cargo run --bin block_reverter --release -- rollback-db --l1-batch-number 3 --rollback-postgres --rollback-tree and restart server

[qiwenzhou]

Sadlly there is no documentation for now. I try to write it down here for those i can remember.

1. hyperchain:

1. zk && zk stack init:name,id,sepolia,L1 rpc, erc20 yes,weth no, use my own account to deploy、govern and operator.
2. zk server --components=api,eth,tree,state_keeper,housekeeper,proof_data_handler,commitment_generator
3. zk stack prover-setup && cd prover && ./setup gpu. zk f cargo run --release --bin zksync_prover_fri_gateway;API_PROMETHEUS_LISTENER_PORT=3116 zk f cargo run --release --bin zksync_witness_generator -- --all_rounds;FRI_WITNESS_VECTOR_GENERATOR_PROMETHEUS_LISTENER_PORT=3420 zk f cargo run --release --bin zksync_witness_vector_generator;zk f cargo run --features "gpu" --release --bin zksync_prover_fri;zk f cargo run --release --bin zksync_proof_fri_compressor

2. transactions

1. I used default operator_blobs_eth_addr to bridge 0.01 eth to L2. This may cause "nonce to low" problem, I guess?
2. more deposits after that.
3. several hours later, server crushed. Direct reason is there is failure in L1
   

3. attempts

1. zk f cargo run --bin block_reverter -- clear-failed-transactions
2. zk f cargo run --bin block_reverter --rollback-db --l1_batch_number 2 --rollback_postgres --rollback_tree
3. now when i try to restart server
   

[qiwenzhou]

I changed the default_state_keeper_db_path and ran: k f cargo run --bin block_reverter --release -- rollback-db --l1-batch-number 2 --rollback-postgres --rollback-tree --rollback-sk-cache. Restart the server.
now the error output is :

How to update?

[qiwenzhou]

@bxpana would you please tell me that which db data should i change to fix this error?

[bxpana]

Are you still having issues with this?

[qiwenzhou]

Thanks for asking. This issue is not bothering me for now.