Transactions are getting send but not showing up on Block Explorer and bridged token are not getting received

[FaizanNehal]

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 created my own zksync ecosystem using the Zk Stack guide.
When I am bridging my ETH from L1 to L2, the transaction is getting successfully send but I ma not rceeiving the tokens on my Layer-2, also the transaction is not showing up on my block explorer.
The wallet on block explorer is also showing it as empty.

Repo Link (Optional)

No response

Additional Details

I created the ecosystem using the command zk_inception ecosystem create then initialized it with zk_inception ecosystem init and then finally ran the server using zk_inception server
After that I ran the portal with the command zk_inception portal
Then I initialized and ran the block explorer using the commands zk_inception explorer init, zk_inception explorer run-backend and zk_inception explorer run.
The screenshots from my terminals are below.

Then I bridge my tokens using the portal. I used the rich wallets provided by matter labs.

After more than 15 minutes when transaction time is finished, I am checking the transaction in my block explorer and it is showing transaction not found error.

and funds are not getting arrived in my wallet

The containers that are running in my docker are as below.

[alhenaai[bot]]

It seems like you've followed the correct steps to set up your ZKsync ecosystem and initiate bridging from L1 to L2. However, the issue with transactions not appearing on the block explorer and tokens not being received on L2 could be due to several reasons:

1. Configuration Issues: Ensure that all configurations in your contracts.yaml and ZkStack.yaml files are correctly set, especially the base_token.address and l1.base_token_addr. These addresses must match the actual contracts deployed on L1 and L2.

2. Server and Explorer Sync: Verify that your block explorer service is properly connected to your L2 node. If the explorer is not synced with the L2 node, it won't display transactions. You might need to check the logs for both the explorer backend and the L2 node to identify any connectivity or syncing issues.

3. Transaction Bridging Logs: Check the logs for the bridging process. There might be errors or warnings that could give more insight into why the bridging isn't successful. Look for any errors related to token bridging or transaction processing in the logs of the services you've started.

4. Network Issues: Since you are on a testnet, network instability or delays could also be a factor. Ensure that your network settings allow for proper communication between all components of your ecosystem.

5. Docker Container Health: Ensure all relevant Docker containers are running without issues. A failing container could disrupt the services necessary for successful transaction processing and bridging.

If after checking these areas the issue persists, you might want to restart the ecosystem and ensure all services are initialized in the correct order as per the setup guide. If necessary, redeploy the contracts and reinitialize the services to ensure a clean state.

For further detailed troubleshooting, you might want to consult the logs more closely or reach out for support with specific logs and error messages that you encounter.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[FaizanNehal]

The number of transactions on my block explorer is also not getting updated.

I am also trying to send the transaction from CLI but it is not moving forward from this line.

[dutterbutter]

Hey @FaizanNehal 👋

First and foremost, great post here man! Screenshots are awesome help! 💯 Before debugging with the below steps, if you've spun down your containers I suggest clearing out all old cache and deleting the containers before starting fresh.

Can you confirm you are able to make request to each of your running chains API? I just want to make sure the chains are up and running as expected. To do so we can first check if the L2 chain is running at port 3050:

curl --request POST \
  --url http://127.0.0.1:3050 \
  --header 'Content-Type: application/json' \
  --data '{
      "jsonrpc": "2.0",
      "id": 1,
      "method": "zks_L1ChainId",
      "params": []
    }'

This should respond with the ChainId of your L1. We can also make a similar request to 8545:

curl --request POST \
  --url http://127.0.0.1:8545 \
  --header 'Content-Type: application/json' \
  --data '{
      "jsonrpc": "2.0",
      "id": 1,
      "method": "eth_chainId",
      "params": []
    }'

Again should respond with the chainID.

If those are correctly responding to requests, we can also peak into the chains logs to see if we any issue when you initiate a transaction.

To do so you can either use the desktop app (as you have depicted above) by clicking into each container, or in your terminal docker ps to get the container ID and then docker logs -f <container_id_or_name>. Once you have the docker logs available go ahead and try initiating the tx again and see if you are able to view any error logs that can help us debug. Please post any debug logs you may see.

[FaizanNehal]

Hi @dutterbutter

Upon running the commands these are m output. Both the outputs are kind of same, I think I might have a problem here maybe.

L2:

L1:

[FaizanNehal]

Hi @dutterbutter

I think I have figured out what might be the issue here. When I last run my ecosystem the name of chain on my explorer was faizanchain and the chain on portal was testchain.

I re-ran the ecosystem again from zk_inception server command, and now my chain on both explorer and portal are faizanchain.

But now I am getting a different internal error while confirming the transaction. Here it is

I was also getting the same behaviour two days ago, the weird thing is I cannot figure out why I am getting two completely different behaviours very randomly.

[dutterbutter]

It is likely due to old cache / artifacts. However we can peek into the logs our chains so we can see what RPC error we are experiencing.

I would suggest killing the containers (docker kill <containerID>) and then deleting all volumes, images, containers and starting fresh. I am unable to reproduce on my side so apologies I dont have a direct solution here.

[FaizanNehal]

Hi @dutterbutter
I cleared the all the volumes, images and containers from my docker and started it over again. I am getting the same RPC error. Upon sending a transaction there is also no error message that is thrown in the logs in my docker. Here is the screenshot of my logs.

[FaizanNehal]

So I also tried sending the transaction from the CLI and it is working and showing up in the explorer. The only unusual thing here is, in my output the transaction hash is showing as 0x7f7f1ee38199cdbad51c41c0ac329136cc2145adbbbefa8724b44dc41e9cabc2 while in the explorer it is 0x97e4cb108a0577ff151db08633eba17b148eac6597f51961fc9beb22e74d7650.
When I am searching the hash 0x7f7f1ee38199cdbad51c41c0ac329136cc2145adbbbefa8724b44dc41e9cabc2 in explorer, it is showing the not found error.

[dutterbutter]

Very interesting sir 🤔 Let me try to reproduce on my end!

[dutterbutter]

I have not been able to reproduce on my side. My only suggestion at this time is to spin down all docker and terminal instance of the infrastructure, clear any cache and only follow the steps outlined in this tutorial: https://code.zksync.io/tutorials/custom-zk-chain

That is, don't spin up an explorer or portal just yet. Get the basic L1 - L2 infrastructure running as expected and then proceed with the following steps described in the README here and here.

[FaizanNehal]

Hi @dutterbutter
I am able to run it but the transaction hash in explorer and transaction hash in the command line terminal are different. Is this the expected behaviour or something unusual is happening here. sorry for too many questions, I need to do some automations so therefore need to have this step clear.

The portal app is still showing the same error