Skip to content

Conversation

@nicholaspai
Copy link
Member

@nicholaspai nicholaspai commented May 8, 2024

  • This PR deploys all new CCTP SpokePools (Polygon, Base, Arbitrum, Optimism) as well as other spoke pools (ZkSync, Linea, Ethereum) so that they all have the same fillDeadlineBuffer as implemented here.
    - Note I have not been able to verify the Mainnet with the verify task that uses solc-json files. I've tried cleaning out the dependencies folder, updating solc to 0.8.25, updating hardhat-verify, all to no avail. So currently the adapters are deployed and verified as flattened contracts that I deployed from Remix. This is not as safe as deploying with solc-json since we can't easily verify the code matches what's in the repo. Therefore, this PR contains the flattened contracts for now This worked after waiting some time and re-trying. I also made sure to clean out all deps and build/cache files

New CCTP-enabledSpokePools:

New CCTP-enabled L1 Adapters

New non-CCTP migrated SpokePools:

@nicholaspai nicholaspai marked this pull request as ready for review May 9, 2024 15:15
Copy link
Contributor

@mrice32 mrice32 left a comment

Choose a reason for hiding this comment

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

Looks good! Just one question

"HubPool": { "address": "0xc186fA914353c44b2E33eBE05f21846F1048bEda", "blockNumber": 14819537 },
"LpTokenFactory": { "address": "0x7dB69eb9F52eD773E9b03f5068A1ea0275b2fD9d", "blockNumber": 14704307 },
"Optimism_Adapter": { "address": "0xAd1b0a86c98703fd5F4E56fff04F6b2D9b9f246F", "blockNumber": 17944184 },
"Optimism_Adapter": { "address": "0xb3a4e39F0CD9aBAc5d866f023C18e73224667Fee", "blockNumber": 19833066 },
Copy link
Contributor

Choose a reason for hiding this comment

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

Since polygon will be upgraded ahead of the others, do we need to merge that one first (and release the package) before the others?

Copy link
Member Author

Choose a reason for hiding this comment

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

technically yes

@@ -1,5 +1,5 @@
{
"address": "0x53dcC21887d54f41B049724b73a2195CE7343873",
"address": "0x7a4Ba159A34c1C49F712B5079a28121bbA0BFb7f",
Copy link
Contributor

Choose a reason for hiding this comment

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

Not specifically related to this PR: one thing that would be cool: if we could have a way to verify that a deployed address matches the compiled code from the repo.

Might be tricky because the bytecode depends on constructor args, but would be cool to have an automation to do this because it's essentially impossible to verify manually.

Copy link
Member Author

Choose a reason for hiding this comment

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

there's a way to do this with forge it hink

Copy link
Contributor

Choose a reason for hiding this comment

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

OOC will we always need to maintain this spoke & should we update it accordingly on Boba?

Copy link
Member Author

Choose a reason for hiding this comment

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

hmm i don't think we need to do anything as long as the pool rebalance routes are disabled for this route and the dataworker doesn't propose bundles with boba

Copy link
Member Author

Choose a reason for hiding this comment

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

we might want to brick the contract somehow

@nicholaspai nicholaspai merged commit 57edc75 into master May 15, 2024
@nicholaspai nicholaspai deleted the npai/polygon-cctp branch May 15, 2024 16:07
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.

4 participants