vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
@v @gt It's interesting that Farcaster wallets leave no trace on Farcaster. There is no way to tell which wallet I used to approve signers. (Right? Or am I missing something?) I think future versions of app keys, should include some way for the wallet to leave a trace. Obv use is Farcaster Connect (knowing which wallets a user used in the past), but there may be other uses, we have not thought of, too.
2 replies
15 recasts
19 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
you can check the chain and reconstruct this from events, but it's not easy to read: If you add a key directly with add(), you can work back from the Add event to the transaction to the sender. If you did it with addFor(), you can work back from the Add event to the signature, which recovers to the approving wallet. But you'd want to index all this to use it.
2 replies
0 recast
1 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
So, how can you tell which wallet I used to generate the signer I approved today (real case)? I don't think you can (the answer is fario). And there's no way to enforce it, but it might be a good idea for the wallet to include an id or something if they like, in the tx.
0 reply
0 recast
1 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Hmm... I see what you mean. But that's not the same as the app used. It's easy to tell for Warpcast, because it uses a specific flow, and (I guess) a specific address to fund the transactions. But not in general.
0 reply
0 recast
0 reaction