Bitcoin Forum
November 15, 2024, 11:08:48 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: manage private keys in iOS app  (Read 1881 times)
jonas.schnelli (OP)
Member
**
Offline Offline

Activity: 66
Merit: 16

bitcoin core contributor


View Profile WWW
October 22, 2013, 02:46:29 PM
 #1

I'd like to slowly slip into the iOS app store with a bitcoin app.
First thing could be a iOS Bitcoin Keychain.

My idea is to have a iOS App ready, where your private keys are generated and stored.
The public key can be "transported" to your Desktop-App with QR-Codes (or bluetooth, or bonjour TCP/IP, etc.).

The desktop app should then transmit unsigned transaction to the iOS app (QR, bluetooth, bonjour TCP/IP) where the tx get signed with the private key.
The signed tx should then be broadcastet over the Desktop-App (somehow sent back to the desktop app).

Of course it need some thought about how the user could backup his private key in case he lost his phone.
Maybe the private keys get's AES256 with a initial creates AES key (ensure strength) which the user needs to write down or print out directly over airprint (no e-mail option!).
The encrypted private keys could be stored on iCloud or other services (Dropbox/Google-Drive).

Would that be possible with bitcoinj?
Any feedback to this approach? Stupid? Or would it help having encrypted/secured wallets?

Thanks
--
Jonas
Mike Hearn
Moderator
Legendary
*
Offline Offline

Activity: 1526
Merit: 1134


View Profile
October 22, 2013, 04:28:12 PM
 #2

Bluntly, I think iOS is a non starter and you should forget about it. Apple's legal team have decided that they don't want an app that can send money without a third party on their devices. Anything that seems to fall in that general area will get banned.

Just get an Android device already Wink
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!