Skip to content

Fix deployment script to use correct deployer address#7

Merged
alexkeating merged 1 commit into
mainfrom
ethereum-deployment
Jul 10, 2025
Merged

Fix deployment script to use correct deployer address#7
alexkeating merged 1 commit into
mainfrom
ethereum-deployment

Conversation

@gettty

@gettty gettty commented Jul 8, 2025

Copy link
Copy Markdown
Contributor

The existing script deploys the contract using the Forge deployment address rather than with the key provided.

@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

Coverage after merging ethereum-deployment into main will be

100.00%

Coverage Report
FileStmtsBranchesFuncsLinesUncovered Lines
src
   QueryTypeStakerFactory.sol100%100%100%100%
   QueryTypeStakingPool.sol100%100%100%100%

Comment thread script/Deploy.s.sol

// Deploy the factory
factory = new QueryTypeStakerFactory(msg.sender, wTokenAddress);
factory = new QueryTypeStakerFactory(deployer, wTokenAddress);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this the same as msg.sender as the deployment is wrapped in a broadcast initialized with the deployer private key

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, if you use msg.sender it deploys with the forge deployment address. I only know this because I had deployed the contract, and it used the wrong owner address, so I had to fix and redeploy it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right right

@alexkeating
alexkeating merged commit b68f7a8 into main Jul 10, 2025
4 checks passed
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.

2 participants