Content pfp
Content
@
0 reply
26 recasts
26 reactions

typeof.eth ๐Ÿ”ต pfp
typeof.eth ๐Ÿ”ต
@typeof.eth
I'm bootstrapping a project and I was hoping to use onchainkit (Coinbase Smart Wallet support is a must), but unfortunately the only EOA wallet options with onchainkit are MetaMask and Coinbase Wallet I wanna support as many wallets as possible, so RainbowKit (which supports Coinbase Smart Wallet + a bunch of other EOAs) is hard to turn down I really hope that onchainkit adds support for more EOAs in the future, either through WalletConnect, ConnectKit, or some other option My preferred flow for onchainkit would be something like: - If no browser extension wallet is installed, default to Smart Wallet (with a way to log in via mobile wallet if on desktop) - If a browser extension wallet is installed or if I'm using a mobile wallet browser, let me select from a list of options including Smart Wallet, but put the wallet I'm using at the top IMO, to bring new people onchain, making it easy to create a Smart Wallet is the move, but for folks that have an EOA, pushing it introduces unnecessary friction
10 replies
6 recasts
65 reactions

Daniel Sinclair pfp
Daniel Sinclair
@danielsinclair
I believe these might be compatible if you use the custom providers implementation and wrap your component in both the OnchainKitProvider and RainbowKitProvider. Wagmi handles the wallet connection state under the hood, so you could still generate transactions from OnchainKit and use RainbowKit's connection UI. https://onchainkit.xyz/config/supplemental-providers
1 reply
0 recast
0 reaction

Daniel Sinclair pfp
Daniel Sinclair
@danielsinclair
If you get this working and you find it useful, I'd be happy to host an example on our repo!
0 reply
0 recast
0 reaction