Bitcoin / Altcoin cold storage / hardware wallet on teensy 3.2

Status
Not open for further replies.

rspenc29

Member
I really want to make a hardware wallet with the teensy 3.2. I have over 15 years experience as a software engineer but that's mostly web development and android apps. I am fairly new (few years on and off) into low level hardware programming, and not a lot of experience with crypto algorithms and protocols even though I use them all the time. Seeing as I can't find any examples of hardware wallets for arduino/teensy, makes me think there are some technical limitations to the hardware that's preventing someone from already taking on this project. Ideally I would like something similar to the trezor or ledger with a 128x32 oled and a few buttons, where i can create a deterministic wallet and addresses (public/private key pairs), store encrypted private keys, and sign transactions. Trezor is open source and I could potentially port some of the code to the teensy library but the hardware it's programmed for is way different and it uses hardware encryption which isn't available on the teensy. As a workaround I was thinking software encryption on a micro sd card but can't find a lot of successful encryption examples for arduino/teensy either.

So, given this information, I just wanted to ask those much smarter than myself if this is a feasible project to take on and what are the potential issues I may run into. I am fully willing to take this on if it's something that could be done in a month or two but I don't want to waste months just to find out I'm in over my head and will never be able to finish the project. Also, if I do take on this project, the end result will be an open source library that would be shared on github, not something I plan to mass produce and sell for profit.
 
For these purposes SPI flash would probably be more secure and reliable than SD.
 
For these purposes SPI flash would probably be more secure and reliable than SD.

That's a good point and something to consider. I guess I was leaning towards SD because it's built in to the 3.5/3.6 and because I'm using my 3.2 for multiple projects with switches to enable/disable features, some of which require SD storage. I could go either way on this and will look into both options.
 
Status
Not open for further replies.
Back
Top