Skip to content

Conversation

@udpatil
Copy link
Contributor

@udpatil udpatil commented Oct 6, 2025

We don't use the deployer account for anything else outside of deployments, and it is randomly generated anyways, so we can instead use a new deployer for each contract to prevent nonce or account related issues causing timeouts on deployments.

@udpatil udpatil force-pushed the uday/fix-contract-deploy branch from 27ff358 to 9157dea Compare October 6, 2025 20:19
@udpatil udpatil changed the title [CON-92] New deployer for each scenario [CON-92] Fix contract deployment and contract txs Oct 6, 2025
@udpatil udpatil force-pushed the uday/fix-contract-deploy branch from 9157dea to f105108 Compare October 6, 2025 20:19
@udpatil udpatil force-pushed the uday/fix-contract-deploy branch from 7704110 to cbc73f0 Compare October 6, 2025 20:51
@udpatil udpatil force-pushed the uday/fix-contract-deploy branch from cbc73f0 to fdf56af Compare October 6, 2025 20:54
@udpatil udpatil merged commit 052ec99 into main Oct 6, 2025
2 checks passed
@udpatil udpatil deleted the uday/fix-contract-deploy branch October 6, 2025 21:20
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

Successfully merging this pull request may close these issues.

3 participants