A place for developers to talk about building on Farcaster.

/dev

what are your top problems when building mini apps? e.g.
- frontend components are hard to build
- transactions are hard to create
- etc. 

looking for ways to make mini app development simpler

building farcaster infra @ /neynar 🪐 | casting @ /rish

Building onchain apps where the user may have multiple addresses is my biggest painpoint

We have the tools to work around it but it’s just a pain to have to account for the fact that a user might do something onchain w one wallet and then come back to the app with a different wallet (maybe they change preferred wallets)

doing the right thing.
working hard.
being optimistic.
putting the team over the individual.
pushing boundaries with creativity.

eng @ base

are you coming across users who change their preferred wallet often?

flock-in

weird, I don't see the request on my end:  https://flock-in.vercel.app?fid=10840

I don’t know if they’re changing it or if the preferred wallet data is stale but I’ve had several users report to me that they don’t see onchain data meant for their wallet when logging into my miniapp. 

Could be a skill issue on my part

I don’t know if they’re changing it or if the preferred wallet data is stale but I’ve had several users report to me that they don’t see onchain data meant for their wallet when logging into my miniapp. 

Could be a skill issue on my part

https://warpcast.com/zguz/0x0b5a8fad

where are you getting preferred wallet data from?

Award-winning Host of @Coinage covering crypto for a mainstream audience | Fmr. YahooFinance Anchor & Harvard Econ Grad | Co-Own Coinage with me 🫡

nooooo. I’m seeing this happen quite often.

I’m trying to balance a good ux w/ wallet flexibility

when you login, what is the wallet that you see in the upper right corner? If you could screenshot that, it would help.

I made the request for 0x65A922561638015E394A20356C31E9A6217513B8

what ended up being the preferred wallet for this user? https://warpcast.com/myk/0x1504a561

are there other examples where users have reported a different wallet than what the API returns? This user doesn't seem to have responded

I never got an answer from @zguz about the wallet that shows up in the upper right corner of the app
https://warpcast.com/myk/0x1504a561

I had a DM with @wakaflocka where the address in the upper right corner ends in 493A but their preferred wallet was listed as 0x87688588fe2440242dc822e21fe9e299486535fb in the neynar api

Building $FLOCKA 🔥 

0xdc471c5c72de413e4877ced49b8bd0ce72796722

don't think the latter part is true, neynar doesn't return a primary address for their profile which also matches warpcast 

afaict their primary address has not been set. there are no verified addresses for them on the protocol at all, and neither on Warpcast APIs. 

you can tap on the tiles and see here: https://explorer.neynar.com/993072 

so they likely connected a wallet manually, I am not sure what you mean by the API returned you something else

Ah in this instance I fell back to the custody address. It’s all in the same bucket of pain where I need to store something onchain for a user and the address that I have available to me at the time may not be the address that the user logs in with

One thing that could be a solve to this is I store data onchain based on fid and I can use the neynar contract that looks up verified addresses by fid

That way, as long as the fid doesn’t change, the user can use whatever verified wallet they want and I can rely on neynars contract to map it to an address

Could be a cool opportunity for a solidity lib that provides a modifier for something like _onlyFid(uint256 fid) and returns true if the msg.sender is a verified address of the given fid

yeah the issue makes sense. in this case, 
1. the user doesnt have an address linked to their profile
2. you fall back to custody address
3. they manually connect a different wallet 

if there are instances where the primary address information is wrong, that's a separate bug we can look at (no such evidence yet). 

re: the overall issue, not sure if there is much to do there but will think more about it.