Coming back to this, because my answer above was too vague. I've written up a proper threat model since:

The honest answer to "weakest part": what runs before NDS-Signer (DSi firmware, Unlaunch, TWiLight Menu++, all from the SD card), which it can't verify. After that, the QR decoding in C, which hasn't been fuzzed yet, and the scribble + mic entropy, which has no measured number. Dice are the safe option for now.

Also, the demo video is on Odysee now instead of mega: 

bitcoin

bitdevs

devs

NDS-Signer: a SeedSigner on a Nintendo DSi & PSBTs as phone tones and more

ndssigner

Coming back to this, because my answer above was too vague. I've written up a proper threat model since:

[https://github.com/ndssigner/nds-signer/blob/main/docs/threat-model.md](https://github.com/ndssigner/nds-signer/blob/main/docs/threat-model.md)

The honest answer to "weakest part": what runs before NDS-Signer (DSi firmware, Unlaunch, TWiLight Menu++, all from the SD card), which it can't verify. After that, the QR decoding in C, which hasn't been fuzzed yet, and the scribble + mic entropy, which has no measured number. Dice are the safe option for now.

I opened issues for each of these: [https://github.com/ndssigner/nds-signer/labels/audit](https://github.com/ndssigner/nds-signer/labels/audit)

Also, the demo video is on Odysee now instead of mega: [https://odysee.com/@ndssigner:9/nds-signer-demo:2](https://odysee.com/@ndssigner:9/nds-signer-demo:2)