Content
@
0 reply
0 recast
0 reaction
Stephan
@stephancill
i spent the last week rebuilding open browser wallet from scratch with the goal of being more of a blank canvas for a application-specific browser wallets features - built on wagmi + viem's account abstraction libraries - it now has no styling whatsoever - uses database backend by default with authenticated sessions (will have a standalone example in the future) - connect to apps with Coinbase Wallet SDK, Mobile Wallet Protocol, and WalletConnect (wip) - supports most common wallet features (sign messages, sign transactions, etc.) - multichain support out the box might refactor this into a library at some point but waiting to see which abstractions make sense https://github.com/stephancill/open-browser-wallet
6 replies
13 recasts
34 reactions
Wilson Cusack
@wilsoncusack
Would be cool if you supported loading an existing wallet via key import!
1 reply
0 recast
6 reactions
Stephan
@stephancill
As in load up an existing smart wallet address and import an owner via the recovery seed phrase?
1 reply
0 recast
0 reaction
Stephan
@stephancill
Might add this onboarding flow: Load smart account address Import owner via seed phrase Add a new owner passkey on open browser wallet đź‘€
1 reply
0 recast
3 reactions
Wilson Cusack
@wilsoncusack
Would be cool! Just to flag, this would put that account on that chain in a “divergent” state in our system and we’d no longer allow that account on that chain to initiate further owner changes.
1 reply
0 recast
2 reactions
Stephan
@stephancill
Hm interesting, that’s good to know So you wouldn’t be able to do recovery via keys.coinbase.com anymore? Or are there other implications?
1 reply
0 recast
0 reaction
Wilson Cusack
@wilsoncusack
Basically, we have a lot of complex logic around replaying owner changes to keep all chains in sync. If someone makes a replayable owner change outside of our domain, we don't attempt to sync that owner change and that account could diverge from future owner changes in our UI. But recovery and the wallets still work. cc @hodges.eth check my math
1 reply
0 recast
2 reactions
Adam Hodges 🔵-'
@hodges.eth
yep, we have no way of knowing if the owner change is intended to be synced to other chains, or if it could be malicious, so when an owner is added via a 3P UI we stop syncing new owners for that chain (it also causes conflicts with our replayable nonce space). both for safety reasons as well as to manage complexity. if this becomes a popular flow we can certainly look into solutions! keyspace will also dramatically simplify all of this.
0 reply
0 recast
1 reaction
