Pavol Rusnak

> The address format is `m/44'/coin_type'/account'/change/address_index`, so in both screenshots above the account is `/0` which is `#1`. Please sync with Suite on this. I think they (mis-)use address index...

I did STM RNG tests back in 2013 when we were still deciding which chip to use. See the repo for the firmware and the results: https://github.com/trezor/rng-test

[Related issue #23](https://github.com/trezor/trezor-firmware/issues/23): We can still require or at least encourage diceware and/or cointoss input when initializing as a standalone device (without host that can provide entropy, e.g. a powerbank).

We can get extra entropy when we tell a user to move their finger randomly while touching the screen for 5-10 seconds. Then we can hash all of the input...

> What would need to happen for Trezor to add BIP-322 signing to the firmware? Let's say 3 major software wallets support this. Then we can consider adding the support.

> Can confirm this error with GCC 14. Same

> I work around this issue by add "-Wno-incompatible-pointer-types" to CFLAGS. It is better to use `-Wno-error=incompatible-pointer-types`, so the warning is still shown but not treated as an error. This...

> as there are dependencies that need fulfilled in order to build that are not addressed in the Makefile or pyproject.toml Can you open another issue stating what your problem...

> Does T1B1/Model One qualify as obsolete too It never really worked so +1 for dropping T1B1 from Core

> let's see if [e114031](https://github.com/bitcoin-core/HWI/commit/e114031f48b639119ff79391890553f654c0573a) helps It did, nice!