-
sarangCLSAG preprint is now updated on IACR: eprint.iacr.org/2019/654
-
sarang(`monero-site` MR in progress to point to the IACR version)
-
selstanice, do you want to post on Reddit?
-
selstaI think people are curious about CLSAG
-
sarangSure, I'll make a post
-
sarangNote that that MRL paper list on getmonero will show the old version until the MR is merged
-
sarangbut the IACR link always shows the most recent version
-
sarang
-
sarang^ selsta
-
selstaty
-
sarangAFAIK all that's needed from a code standpoint is complete trezor/ledger support, which is in progress now that the rest of the code is in place
-
sarangmoneromooo: do you consider your clsag branch (with the last commit of my clsag-device branch added) suitable for audit/review?
-
moneromoooI think so. I really forgot whether I still wanted to do something now, so I'll consider it done :)
-
moneromoooThe one thing I remembered is to move the fork from 12 to 13, and it's done.
-
sarangDo you plan to wait on that device_default commit until trezor/ledger support is done?
-
sarangPresumably any audit should include that particular commit, since it offloads some crypto functions to device_default
-
moneromoooI can add it when done.
-
sarangOK, so I should rebased my `clsag-device` to your `clsag` for the fork update, and use that for audit?
-
sarangThat way auditors have the device-specific function structure, even without the ledger/trezor code
-
sarang(which seems out of scope anyway)
-
sarang^ moneromooo
-
moneromoooYou can do whatever you'd rather. I'd imagined I would cherry-pick your new patch on top of my branch, but you can also merge my changes if you'd rather.
-
moneromoooMight be best if the branch that gets reviewed is in your tree since you'll likely be involved in the review directly.
-
sarangOK, I suppose it depends on the audit timing