Farcaster

Reviving the "primary address verification" FIP.

When we wrote this a year ago, it seemed like a good idea to allow only EOAs as primary, since SCWs may not be deployed everywhere. Now I am much less sure since most modern smart accounts have crosschain counterfactual addresses.

Should we leave this up to the user, who can verify smart contract addresses at their own risk?

Reviving the "primary address verification" FIP.

When we wrote this a year ago, it seemed like a good idea to allow only EOAs as primary, since SCWs may not be deployed everywhere. Now I am much less sure since most modern smart accounts have crosschain counterfactual addresses.

Should we leave this up to the user, who can verify smart contract addresses at their own risk?

https://github.com/farcasterxyz/protocol/discussions/141

Real World Ethereum 🌎 
building /daimo ✳️ 

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

chef at moxie.xyz | Moxie is your onchain AI assistant—analyzing transactions, unlocking social alpha, and executing trades on your behalf.

Currently deploying. Unofficial head platypus of /lp 

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

The main downside is that it would be possible to verify older SCWs that are not deployed cross chain, like older Gnosis Safes.

(tagging in a motley assortment of people who use primary addresses, smart accounts, or both @woj.eth @wilsoncusack @henri @dcposch.eth @koeppelmann.eth @jacek @symmetry @deployer @betashop.eth @vrypan.eth)

Founder @payflow /payflow payflow.me /crimea 🇺🇦

and some who gave feedback on the original FIP: @androidsixteen.eth @vrypan.eth @sinaver.eth