In order to accelerate adoption of the new Bridge, I recommend @dexter703 should refactor the S Y R I U S extension to support manifest v3 and submit an AZ for the work.
@vilkris pointed out that the wallet supports manifest v2, and apparently google has changed to manifest v3. Google will not accept the SYRIUS Chrome extension unless we upgrade. I think this is a high priority to accelerate adoption of the bridge.
{âdescriptionâ:âSyrius extension provides a non-custodial wallet solution for Zenon - Network of Momentum that can run in the browserâ,âversionâ:â0.1.9â,âmanifest_versionâ:2,ânameâ:âZNN Syrius Extensionâ,âbackgroundâ:{âscriptsâ:[âbackground.bundle.jsâ],âpersistentâ:true},âcontent_scriptsâ:[{âmatchesâ:[âhttp:///â,âhttps:///â,â<all_urls>â],âjsâ:[âcontentScript.bundle.jsâ],âcssâ:[âcontent.styles.cssâ]}],âbrowser_actionâ:{âdefault_iconâ:âicon-34.pngâ,âdefault_popupâ:âpopup.htmlâ},âpermissionsâ:[âstorageâ,âunlimitedStorageâ],âiconsâ:{â128â:âicon-128.pngâ},âdevtools_pageâ:âdevtools.htmlâ,âcontent_security_policyâ:âscript-src âselfâ âwasm-evalâ; object-src âselfââ}
Apparently, adoption for this is pretty low because of UX challenges. (plugin on top of an extension)
Perhaps a cleaner route would be to implement the BTC wallet into Syrius extension so it can be used in all BTC DeFi applications? Not sure how much can be borrowed from mobile implementation to do thisâŚCC: @john.maxwell
With the new architecture for the mobile and desktop repo, you can borrow a lot of business logic from the repo.
Regarding the extension, you might be able to build it with Flutter, as long as the packages needed for the intended features have web support.
I am not familiar with the web extension, what it does, and what is needed for the manifest version upgrade. But you can give me a list of features for a new extension, and I can check if it can be done in Flutter.
I think he has some good ideas in here we can leverage. Iâll do that same and maybe we can develop a scope. His one big idea was to make a simple version that hid all the advanced features. That is something that could help us a lot.
Maybe @Goldmoon has some ideas too. He had some strong opinions on needing a simple wallet. He is working on a TG game for NoM now.
@john.maxwell I just read the gravity wallet thread again and I think the one big idea is to abstract away the idea of QSR, fusing it, and understanding what it does. That is gigabrain stuff that no one cares about.
So if I were to summarize some features it would be:
Simple mode that abstracts away the concept of QSR. All you need to know (in this mode) is that you need it for fast transactions. If you own QSR in the wallet, TXs are fast. If you donât own it, TXs are slow.
In simple mode the wallet automagically handles fusing QSR. The user just needs to know if they have QSR or Not. And how much is left for more TXs. Maybe something like a fuel tank or antigravity
We should give the user the ability to backup seeds in Basic mode after the wallet is created. Maybe the setup process has two modes - Basic and Advanced setup.
Gravity wallet assumed zkSync (zerosync) which is not available. So maybe it just uses a public node by default which can be changed in advance mode.
Advanced mode would open up more features that are consistent with what is available today in the existing web wallet.
I read the proposition on Gravity Wallet and the specific comment that you mentioned. The sketch that you proposed is not difficult to implement. Whatâs difficult is having all the needed libraries available for Flutter Web also.
Right now, I canât start anything else. But after I finish the proposed projects, we can start working on a lighter wallet for web.