[Deployment] Universal Deployer

[ScreamingHawk]

Team or Project

Sequence

ZK chain

ZkSync Sepolia

Environment

Testnet

L2 block number

No response

zkSolc Version

xxx

zksync-ethers Version

xxx

Minimal Reproducible Code or Repo Link

https://gist.github.com/Agusx1211/de05dabf918d448d315aa018e2572031

Does this work on other EVMs? (If yes, please list at least 1 of them)

All of them... Mainnet, Optimism, Arbitrum,....

Description of What Your Contract Does

A CREATE2 deployer with a fix address similar to ERC-2470

Additional Details

Hi team. We had an issue deploying one of our deployer contracts. Could you help us debug what caused this issue? https://sepolia.explorer.zksync.io/tx/0xe25e191d75728579e7bc10a220798ce9cc94de5acbc4d2e274f290db52ecfe43#overview

Also, this transaction was a presigned we need to work so we can have a consistent deployment address for the contract. It looks like this failure resulted in a nonce increment. See https://gist.github.com/Agusx1211/de05dabf918d448d315aa018e2572031 (similar flow to ERC-2470).

Is there a way we can revert the nonce of the EOA or force the transaction/deployment to get this contract at the correct address?

---

I suspect this is related to: #870

[dutterbutter]

Hey there 👋

I can investigate further but pre-signed or keyless txs may not work as expected with EVM interpreter due to the gas model differences. Refer here for details. Nonetheless I will look into further to confirm.

[ScreamingHawk]

This still looks to be an issue. Here's another failing transaction with similar parameters: https://sepolia.explorer.zksync.io/tx/0xa50c29117ab8f123fe11b11926e5332fe80987f2b35e09bd5220cc02f941d6aa

[dutterbutter]

Apologies for not following back up here - due to the differences in gas accounting pre-signed transactions will fail. We have other pre-deployed contracts that may be used, however Universal Deployer will need to be included in a future protocol upgrade.

[taylanpince]

@dutterbutter Thank you for the response. Can you let me know what you need to include the universal deployer in the next protocol upgrade? Also if you can give us an ETA that would be great.

[uF4No]

this will be included in protocol v29. See PR that adds this contract.

cc @ScreamingHawk

[ScreamingHawk]

If we can add this to the network as part of a protocol upgrade that would be fantastic! The contract's address is 0x1b926fbb24a9f78dcdd3272f2d86f5d0660e59c0. The EVM bytecode is available on mainnet (and many other networks).

[dutterbutter]

Targeted deployment is v29 (so not next upgrade but the one there after)