Image credit (
I'm continuing my work on Ledger App Hive and I am pretty confident it will be finished and submitted for official review soon.
Previous posts regarding Ledger app:
I decided to rewrite the app from scratch. The old codebase was a bit messy and it would be really hard to work on it. Sometimes it's just easier to start from scratch. I only adopted the ASN1 DER encoding, proposed by netuoso for communication between Ledger device and PC/mobile.
It's basically finished. The new codebase is built on top of the latest boilerplate (provided by Ledger) and utilizes their newest SDK. Thanks to this, I was able to write the code in a way that will work on both Nano S and Nano X the same way (except for the fact that Nano X has a bigger display).
The new codebase compiles with 0 warnings and produces 0 bugs when tested with Clang Static Analyzer. This is the requirement that needs to be met before submitting the app for official review.
make[1]: Leaving directory '/app'
scan-build: Removing directory '/app/output-scan-build/2021-08-16-224415-44-1' because it contains no reports.
scan-build: No bugs found.
New SDK allowed me to redesign the user experience. Now, you can loop through the entire transaction back and forward. The previous version allowed you to verify every transaction field only once and it was really easy to accept or reject the transaction by mistake. Ledger has also some functional/design requirements and the new version follows them.
And, as I already said, it's working on Nano X.
This is a view from the simulator because there is no way to sideload the unofficial app to Nano X.
During the last two weeks, I put a lot of effort into unit testing the app (which is not only required by Ledger company but also very useful in the matter of stability and security). I covered most of my files with unit tests written in ANSI C, using cmocka framework. This will minimize potential problems, like buffer overflows/underflows etc which are really common on apps written in C.
Those need to be done yet, but I already prepared a Javascript library that is fully featured and can be used not only to communicate with the physical device but also with the simulator/debugger. The next step will be to create automated tests, to verify signatures for specified test transactions.
I'm already using it to broadcast transactions to our testnet. It shouldn't take long to finish this part.
We're close.
Follow me to be up to date with incoming development updates!
Click on the image to vote for 