monzero-core.git/src/device_trezor, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2026-04-25T12:29:17Ztrezor: replace use of boost::is_base_of with std::is_base_of2026-04-25T12:29:17Ztobtohttob@featherwallet.org2026-04-25T12:29:17Zurn:sha1:919d247f7c62779a78df10e235811a24b0d0ecfdtrezor: fix protobuf 30 compatibility2025-03-18T07:36:13Ztobtohttob@featherwallet.org2025-03-16T21:39:31Zurn:sha1:bdcfd32f634989676594ee4d3ffc511c041d16e8Fix build with boost ASIO 0.87. Support boost 1.66+2025-02-14T18:29:57ZLee *!* Clagettcode@leeclagett.com2024-12-17T21:40:15Zurn:sha1:01bcd52924244ec8d2a24c10fcef8959289d09ffallow exporting outputs in chunks2022-09-07T06:22:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-08-16T20:20:38Zurn:sha1:0cbf5571d3ccd07c81d33b05dd23b2ac9c777c3b
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
feat(trezor): add HF15 support, BP+2022-08-05T12:27:16ZDusan Klinecdusan.klinec@gmail.com2022-04-12T00:06:19Zurn:sha1:6075be9cc8c3e8aacfa1428816e86dc623a72600
- BP+ support added for Trezor
- old Trezor firmware version support removed, code cleanup
Add view tags to outputs to reduce wallet scanning time2022-04-18T07:49:53Zj-bermanjustinberman@protonmail.com2021-11-15T13:23:53Zurn:sha1:ea87b30f8907ee11252433811e7a7d0c46758cca
Implements view tags as proposed by @UkoeHB in MRL issue
https://github.com/monero-project/research-lab/issues/73
At tx construction, the sender adds a 1-byte view tag to each
output. The view tag is derived from the sender-receiver
shared secret. When scanning for outputs, the receiver can
check the view tag for a match, in order to reduce scanning
time. When the view tag does not match, the wallet avoids the
more expensive EC operations when deriving the output public
key using the shared secret.
Copyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009Merge pull request #78692021-10-18T04:28:04Zluigi1111luigi1111w@gmail.com2021-10-18T04:28:04Zurn:sha1:ebc655c6ad594f0853f6a0f955ec46200efe7865
ad9fde4 UB: virtual methods in destructor at Trezor (mj-xmr)
UB: virtual methods in destructor at Trezor2021-09-08T12:44:35Zmj-xmrmjxmr@protonmail.com2021-08-16T09:45:39Zurn:sha1:ad9fde46a32587aaeee15a2142a74b3d85a3f636trezor: try empty passphrase first2021-08-03T11:54:04ZDusan Klinecdusan.klinec@gmail.com2021-07-14T15:08:36Zurn:sha1:13a8a576ed17b19197ca3518d686a0f8410fdbe9
- Try empty passphrase first when opening a wallet, as all Trezors will have passphrase enabled by default by Trezor Suite by default.
This feature enables easier access to all users using disabled passphrase (or empty passhprase)
- If wallet address differs from device address with empty passphrase, another opening attempt is made, without passphrase suppression,
so user can enter his passhprase if using some. In this scenario, nothing changes to user, wallet opening just consumes one more call
to Trezor (get wallet address with empty passphrase)
- also change how m_passphrase is used. Previous version did not work well with recent passphrase entry mechanism change (made in Trezor),
thus this commit fixes the behaviour).