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

Feat/readme #36

Merged
merged 4 commits into from
Jun 26, 2024
Merged

Feat/readme #36

merged 4 commits into from
Jun 26, 2024

Conversation

devlancer412
Copy link
Contributor

No description provided.

@devlancer412
Copy link
Contributor Author

@chimera-defi Could you check readme for deploy and verify tasks?

You can run the deploy script by specifying tags for the deploy script:

```bash
yarn deploy:sepolia --tags minter
Copy link
Owner

Choose a reason for hiding this comment

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

hmm looks like running the underlying with tags minter seems to err out

$ npx hardhat deploy --network localhost --tags minter
TypeError: Cannot read properties of undefined (reading 'address') at /04_minter.ts:24:23

same with payment splitter.
wsgeth and sgeth seem to deploy properly and addresses get reused correctly though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's because deploy script uses second wallet address as mutisig address

const splitterAddresses = [accounts.deployer.address, accounts.multiSig.address, wsgEth.target];

namedAccounts: {

There are two cases can fix this.

  • don't use named account for deploy script and use static address(but named accounts provides some benefits for testing and automation).
  • we can use mnemonic or can use multiple private keys for deployment in hardhat config

Copy link
Owner

Choose a reason for hiding this comment

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

hmm, lets do what we used to do in hardhat config and use the default anvil private key for the default address? and make it clear what is expected from the script user to get it to work?

on mainnet, we wont have the priv key of the multisig as itll be a gnosis safe, but we can execute txs through it, and ideally we deploy everything first, then transfer anything needed to the multisig

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah. maybe, let me change multiSig address to constant

Copy link
Contributor Author

@devlancer412 devlancer412 Jun 25, 2024

Choose a reason for hiding this comment

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

Used constant multisig address. Please check deploy script now. @chimera-defi

@chimera-defi chimera-defi merged commit 6d1365a into chimera-defi:main Jun 26, 2024
1 check passed
@devlancer412
Copy link
Contributor Author

@chimera-defi Could you kindly check tg?

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