fluidkey

@moritz 

random vibe

- problem a user has is generating new pw. 1pw makes that easy by allowing a user to... generate new pw ad infinitum. 

- problem web3 user has is new accounts (desired or not) for dapps. fluidkey makes that easy by allowing a user to.... generate fresh addresses ad infinitum. 

- fluidkey vibes

great parallel by @accountless.eth 

you shouldn't use the same pw for every account, don't use the same Ethereum address for everything you do onchain

at trust wallet via sequence. pimlico. poap. polygon. metamask. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

I make music, take pictures and break prod, mostly. 

nkem.dev /learninpublic /true

this is my new mantra. Framing this and actioning asap! 
Just to be sure, is fluidkey just for receiving? And what multisig do you use?

I think it really depends on a case by case, but this is my set up:

- A public one - connected to ENS, Farcaster, holds NFTs, etc.

- Fluidkey to receive payments and store ETH with better privacy

- Safe multisigs for valuable assets

- A few other "hot" accounts, signers for Safes, etc across different wallets

Man, I need re-education on my onchain habits. 

How do you advise using accounts? One for public persona, a business/professional one, and a storage one for things of value? 

And with the public account, use fluid key to generate fresh addresses per need base. Am I correct?