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: Add EP0.7 audited MSCA contracts testnet deployment logs and update scripts #6

Merged

Conversation

ashutosh-ukey
Copy link
Contributor

@ashutosh-ukey ashutosh-ukey commented Sep 26, 2024

Summary

Update deployment scripts and add deployment logs for audited MSCA EP0.7 contracts.

Checklist

  • Did you add new tests and confirm all tests pass? (yarn test)
  • Did you update relevant docs? (docs are found in the docs folder)
  • Do your commits follow the Conventional Commits standard?
  • Does your PR title also follow the Conventional Commits standard?
  • If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
  • Did you run lint (yarn lint) and fix any issues?
  • Did you run formatter (yarn format:check) and fix any issues (yarn format:write)?

Testing

All the script changes were tested locally in the process of deploying the new contracts. Any edits made during the PR review process were tested by simulating the script and verifying that there were no errors. I tested the cast send commands on a local networks and verified that contracts were deployed at the same addresses as those deployed using the forge script command.

@ashutosh-ukey ashutosh-ukey changed the title feat: add EP0.7 audited MSCA contracts deployment logs and update scripts feat: Add EP0.7 audited MSCA contracts deployment logs and update scripts Sep 26, 2024
.env.example Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@ashutosh-ukey ashutosh-ukey force-pushed the deploy-ep0.7-audited-MSCA-contracts branch from cb52582 to 7d1e1ea Compare September 26, 2024 21:42
.env.example Outdated Show resolved Hide resolved
@ashutosh-ukey ashutosh-ukey force-pushed the deploy-ep0.7-audited-MSCA-contracts branch from 383e633 to 8d75ec8 Compare September 27, 2024 17:02
.env.example Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
script/000_ContractAddress.sol Show resolved Hide resolved
@ashutosh-ukey ashutosh-ukey changed the title feat: Add EP0.7 audited MSCA contracts deployment logs and update scripts feat: Add EP0.7 audited MSCA contracts testnet deployment logs and update scripts Sep 27, 2024
@huaweigu
Copy link
Contributor

LGTM. @dlim-circle could you please take another look at your convenience?

Copy link
Contributor

@dlim-circle dlim-circle left a comment

Choose a reason for hiding this comment

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

@ashutosh-ukey Think you asked previously, did you also wanted to deploy the mainnet contracts for plugins that doesn't need owners?

@huaweigu huaweigu merged commit 4294cc2 into circlefin:master Sep 27, 2024
6 checks passed
huaweigu pushed a commit that referenced this pull request Sep 27, 2024
🤖 I have created a release *beep* *boop*
---


## 1.0.0 (2024-09-27)


### Features

* Add EP0.7 audited MSCA contracts testnet deployment logs and update
scripts
([#6](#6))
([4294cc2](4294cc2))
* Deployed and Verified SponsorPaymaster on Testnet
([#2](#2))
([9cdf6dc](9cdf6dc))


### Miscellaneous Chores

* **ci:** Minor refactor to release workflow
([#4](#4))
([01ece52](01ece52))
* **style**: organize imports
([#1](#1))
([1d2d26c](1d2d26c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
@ashutosh-ukey
Copy link
Contributor Author

@dlim-circle I will deploy those ones locally and update our internal docs, but I was planning on bunching together all of the mainnet MSCA audited contract deployment logs into one big PR later.

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