Pavol Rusnak

@dxoigmn Can you generate an image for any given hash (preimage attack) or do you need access to the source image first (second preimage attack)?

For the record, clightning is now broken in nixpkgs and nix-bitcoin because mrkd is now broken in nixpkgs - https://github.com/NixOS/nixpkgs/blob/0b73b43a942d4f264036c74d03758194ba0b5855/pkgs/development/python-modules/mrkd/default.nix#L27-L28

Please rebase on top of current master to remove the merge commit.

Tracking issue for Trezor Taproot Support: https://github.com/trezor/trezor-firmware/issues/1656

> Trezor recently merged Taproot support for the Trezor T: [trezor/trezor-firmware#1891](https://github.com/trezor/trezor-firmware/pull/1891). The initial support PR will likely only include Trezor T support as it is the easiest one for me...

> That one is closed and seperated into subtasks: > [trezor/trezor-firmware#1943](https://github.com/trezor/trezor-firmware/issues/1943) > [trezor/trezor-firmware#1944](https://github.com/trezor/trezor-firmware/issues/1944) > [trezor/trezor-firmware#1946](https://github.com/trezor/trezor-firmware/issues/1946) That is not entirely correct. Taproot for singlesig has been implemented in full for both...

With poetry, `requests` are installed via `sphinx` as its dependency. Since `setup.py` does not mention `sphinx`, it also does not install `requests`.

The only thing that HWI would need to store the dict of `device_id`s and `session_id`s. This could be in a form of a .json file stored in `~/.hwi` or alternative...

If we don't want to store session on filesystem, we can have them in memory. We'd just need to have bi-directional stdin/stdout communication interface #450, so we don't have to...

Which OS is that? Windows? Which "other apps" does Trezor work with?