Skip to content
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

[Multichain] fix: Use chain-specific addresses for safe creation [SW-261] #4305

Open
wants to merge 1 commit into
base: epic/multichain-safes
Choose a base branch
from

Conversation

usame-algan
Copy link
Member

What it solves

Resolves SW-261

How this PR fixes it

  • Uses chain-specific addresses for safeFactory, safeL1 and safeL2

How to test it

  1. Create a safe on zkSync
  2. Observe no error

Checklist

  • I've tested the branch on mobile 📱
  • I've documented how it affects the analytics (if at all) 📊
  • I've written a unit/e2e test for it (if applicable) 🧑‍💻

Copy link

Copy link

github-actions bot commented Oct 2, 2024

Copy link

github-actions bot commented Oct 2, 2024

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 987.27 KB (🟡 +26.17 KB)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Fifteen Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/ 511 B (🟢 -24.37 KB) 987.77 KB
/address-book 26.09 KB (🟡 +5 B) 1013.36 KB
/apps/open 53.09 KB (-1 B) 1.02 MB
/balances 29.42 KB (🟢 -1.52 KB) 1016.68 KB
/balances/nfts 19.18 KB (-1 B) 1006.45 KB
/home 57.22 KB (🟢 -923 B) 1.02 MB
/new-safe/advanced-create 36.49 KB (🟡 +1.36 KB) 1023.76 KB
/new-safe/create 35.75 KB (🟡 +1.36 KB) 1023.02 KB
/new-safe/load 16.41 KB (🟡 +6 B) 1003.68 KB
/settings/modules 9.82 KB (🟡 +38 B) 997.09 KB
/settings/notifications 27.03 KB (-2 B) 1014.29 KB
/settings/setup 35.98 KB (🟡 +5 B) 1023.25 KB
/transactions/tx 21.07 KB (-2 B) 1008.34 KB
/welcome 6.8 KB (🟢 -1 B) 994.07 KB
/welcome/accounts 379 B (🟢 -1 B) 987.64 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

Copy link

github-actions bot commented Oct 2, 2024

Coverage report

St.
Category Percentage Covered / Total
🟡 Statements 77.95% 12359/15856
🔴 Branches 58.24% 3232/5549
🟡 Functions 65.18% 1943/2981
🟡 Lines 79.45% 11153/14038

Test suite run success

1541 tests passing in 205 suites.

Report generated by 🧪jest coverage report action from 035a761

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.

1 participant