Warpcast

🐟 Snappa | picosub.artlu.xyz | SassyHash.artlu.xyz

Find me with my same PFP on GH

It's not only on the device, I just logged in with a fresh emulator.

Clearly, it's stored persistently.

In the best-case scenario, it's encrypted with the user-provided seed as a password, and the seed is never stored at Merkl.

But again, without the full source code of the backend + client, it's just: "trust me, bro", for all we know, even the seed could have been stored.

Thanks, much appreciated. 

I have not tested if the auth token is enough, but I can look into it.

My speculation of this being guarded by the seed is the scenario, I dealt with in the past as an option when dealing with apps that integrate a client-side wallet. 

That scenario provides better protection for users, as any code that needs your PK needs to be executed by the client, which is more cumbersome for the provider because if users don't update the app, the provider can't take that action, or if the users use an alternative client( in Farcaster case).

An example of this is the upcoming authorizing the Warplet address as an Auth address, which can only be executed with the custody PK, and will be fulfilled automatically. 

If is not accomplished by pushing code to the client it means Warpcast has direct access to your PK which is bad IMO.

I'll take a look to see if it can be retrieved by auth token only and come back to this.