Please login or register.

Experimental trezor firmware testing


I worked on a trezor firmware which supports XMR awhile back but stopped development around August last year. I want to "complete" the firmware soon and then release the source to github when it's somewhat stable. I'm releasing the binary since I need help testing the current version.

While there are user interaction limitations, the firmware is fully functional and can be used to sync accounts as well as transfer XMR from active accounts. Only simplewallet is supported at the moment and from my testing, windows is fairly stable while linux needs some work [FIXED].

The firmware is compatible with BTC and does not remove any functionality available in the official firmware. The source is upstream compatible and can be merged to the official source (if they want to). XMR uses the same seed as BTC so you can restore your old seed anytime and regain your old account.

There are important points to note:

  • The viewkey is sent to the client. A bad client could potentially store these keys and see all incoming transactions to your account, privacy is then compromised.
  • The client has no access to the sendkey and can only request the device to generate key images or sign transactions. Your funds are safe.
  • It takes about 40ms to generate each key image. For large wallets, re-sync is going to take a while, so keep the wallet bin files.
  • [FIXED] The send confirmation prompt is incomplete. It will be fixed in subsequent versions.
  • [FIXED] There is no reconnect/retry implemented in simplewallet at the moment.
  • Max mix level is 9

V0925: trezor_xmr_test_firmware_0925

  • Updated to trezor source v1.4.0

V0313: trezor_xmr_test_firmware_0313_win64

V0313: trezor_xmr_test_firmware_0313_linux64

V0313: trezor_xmr_test_firmware_0313_osx64

  • Fixed Bus: 10 error


  • Added reconnect handler when trezor is unplugged while simplewallet is active
  • Added tx_seckey storage support to firmware
  • Added support for 'address' simplewallet command
  • Fixed support for entering passwords when trezor is initialized/recovered with password protection enabled


  • Added binaries for linux-64 and osx-64
  • Fixed usb transport bug in linux/osx
  • Updated source to master b96147030cf06b7adacafebff196bc23a4b19199
  • Added trezorctl to wipe, reset, recover the trezor
  • Added trezorctl option to recover the monero mnemonic from the trezor seed given a specific address index


  • Added send prompts when transferring xmr with multi destination support.
  • Fix: added error handler when mixin level is > 9
  • Fix: added error handler when sending to > 10 addresses in a single transaction.


  • Test release

Upgrade instructions:

  1. Disconnect the trezor from the USB cable.
  2. Press both buttons on the trezor then connect the USB cable.
  3. Run upload.bat. Wait until new firmware upload is completed.
  4. Verify firmware fingerprint (from fingerprint.txt)
  5. Disconnect then reconnect trezor to USB.
  6. Go to (using CHROME) and initialize your device. (You have the option to restore your SEED words if you want to keep using the trezor with your current BTC (etc.) account.
  7. Close CHROME. Otherwise, it will not release the trezor USB device and simplewallet will not find it.
  8. Run simplewallet.exe --hardware-wallet n (n can be any reasonable number eg. --hardware-wallet 0)

PIN Entering:


Replies: 58
pa edited 1 year ago Weight: 0 | Link [ + ]

Tested V0313 using Trezor and OS X 10.11.3. Everything worked well, including sending and receiving in simplewallet. (The only problem I had was failed firmware upgrade due to USB cable failure. Swapping cable fixed that.)

Impressive work, @NoodleDoodle!

pa posted 1 year ago Weight: 0 | Link [ + ]

It would be wonderful if NoodleDoodle's work could be integrated with the upcoming official GUI! In particular, Trezor PIN entry via GUI would be very helpful.

xmrdc posted 1 year ago Weight: 0 | Link [ + ]

Tested build 313 on OSX v. 10.9.4. Was able to send and receive .2xmr just fine. Can also log into

pa posted 1 year ago Replies: 1 | Weight: 0 | Link [ + ]

NoodleDoodle, How secure is the Trezor code at this point? Is it ready to entrust with medium or large amounts of XMR?

Reply to: pa
dEBRUYNE posted 1 year ago Replies: 1 | Weight: 0 | Link [ + ]

I'd wait until the code is released on Github and merged upstream by Trezor (and thus signed).

Reply to: dEBRUYNE pa
NUKE1989 posted 1 year ago Weight: 0 | Link [ + ]

Any subjective guess about how much time this will take? After the reddit post about mymonero (which might be just fud anyway) i would prefer to send what amounts i keep there to trezor.

dru1 posted 1 year ago Replies: 1 | Weight: 0 | Link [ + ]

Hey NoodleDoodle, can you make the binaries available again? Just bought a second trezor ready to test it out with monero :)

Reply to: dru1
NoodleDoodle edited 1 year ago Replies: 1 | Weight: 0 | Link [ + ]

Links updated.

Reply to: NoodleDoodle dru1
dru1 posted 1 year ago Weight: 0 | Link [ + ]