Skip to content
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
782 changes: 782 additions & 0 deletions broadcast/multi/101_DeploySponsorPaymaster.s.sol-1754502057/run.json

Large diffs are not rendered by default.

782 changes: 782 additions & 0 deletions broadcast/multi/101_DeploySponsorPaymaster.s.sol-1754510820/run.json

Large diffs are not rendered by default.

715 changes: 536 additions & 179 deletions broadcast/multi/101_DeploySponsorPaymaster.s.sol-latest/run.json

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions script/bytecode-deploy/100_Constants.sol
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ library Constants {

// A list of chains that need to run setup work after deployment. Please adjust the list based on the chain
// expansion needs.
function getChainsForSetup() internal pure returns (string[4] memory) {
return ["base-sepolia", "base", "op-sepolia", "op"];
Copy link
Contributor

Choose a reason for hiding this comment

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

Why removing testnets, op and base?

Copy link
Author

Choose a reason for hiding this comment

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

so I deployed the contracts for celo, sonic, and world testnet first and then celo, sonic, and world mainnet afterwards. that's why you are seeing those three chains in the getChainsForSetup() function

Copy link
Contributor

Choose a reason for hiding this comment

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

Okay, so these are the chains currently being deployed, we might want to consider renaming the function to better reflect that.

Copy link
Author

Choose a reason for hiding this comment

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

@huaweigu yeah that makes sense, do you have any suggestions in mind? I'm thinking maybe something like getCurrentChainsForSetup(), getCurrentDeploymentChains(), etc.

Copy link
Contributor

Choose a reason for hiding this comment

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

getCurrentDeploymentChains sounds good!

function getChainsForSetup() internal pure returns (string[3] memory) {
return ["sonic", "world", "celo"];
}
}

Large diffs are not rendered by default.

Copy link
Contributor

@stigter-circle stigter-circle Aug 7, 2025

Choose a reason for hiding this comment

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

@hieule-circle looks like the content didn't get committed.

Copy link
Author

Choose a reason for hiding this comment

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

@stigter-circle constructor args added

Empty file.
Loading