Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] Deployment Challenges #297

Open
salman01zp opened this issue Apr 10, 2023 · 0 comments
Open

[ISSUE] Deployment Challenges #297

salman01zp opened this issue Apr 10, 2023 · 0 comments

Comments

@salman01zp
Copy link
Contributor

salman01zp commented Apr 10, 2023

Overview

These are some of the challenges faced while deploying, primarily related to the having same nonce.

  • Ensure that you use the same nonce across all chains to generate the same deployer contract address.

  • If the deployment fails for one of the chains, follow these steps:

      1. Make the nonce same for all chains by making some transactions. If the nonce difference is too big, given the high transaction fees for Goerli or Arbitrum, it would be better to use a fresh account.
    
      2. Once the nonce is same for all chains, re-run the script to deploy contracts to all chains from the beginning.
    
    
  • Recently started having a consistent issue with deploying to Avalanche and Optimism test net with errors like nonce already used, transaction_replaced. So skipped them from deployment for now
    Error log

Check this notion doc for more details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant