Farcaster Devs

Feedback regarding detection of mini-app hosts:

• Option 1 (well-known query parameter) would be the worst because it’s another identifier apps need to hardcode and will be easily spoofed (akin to browser extension wallets setting `isMetaMask` to true on their `window.ethereum` object). Just continue to let apps specify custom params for themselves in `<meta name="fc:frame">` if they really need it.

• Option 2 (message passing) is ideal but can be improved further – I recommend turning it into a two-way message system modeled after EIP-6963 to avoid race conditions. (Also while you’re at it, use EIP-6963 to announce Farcaster Wallet’s EIP-1193 object to the app for instant compatibility with existing wallet picker UIs.)

• Option 3 (`isInMiniApp()` SDK function) – this is fine assuming apps don’t already have the SDK code-split from their main client-side bundle, but maybe redundant to Option 2.

Another benefit of the wurplet adopting EIP-6963 – apps can just leverage all the standardized RPC methods apps normally expect from a traditional wallet, like checking whether a given chain is supported or not.

Another benefit of the wurplet adopting EIP-6963 – apps can just leverage all the standardized RPC methods apps normally expect from a traditional wallet, like checking whether a given chain is supported or not.

https://github.com/farcasterxyz/miniapps/discussions/240#discussioncomment-13108720

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

This would also mean we can use Warplet in mini apps without the extra connector right? Since it’s injecting the whole provider object

Also for Option 2, you may as well just extend the EIP-6963–announced EIP-1193 interface with custom RPC methods to avoid the need for a custom client-side SDK altogether.

https://warpcast.com/darrylyeo/0x0ac8b731

Yup, would simplify wallet picker UIs and eliminate a bunch of bespoke SDK logic among many other benefits!

gm. Fulltime degen, building fun stuff onchain. 
Master of Disaster Frogworks, /ottodao bullfrog, ex @astaria

Yup, would simplify wallet picker UIs and eliminate a bunch of bespoke SDK logic among many other benefits!

https://warpcast.com/darrylyeo/0x0d5d7f45

@farcaster dev / dad / books, cooks, ski, code ~ there are many things of which a wise man might wish to be ignorant

yea it's possible on mobile since WebView paradigm let's your inject and execute arbitrary code on the document

but blocked on web as you called out

Hmm. Wonder how existing wallet apps are able to pull this off with their in-wallet browsers.

I suppose for the web client you’d have to do this on the SDK side after all, given iframes have pretty strict cross-origin security.

i don’t think this is possible?

extensions are able to inject code into any document you’ve loaded

mini apps get rendered in iframes. we can’t just inject arbitrary code into it. the connector needs to be there to request and listen for the events coming from the parent