Wallet Logo

Stepan Snigirev STM32F769DISCO DIY Hardware Wallet

Latest release: 0.0.2_alpha ( 21st September 2019 ) 🔍 Last analysed 20th May 2022 . Do-It-Yourself Project Not updated in a long time
26th April 2019

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word discussing build reproducibility with Stepan Snigirev STM32F769DISCO DIY Hardware Wallet  via their Twitter!

Do your own research!

Try out searching for "lost bitcoins", "stole my money" or "scammers" together with the wallet's name, even if you think the wallet is generally trustworthy. For all the bigger wallets you will find accusations. Make sure you understand why they were made and if you are comfortable with the provider's reaction.

If you find something we should include, you can create an issue or edit this analysis yourself and create a merge request for your changes.

The Analysis 

Background

Stepan Snigirev is involved with Specter Solutions and is the CTO of Crypto Advance.

Snippet of the repository

Hardware wallet in micro-python on STM32F769-Discovery board

Currently focusing on STM32F769DISCO developer board. Support of other boards comes as soon as this one is stable enough.

Project structure

micropython folder contains a fork of micropython with some temporary workarounds for stm32f769 board. Currently the master branch of micropython fails to build for this target, as soon as it is fixed we will switch to the main micropython repo.

  • usermods/mpy-bitcoin folder contains minimal C-modules for micropython with basic crypto algorithms. Interface to optimized C modules allow to use optimized elliptic curve arithmetics and hashing functions:

  • usermods/mpy-bitcoin/hashlib.c adds support of sha1, sha256, sha512 and ripemd160 required for Bitcoin to hashlib python module.

  • usermods/mpy-display/ folder contains a C-module to work with the display present on the board.

  • usermods/mpy-secp256k1/ folder defines bindings to the secp256k1 library

Verdict

This do-it-yourself project hasn’t been updated for more than 2 years.

(dg)

Verdict Explained

This project is not meant for non-technical end users.

As part of our Methodology, we ask:

DIY

Is the product meant to be ready for use "out of the box"?

If the answer is "no", we mark it as "Do-It-Yourself Project".

Many hardware wallet projects aim to be as transparent as possible by using only off-the-shelf hardware with an open design and open code. If the product reviewed is not available in an assembled form - if the user has to source his own hardware to then maybe solder and compile software to install on the device it falls into this category.

But we also ask:

Obsolete!

Was the product updated during the last two years?

If the answer is "no", we mark it as "Not updated in a long time".

Bitcoin wallets are complex products and Bitcoin is a new, advancing technolgy. Projects that don’t get updated in a long time are probably not well maintained. It is questionable if the provider even has staff at hands that is familiar with the product, should issues arise.

This verdict may not get applied if the provider is active and expresses good reasons for not updating the product.