-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
xmr: fix new transaction type for CLSAG, HF=13 #1246
Conversation
ph4r05
commented
Sep 3, 2020
•
edited
Loading
edited
- Changes required to make CLSAG working.
- Transaction type was not set accordingly
- Related to the Trezor: Enable CLSAG support for Trezor client monero-project/monero#6798
- New binary tests testing both HF=12 and HF=13: https://github.com/ph4r05/monero/releases/tag/v16.0.0.0-tests-u18.04-01
3cdc100
to
61c8d24
Compare
@ph4r05 What is the date this should appear in the firmware update? We haven't planned to do a firmware update soon, so knowing that will help us plan accordingly. |
@SarangNoether do we pls have any time estimate when CLSAG appears on the Mainnet? |
Binaries should be released around September 17, and CLSAG functionality will be activated on the network at a set block height around October 17 (and will be mandatory). |
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.
utACK
|
My mistake, I missed that. |
@ph4r05: Will any additional Monero codebase PRs be required to ensure Trezor support? |
No, this was all. All required PRs are merged. I've tested it with integration tests on both HF=12 and 13 blockchains and Trezor-signed transactions passed the verification process. |
Great! Monero binaries will be prepared and released soon, and CLSAG functionality will be activated (and required) around 17 October 2020. |
@ph4r05 (and others): Is it expected that Trezor firmware will be updated/released in advance of the CLSAG activation date? |
@SarangNoether our original plan was to release on November 4th. Is the date Oct 17th already set in stone and definite? |
The upgrade block height has already been merged. I posed the situation to the developer IRC channel, but any potential decision to delay this is not up to me. |
Ok in worst case scenario we will release on Oct 6th. It messes up some planning of ours but we'll manage :). Let me know. Thanks! |
Sounds good! I will follow up here with any developments. |
I did not hear support in the development channel to change the upgrade block height, so I think it is safe to assume that it will remain the same and take place around October 17. |
@SarangNoether Is the upcoming hardfork already deployed on Stagenet/Testnet? Where do I find info like this - roadmap of hardforks? |
It is deployed on testnet and will be deployed to stagenet on 2020-09-28. |
We will release on Oct 7th then, firmware version 2.3.4. Thanks everyone. |
@SarangNoether
|
@bosomt AFAIK you can use both Stagenet and Testnet to perform the test, here are the public servers and faucets info: |
Alternatively you can find testnet / stagenet nodes here: https://community.xmr.to/nodes.html Faucet: |
QA OK sent tests transactions via gui client:
RingCT/type: yes/5 Send XMR transaction Send and receive XMR with passphrase |
Nice! Thanks @bosomt ! |
Thank you for publishing the new firmware version with CLSAG support. We will take the extra potential time necessary for firmware updates into account in future network upgrades. |