Content
@
https://warpcast.com/~/channel/miniapps
0 reply
0 recast
0 reaction
Angel
@sayangel
now that we have more chains supported I'm finding it hard to know if I'm experiencing bugs in mini apps because my warplet isn't switching chains correctly or something else. Chain indicator somewhere on mini app UI would be nice so each dev doesn't have to implement a chain id display. At the very least would be nice to see it in the "connected" display that shows up when you expand the ellipsis menu.
3 replies
0 recast
11 reactions
horsefacts
@horsefacts.eth
yeah, we have been chewing on this internally (cc @deodad). one problem is that *all* miniapps are multichain and stateful (since one app may switch your wallet to some other chain), but they don't necessarily know it. a common issue is not ensuring you switch to the right chain before requesting a tx.
2 replies
0 recast
6 reactions
Manan
@manan
imo - all chains should be connected all at the same time :) why do we need to switch chains at all? is this web3js's legacy?
3 replies
0 recast
15 reactions
Tony D’Addeo
@deodad
100% agree and was thinking last night: - is there anything we're missing on the stateful model that makes it make sense? the best argument I assume is some sort of security angle where a user might get tricked if they aren't paying attention, which imo is weka - how warpcast practically break this pattern? I think it might be harder than it seems, for instance wagmi accepts chainId on it's sendTransaction action but will throw if it doesn't match. what we want is to programmatically switch. https://github.com/wevm/wagmi/blob/main/packages/core/src/actions/getConnectorClient.ts#L109
0 reply
0 recast
1 reaction
Gabriel Ayuso
@gabrielayuso.eth
Yeah it doesn't make sense at all. Poor design.
0 reply
0 recast
1 reaction
Angel
@sayangel
The one true superchain
0 reply
0 recast
2 reactions
