Varun Srinivasan
@v
A quick primer on how keys and frames work in FC. During sign up: 1. User creates eth key on their phone. 2. Warpcast creates account key on its server. 3. User approves account key onchain Eth keys can hold funds and can control your account. Account keys can only post messages from your account.
6 replies
45 recasts
155 reactions
Varun Srinivasan
@v
The eth key controls your account and is an Ethereum address. The account key can post from your account, and is NOT an Ethereum address. This design is intentional and ensures that: 1. users never have to give apps control of their account 2. apps never have to worry about users storing funds on keys they control
1 reply
1 recast
15 reactions
Corbin Page 👑🎩
@corbin.eth
I’d recommend Option 2 in the short-term and see how it’s used before deciding if Option 1 is viable or whether to build Option 3. Option 1 with cross-app support is viable with tx monitoring and session keys to scope in limited low-value permissions per Frame. But that stack is not mature yet.
1 reply
0 recast
1 reaction
Ishika
@ishika
Miss your YouTube videos, pls upload more walk throughs here now that video is supported 🫡
0 reply
0 recast
0 reaction
Matthew Fox
@matthewfox
I think enabling AA at scale is the most advantageous and can limit user first party wallet risk That said, simple tx like send would be nice from the user account. Makes it easy to top up an AA acc while preserving security I think mobile<>mobile has the highest risk vector
0 reply
0 recast
0 reaction