-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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: use networkClientId to resolve chainId in PPOM Middleware #27263
feat: use networkClientId to resolve chainId in PPOM Middleware #27263
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [d30b4a5]
Page Load Metrics (1854 ± 121 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
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.
Seems correct to me but we should definitely get an approval from @jpuri or someone else on confirmations before merging!
tested this by trying to send a malicious tx on a different chain from the globally selected by setting To be extra safe, the globally selected network was set to Linea Sepolia, a chain that PPOM does not support. This implies that the warning shown must have used the request's chainId |
Quality Gate passedIssues Measures |
Builds ready [47ba18d]
Page Load Metrics (1857 ± 65 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
Description
Updates the PPOM Middleware to use the chainId for the dapp selected network instead of the globally selected network when processing a request
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist