Ethereum Account Abstraction

How will namespace resolution work on FC now that there are embedded wallets in Warpcast?

For example my fname is vinayvasanji, but I use my ENS on my profile which is vinayvasanji.eth

My ENS resolves to my EOA wallet address
My fname I presume will now resolve to my Warpcast embedded wallet

If someone tries to pay me via my Farcaster username (vinayvasanji.eth) within FC I'm assuming the funds will credit to my embedded wallet rather than my EOA, despite the identifier being my .eth which actually resolves to my EOA

If someone tries to pay me outside of FC, but to my fname, which is possible for certain products that have integrated fname namespaces, will they send funds to my ENS EOA or my FC embedded wallet?

Can someone clarify how all this is going to work?

There's a super easy fix for this. All you have to do is upgrade your embedded account to a smart account via EIP 7702. Next, depending on your smart account implementation, you could install an EIP 7579 module allowing you to transfer out all incoming tokens. Welcome to the future of finance.

now /backpack • building @so many products • prev. @everyname (acq) @nethermind @proximacapital @consensysacad • thomphreys.com