-
Notifications
You must be signed in to change notification settings - Fork 613
Update implementations #8334
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
Merged
+9
−4
Merged
Update implementations #8334
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 @@ | ||
| --- | ||
| "thirdweb": patch | ||
| --- | ||
|
|
||
| Update implementations |
This file contains hidden or 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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify that the updated WETH addresses are the canonical wrapped ETH contracts.
The WETH contract addresses for chains 232 and 37111 have been updated. Since WETH is a critical infrastructure token, confirm these addresses point to the official/canonical WETH implementations for these chains.
Run the following script to verify the WETH contract addresses:
Also applies to: 40-40
🏁 Script executed:
Length of output: 455
I need to identify what chains these are and verify the WETH addresses. Let me search for information about these chains and their canonical WETH contracts.
I need to clarify what chains 232 and 37111 represent to properly verify these WETH addresses.
Based on my web searches, Lens is a Layer 2 blockchain that is built using zkSync's ZK Stack, and Chain 232 corresponds to Lens Network. However, I haven't been able to identify what chain 37111 represents. Let me search the codebase to understand the context better and verify these addresses.
Review requires manual verification — Chain 37111 identity is not readily identifiable via web search.
I've verified that Lens is a Layer 2 blockchain that is built using zkSync's ZK Stack, confirming Chain 232 is Lens Network. However, I cannot definitively identify Chain 37111 through publicly available information. Additionally, I was unable to locate the specific canonical WETH addresses for these chains to verify that the provided addresses are correct implementations.
🏁 Script executed:
Length of output: 5836
Now I understand the context better. Chain 37111 is Lens Sepolia (testnet) and Chain 232 is Lens Mainnet. Both are zkSync Stack-based chains. Let me search for the official WETH addresses for these Lens networks.
🌐 Web query:
💡 Result:
Lens Chain (mainnet) WETH: 0xE5ecd226b3032910CEaa43ba92EE8232f8237553. [1][2]
Sources:
[1] Lens Docs — Deployed Contracts (Lens Chain Mainnet).
[2] Lens Onboarding Docs — Deployed Contracts (Lens Chain Mainnet).
I found a critical discrepancy. The official WETH address for Lens Chain (mainnet) according to Lens documentation is
0xE5ecd226b3032910CEaa43ba92EE8232f8237553, but Chain 232 in the PR shows0x6bDc36E20D267Ff0dd6097799f82e78907105e2F. Let me also verify the Lens Sepolia address.🌐 Web query:
💡 Result:
Lens testnet WETH: 0xaA91D645D7a6C1aeaa5988e0547267B77d33fe16. [1]
Sources:
[1] Lens documentation — Deployed Contracts (Lens Chain Testnet).
Replace both WETH addresses with the official Lens Network contracts.
The WETH addresses are incorrect according to official Lens documentation:
0x6bDc36E20D267Ff0dd6097799f82e78907105e2Fwith0xE5ecd226b3032910CEaa43ba92EE8232f8237553(per Lens Docs)0xeee5a340Cdc9c179Db25dea45AcfD5FE8d4d3eB8with0xaA91D645D7a6C1aeaa5988e0547267B77d33fe16(per Lens documentation)🤖 Prompt for AI Agents