-
Notifications
You must be signed in to change notification settings - Fork 411
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: private key signer #3784
Feat: private key signer #3784
Conversation
Branch preview✅ Deploy successful! Website: |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
1003.74 KB (🟡 +52.28 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!
Two Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/ |
24.86 KB (🟡 +1 B) |
1 MB |
/licenses |
4.97 KB (🟢 -29 B) |
1008.71 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.
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success1444 tests passing in 199 suites. Report generated by 🧪jest coverage report action from a7f0855 |
It looks really promising! and it will going to be really useful for automation to be able to switch owners, so test on 2/x safes can be performed My initial feedback.
|
ESLint Summary View Full Report
Report generated by eslint-plus-action |
@francovenica fixed both, thank you! |
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.
If I understand correctly this is meant to mainly be a tool for our e2e tests to use multiple signers.
I think we should make sure that this won't accidentally turned on in prod.
src/hooks/wallets/wallets.ts
Outdated
@@ -45,6 +46,7 @@ const WALLET_MODULES: { [key in WALLET_KEYS]: (chain: ChainInfo) => WalletInit } | |||
[WALLET_KEYS.LEDGER]: () => ledgerModule() as WalletInit, | |||
[WALLET_KEYS.TREZOR]: () => trezorModule({ appUrl: TREZOR_APP_URL, email: TREZOR_EMAIL }) as WalletInit, | |||
[WALLET_KEYS.KEYSTONE]: () => keystoneModule() as WalletInit, | |||
[WALLET_KEYS.PK]: (chain) => pkModule(chain.chainId, chain.rpcUri) as WalletInit, |
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.
I think we ensure that this wallet can only be enabled when IS_PRODUCTION
is false
as it is a tool for our e2e tests.
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.
To enable it, you'd have to go to the production config service, create a PK wallet, and enable it on a chain. Don't think this can be done accidentally.
Edit: actually you have to create a wallet for it to be disabled if not explicitly enabled. The config service is a little bit backwards...
const signedMessage = await wallet.signTypedData(params[1].domain, params[1].data, params[1].value) | ||
return signedMessage |
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.
Nit:
const signedMessage = await wallet.signTypedData(params[1].domain, params[1].data, params[1].value) | |
return signedMessage | |
return wallet.signTypedData(params[1].domain, params[1].data, params[1].value) |
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.
In that case we can merge it, but need to document somewhere not to enable this wallet for new chains / in prod.
@schmanu I ended up adding a prod check as you suggested because this will allow us to use this wallet on dev even if the CGW toggle is set to prod. |
What it solves
An experimental web3-onboard module to allow connecting directly with a private key as a Safe signer.
The idea is that you can have a (non-primary) signer key stored in your password manager/OS keychain and log in with it like with a password.
The private key is then stored in the session storage and it reconnects if the page is reloaded.
adc2f">