martin
martin
Moved to trezor-suite repo https://github.com/trezor/trezor-suite/pull/9337 does anybody use it in production from npm? if yes, we should re-release it again under @trezor/ org
very dirty draft resolve #15032 
now `device.state` is used to identify specific device on TrezorConnect level. `device.state` is deprecated and will be replaced with `device._state` which we should start using now.  this should also...
reverted because of unexpected behavior https://github.com/trezor/trezor-suite/pull/15009 possibly related - #15000 - #15005 - https://satoshilabs.slack.com/archives/G019WLX2P7B/p1729519285307589
when I do `yarn workspace @trezor/connect-explorer dev` I get could it be somehow connected to updating socks-proxy lib recently?
1. introduce a new connect `"call in progress"` event 2. use this event to set `suite.locks[device lock]` in suite and get rid of the whitelist of wrapped methods. From now...
wip to be specified We need to have TrezorConnect.init ({ knownDevices }) param like this https://github.com/trezor/trezor-suite/commit/1a5b98622198f87cb70da9f66b56d8d1231bffd1 usecases: - thp - firmware hash check consider: maybe get rid of `pendingTransportEvent`
there is `LoadDevice` message which has not been implemented to connect yet. It might be useful for testing. lets implement it ``` "LoadDevice": { "fields": { "mnemonics": { "rule": "repeated",...
This PR implements "confirm-less labeling" feature. Previously, you needed to confirm "Enable labeling" dialogue on device screen. This is not needed anymore, or, more specifically, after this is merged the...
main changes: - replace text "device detected in incorrect state" with "device used elsewhere". There is nothing wrong with the device. it is just used elsewhere. - make information about...