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

Exposing a list of chain IDs in the SDK wouldn’t hurt, but this can quickly become stale if apps don’t bump their SDK package version in a timely manner.

Have Warpcast announce Farcaster Wallet’s EIP-1193 object to the app using EIP-6963, then support the RPC methods `wallet_addEthereumChain` (EIP-3085) and `wallet_switchEthereumChain` (EIP-3326).

This lets apps “request” a particular chain, which Farcaster Wallet can accordingly accept or reject on the spot.

Engineer @farcaster. Founder bountycaster.xyz

Ex Phantom, 0x Project engineer.

From Italy originally, currently live in NYC

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

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

Explore the EIPs / ERCs mentioned in this cast: