-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CCIP-2155] Smoke Tests Deploy Tokens from non CCIP-Owner Address (#968)
## Motivation Our E2E tests currently deploy and configure all contracts from a single address, `main`. The introduction of Self-Serve Token Pools makes this especially unrealistic. ## Solution * Create a new account, `tokenDeployer` to deploy tokens and pools from by default. The funding for this account is messy, and fixes are tracked by CCIP-2471. * This account can be disabled if certain contract version requirements are not met, or by toggling the `TokenConfig.CCIPOwnerTokens` config option. * The account is created in the form of a new client to handle concurrent contract deployments gracefully. * Each token and pool now has a `OwnerAddress` and `OwnerWallet` field so that they can make `onlyOwner` calls from this wallet. This is by default and for now cannot be modified. * Fund return now also checks for other wallet balances
- Loading branch information
Showing
15 changed files
with
451 additions
and
259 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
"ccip": patch | ||
--- | ||
|
||
#internal Expands the CCIP revert reason script with more ABIs |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.