Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: Add ability to verify XDR's on mobile #1796

Open
piyalbasu opened this issue Jan 16, 2025 · 1 comment
Open

SPIKE: Add ability to verify XDR's on mobile #1796

piyalbasu opened this issue Jan 16, 2025 · 1 comment

Comments

@piyalbasu
Copy link
Contributor

piyalbasu commented Jan 16, 2025

Consider a scenario where a user has malware on their computer that compromises their hardware wallet. If they go to sign a transaction in Freighter with their hardware wallet, the signed XDR that comes back from the wallet may not be what the user expects. The user is blindly trusting their hw wallet to give them back the correct XDR to send on to the network. In our send/swap flows, we do show the user the XDR with signatures before sending, but we don't provide a way for user's to verify it.

One idea is to verify the XDR with a mobile device. What are options for doing this?

  • How can we leverage Freighter mobile as a way to view/verify XDR's quickly?
  • What do we need to build in Freighter extension/web to share the XDR to a mobile device?
  • What do we need to build in Freighter mobile in order to parse this data for the user?

Further context:
https://stellarfoundation.slack.com/archives/C03347FNAHK/p1729622611848269
https://medium.com/@RadiantCapital/radiant-post-mortem-fecd6cd38081

@MonsieurNicolas
Copy link

I think what we are probably more worried about in this context is to have the front end component of the signing flow to be compromised. In this specific case the mobile device running freighter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants