[Dev Tools] forge script fails because of mismatched nonces

[asselstine]

Team or Project

PoolTogether

ZK chain

Era

Environment

Testnet

Select the Dev Tool you are using

Foundry

Provide the version of the tool (if applicable)

foundryup-zksync 0.3.3, forge-zksync 0.0.8

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

I'm trying to deploy the standard PoolTogether testnet to a zkSync node using our forge script, but it seems to be failing due to a nonce issue.

Repo Link (Optional)

https://github.com/GenerationSoftware/pt-v5-testnet/tree/zksync

Additional Details

Forge script fails on nonce

I'm trying to deploy our PoolTogether testnet configuration to a zkSync node. However, I've been unable to determine why our forge deploy script fails with the zksync tooling. The script seems to skip a few nonces halfway through. The failure message is:

Error: Failed to send transaction

Context:
- After 5 attempts, provider nonce (11) is still behind expected nonce (13).

I've wondered if it's because we have some factory contracts, so I enabled --zk-enable-eravm-extensions but it didn't work.

I've wondered if it's because of contract size limits, but from what I've gathered we're still far under the limit.

I would love some help with this!

Reproduction

1. Clone the PoolTogether Testnet Deploy repo github
2. Checkout the zksync branch
3. Run forge install (this will take some time)
4. Copy .env.example to .env and direnv allow, or whatever tool you use for env vars. This will add the anvil default key to env vars that are consumed by the deploy script.
5. If you've installed forge as forge-zksync you can skip this step, otherwise: go into package.json and change the "deploy:full-zksync" script's forge command from forge-zksync to forge.
6. Open a second terminal and start anvil: either anvil or anvil-zksync dep on how you installed it
7. Back in the first terminal increase the time of the node: cast rpc --rpc-url http://0.0.0.0:8011 evm_increaseTime 100000 (this is needed because of a quirk in our deploy script)
8. Now mine a block: cast rpc --rpc-url http://0.0.0.0:8011 evm_mine
9. Now run the deploy script: npm run deploy:zksyncLocal

You should see it successfully run the first 10 transactions, then die on the 11th with the message:

Error: Failed to send transaction

Context:
- After 5 attempts, provider nonce (11) is still behind expected nonce (13).

Now when you look at the ./broadcast/DeployTestnet.s.sol/260/run-latest.json file you'll see the transaction nonces are like so:

"nonce": "0x0",
"nonce": "0x1",
"nonce": "0x2",
"nonce": "0x3",
"nonce": "0x4",
"nonce": "0x5",
"nonce": "0x6",
"nonce": "0x7",
"nonce": "0x8",
"nonce": "0x9",
"nonce": "0xa",
"nonce": "0xd",
"nonce": "0xe",
...cut these off for brevity

The nonces jump from 0xa to 0xd; what happened to 0xb and 0xc? Seems like a clue to me, though I'm not sure how to investigate further.

[dutterbutter]

Hey @asselstine 👋

Thank you for posting. And a BIG thank you for the well structured post. 🙏

Let me investigate this!

[dutterbutter]

Quick update here: I am able to reproduce on my side, and investigating the nonce issue within deployCore(). I will continue investigating the issue and provide another update once I've zero'd in on the potential issue.

For posterity, I will link relevant foundry-zksync documentation of nonce differences here.

Appreciate the patience while I determine the issue! 🙏

[asselstine]

Thank you @dutterbutter ! This would be a big unlock for us

[asselstine]

Also, if it helps: this behaviour also occurred when attempting to deploy to zkSync Sepolia Testnet

[dutterbutter]

We've identified the issue within forge script and are actively working on resolving for the next release of foundry-zksync. Should be included in 0.0.9. I really appreciate posting the issue so we can make it better and the patience 🙏

[asselstine]

Fantastic! Thank you and the team for fixing this so quickly. We can continue testing now.

[dutterbutter]

Quick update here: We couldnt fit it in 0.0.9 but will be in the next release. Apologies for any inconvenience 🙏

[dutterbutter]

For reference / tracking it will be resolved in these PRs: matter-labs/foundry-zksync#929, and matter-labs/foundry-zksync#923 🙏

[dutterbutter]

Fixed and released in 0.10.0 : https://github.com/matter-labs/foundry-zksync/releases/tag/foundry-zksync-v0.0.10

[asselstine]

Excellent! Thanks @dutterbutter ill give the script another try when I get a chance