frames-v2

Frames v2 Highlights: Domain Associations 👷 ↔️ 🌐 

problem: trusting a frame

context: it's important for users to understand who they're interacting with when using a frame so they can make informed decisions like whether to approve a transaction requested by the frame.

v1: the frame was identified by a domain just like how a website is identified when browsing the web. This was ok but not great—for well known sites like zora.co this works but for devs building without an established brand it's fairly useless.

v2: an account can create a public association between itself and a domain. This let's frames be presented to users with a clear and strong signal of which Farcaster account built it. It also means the frame can provide a name (in v1 this was a bad idea since it's leads to phishing attacks).

Building @warpcast and @farcaster, new dad, like making food

yeah have always wanted a creator fid association! where is this association stored?

working @ /neynar   🪐  casting @ /rish

yea these are a no brainer for neynar to index

excited to see if any use cases pop up outside of frames

this probably could've been it's own FIP but frames v2 introduces /.well-known/farcaster.json that includes the Domain Account Association

haha I have read this spec a few times and def glossed over that line lol 

thanks for pointing out

this probably could've been it's own FIP but frames v2 introduces /.well-known/farcaster.json that includes the Domain Account Association

https://github.com/farcasterxyz/protocol/discussions/205#domain-account-association