-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(trezor): add HF15 support, BP+ #8299
Conversation
Pinging @sethforprivacy that we have all code ready in PRs to support HF15 |
Wow, that was quick, thank you! Will forward this on and update the checklist. |
38c0717
to
1c4cd56
Compare
Just pinging that Trezor PRs were merged |
Thanks, @ph4r05, I pinged the Monero dev channel that this should be ready for review etc. yesterday, and will be sure we get it in ASAP. Thank you for all of the hard work on this! |
Just to confirm, does the have the inv-8 reversion? #8277 (only merged 17 days ago) I remember hearing that concern. The only branch with a commit since then (besides a version bump on the same day, present in this branch) is the "hackathon results" which seems to be cleaning up. Any test on the current master which confirms TXs work would be sufficient to confirm :) |
@kayabaNerve thats a good point, let me check |
1c4cd56
to
ee72984
Compare
@kayabaNerve you were right, I've incorporated the #8277 change. Trezor firmware needs the change as well, I will create the PR now. |
Thanks, and sorry you're only hearing about this now after Trezor already did a merge. Happy we're catching it though, and thanks again for working on this :) |
No problem @kayabaNerve! I am glad we caught it before release! :) |
ee72984
to
e621309
Compare
hello @moneromooo-monero, if you pls find a minute, I would be grateful for PR review for upcoming HF upgrade, thanks a lot! :) |
We will have a second release before the HF that will include this patch. |
@ph4r05 Just for completeness, did you test this on the current testnet? Are view tags working correctly in addition to BP+? Also is the firmware already out so that I can test this myself? If not, any approx release date? |
|
View tags: #8061 |
There is definitely no view tags support added in Trezor. I will check it out this week and figure out required changes. |
I asked @j-berman and he said
but he only took a quick look himself. I think the easiest way would be to make a transaction on testnet, or change the fork height locally and try to construct a transaction. |
- BP+ support added for Trezor - old Trezor firmware version support removed, code cleanup
e621309
to
a0df140
Compare
thanks @selsta for the ping! I've added view tag support to the trezor firmware: trezor/trezor-firmware#2345. This PR is also updated. As wallet is using view_key to derive view tags, tx receiving code on the wallet side does not require changes.
|
@matejcik It would be good to have a date for the Trezor firmware release as it's something that has to be done before we hardfork. The current HF date is |
@selsta We will not be releasing firmware sooner than August 17-ish. |
@selsta are pls HF15 changes enforced on activation or is it still possible to send HF14 transactions to the network (normal Bulletproofs) for some time after HF15 activation? If HF15 rules are enforced, Trezor won't be able to sign new transactions until new trezor-firmware update. |
I believe there will be a 24 hour interim period where both transaction types are valid. After those 24 hours, only the new ones will be. |
@matejcik Would it be possible to split the firmware update in two? One for monero and one for the other planned changes? If not we will have to ask the monero community if they prefer to delay the hardfork or if they are okay with leaving Trezor users unable to transact for about 2 weeks. Both are not ideal :/ |
@selsta thing is, there are no other planned changes right now .) |
Bad news everyone. |
Thank you for the update, four days shouldn't be too bad. @ph4r05 Is there a way for me to install the firmware before the update is out? A nightly firmware build or something similar? I want to do some additional testing on testnet. |
@selsta you should be able to pick a firmware image from our CI |
Did some testing with the firmware image from CI, tx creation and receiving worked well on testnet. |
@ph4r05 please also open against release-v0.18 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM. I see the majority of this PR's changes get rid of dead code for now unusable versions, thank you :)
The one thing I didn't fully wrap my around is the minimal versioning setting, but I figure you've got it how you want it
if (trezor_version <= pack_version(2, 0, 10)){ | ||
throw exc::TrezorException("Trezor firmware 2.0.10 and lower are not supported. Please update."); | ||
if (trezor_version < pack_version(2, 4, 3)){ | ||
throw exc::TrezorException("Minimal Trezor firmware version is 2.4.3. Please update."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From these comments:
Another thing, I hard-coded to the monero wallet that firmware version 2.5.1 supports HF15
We are releasing 2.5.1 which does not include this PR. Please bump to 2.5.2 in the monero PR.
I'm assuming only Trezor v2.5.2 will support bp+ and view tags. Wouldn't that mean the minimal Trezor version should be v2.5.2? Is the minimum set at v2.4.3 to support tx construction pre-fork?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind, I see. Once this ships, Trezors v2.4.3 and up will be able to use updated wallets until the fork height
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @j-berman! That was the idea, so old Trezors could still use the wallet even if they did not update yet. We can later enforce minimal version 2.5.2.
Trezor firmware changes: trezor/trezor-firmware#2232