Recommended
Recommended
More Related Content
Similar to Product Architecture of Hardware Wallet - Without Sequence Diagrams.pdf
Similar to Product Architecture of Hardware Wallet - Without Sequence Diagrams.pdf (20)
Recently uploaded
Recently uploaded (20)
Product Architecture of Hardware Wallet - Without Sequence Diagrams.pdf
- 2. Key Features For long term saving • Support for watch only addresses For medium term saving for future expense • Separate Wallets for different classes of expenditure For daily transactions • Lightning Network channels. For prepaid card with oversight • Separate device with preloaded coins for each member Onboard last person of society • Low cost • Inconspicious USB device • Tied with a mobile phone. Never carry all your money • Hardware device only carries private keys and addresses secured by HSM. • Keys are generated offline on unconnected computer
- 3. Guiding Principles - Requirement Mapping Security • Security against theft: Theft or loss of device/mobile phones, Limited loss against robbery, secure against loss on physical break into device. • Security against hacking and attacks: Fake device, trozen apps, Man in the middle attack, spyware/key-loggers. • Safe recovery of coins when device and mobile are lost, stolen or broken. • Safe recovery of coins if password is lost Privacy • Each address pays one time • Bloom Filter based network communication • Bluetooth device wallets are "Just a bunch of keys (JBOK)" Convenience • Easy to pay (All payments will happen through Mobile app) • Easy to receive (Receiving will happen through Mobile app) • Ease of recovery (Seed will help in recovery) • Easy to carry (Very small USB device) • Easy to secure (Seed can be written on paper or remembered easily) Open Source • Open standards • GPLv3 Mobile App
- 4. Target Use cases Initialization It should be easy tosetup Devicessecurely. Initialization happensoffline Recovery Loss of devicesor mobile should not lead to loss of funds. Recovery should be easy. Recovery happensoffline. Payment Sendingorreceivingshould support QRcode, addresses and app integration. Payment/Receivingshould be secure. Fund allocation/partition Allows allocation of funds among children oremployees with oversight but not control. Allows multiple walletsbased on usage and security. Cold Storage Wallet should allow watch only addresses for only receivingfunds.
- 5. Components
- 6. Security Features Security Device verification Bootable Linux Image Blutooth device Authentication 3-factor authentication User (Password) Mobile App Blutooth Device Blutooth stores multiple wallets Device communication Encrypted communication Private/Public keys not exchanged Recovery Mnemonic code based Only through linux usb pen drive
- 7. Privacy Considerations Single time address use • Change left in a transaction is transferred to new address. Bloom Filter Based communication • We will have Simple Payent Verification (SPV) implementation on our mobile app. Wallet is "Just a bunch of Keys" • We will not use xpub as this can link between addresses.