“Embedded wallet” is a funny marketing term. It borrows legitimacy from embedded systems, which suggests that the wallet is part and parcel of the application

In reality, it’s a “hosted” wallet - the host (aka the SaaS provider) can revoke access to the wallet as soon as their customer (the app) stops paying

spotlight

friendly neighborhood anon // crypto angel + advisor + shitposter

I'm prob not the first to think of this trick but I'm using an AA provider with privy for /spotlight partially to preserve optionally for embedded providers

Oh interesting — i hadn’t thought about embedded systems, for us was about the relationship to the product experience, trying to make onchain actions a natural part of user interactions. 

We actually wrote a bit about it at the time (https://www.privy.io/blog/embedded-wallet-launch) but iirc term was from @gaby

FID 83. Investor at TCG Crypto. Farcaster power user. nf.td/gaby

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

was digging into some @privy docs yesterday, i found the term "embedded wallet" a bit misleading lol. "Hosted Wallet" is far more accurate. 

curious for the evolution of AA wallets though, although still not composable, can be a new users 'first' wallet (but not their last)