@
0 reply
0 recast
0 reaction
Phil Cockfield pfp
Phil Cockfield
@pjc
↑ Installed "Obvious" yesterday. Q: If I'm looking to get my head around an AA Wallet is this a good one to center attention on @accountless.eth ?
0 reply
0 recast
1 reaction
@
0 reply
0 recast
0 reaction
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Would love to hear first hand feedback on the Obvious wallet @pjc
2 replies
0 recast
0 reaction
Phil Cockfield pfp
Phil Cockfield
@pjc
Hey @jebui - I still have "beginners mind" on your wallet (as in I've installed it, but haven't done anything with it yet) - so may still be useful to comment on "initial observations" for you. What would be useful? What is the kind of user are you designing for? What would your ideal user know before starting?
1 reply
0 recast
1 reaction
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Ideally someone who is crypto aware, who has tried a couple of other wallets and would like to have an easier to operate wallet. Knows about chains bridges and has heard about AA. Would be useful to hear if you understand the value props as you onboard and where you are facing confusions if any as you use the app.
1 reply
0 recast
0 reaction
Royal pfp
Royal
@royalaid.eth
Hey πŸ‘‹, I am actually going around testing AA wallets and seeing how they work with Mai.finance (I help with the frontend). I will be sure to include this in the testing and I can try to write down my thoughts on the onboarding flow too.
1 reply
0 recast
2 reactions
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Would love to hear your perspective @royalaid.eth
1 reply
0 recast
0 reaction
Royal pfp
Royal
@royalaid.eth
Okay so I have a few nitpicks with the onboarding flow but overall its great! I do have one odd bit of behavior, if I set the chains on the walletconnect config to more than just 1 and 137 (mainnet and Polygon) the app just silently fails to connect and eats the walletconnect modals QR connection.
2 replies
0 recast
0 reaction
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Ah the smart wallet is currently supported only on 1 & 137 now as the contracts are deployed only there as yet. We try to make this amply clear during the onboarding that the smart wallet is only on those two chains now. You can create a normal eoa wallet and use that to connect to all other chains.
1 reply
0 recast
0 reaction
Royal pfp
Royal
@royalaid.eth
Right but the user flow AFTER getting onboarded and just connecting to a Dapp that requests more than 1 and 137 right now provides no feedback, it would be nice to least display some of kind of error like Ledger live does to explain to the user why the connection fails
1 reply
0 recast
0 reaction
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Got you will fix that. Thanks for letting know.
1 reply
0 recast
0 reaction
Royal pfp
Royal
@royalaid.eth
Sweet Jesus, okay the solution I found is to set a minimal set of required chains, in our case polygon and mainnet. Then after your wallet connects you can fetch the session's chains (the one's the wallet will accept) via this snippet I attached in the image. Surely there is a better way but this works for now
1 reply
0 recast
0 reaction
Jebu Ittiachen pfp
Jebu Ittiachen
@jebui
Could you give context on what you are trying to accomplish? For a wider set of chains support use the non aa wallet. You can get that by creating a wallet in the β€œAdd or create more wallets” button on the home page
1 reply
0 recast
0 reaction