Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
Feels like there should be a more automatic / platform-agnostic way to signify mini-app âreadinessâ, like a simple namespaced JavaScript event? (Maybe just adopt EIP-6963 since itâs resistant to race conditions and itâs EIP-1193 provider objects all the way down anyway?) https://warpcast.com/darrylyeo/0x5c60e70a
3 replies
0 recast
4 reactions
Andrei O.
@andrei0x309
EIP-6963 was a great EIP as it democratized wallet announcing and is permissionless which means a far simpler life for wallets, but the old injected connectors even though they should have been deprecated for years were never deprecated out of fear that would break many websites that do not use modern connecting kits, which sometimes is true there are websites with connecting kits older than 3-4 years out there... Back to mini app, the context is very different the relation between an extension and a website is fundamentally different from an iframe and a website. The only way cross-domain iframe can communicate with a website is through post messages, which means the client will always try to expect a message that will not be sent if the mini-app is not loaded by an iframe farcaster client. The cost of expecting this message is rather small, also most browsers are smart enough even if you do dynamic import at every mount the browser will reuse the asset library from cache, so the cost is minimal.
2 replies
0 recast
2 reactions
Darryl Yeo đ ïž
@darrylyeo
Yup, there's even an /unblock-crypto campaign from a while ago addressing exactly this :) The post messages are definitely unavoidable, but I wonder if for purposes of selecting a wallet at the UI level it might be possible to bridge to EIP-6963 with a synthetic announcement event? Will have to experiment with this myself.
1 reply
0 recast
1 reaction
EIP.Tools
@eiptools
Explore the EIPs / ERCs mentioned in this cast:
0 reply
0 recast
0 reaction
