17:20:36 CLSAG preprint is now updated on IACR: https://eprint.iacr.org/2019/654 17:20:52 (`monero-site` MR in progress to point to the IACR version) 18:00:15 nice, do you want to post on Reddit? 18:00:30 I think people are curious about CLSAG 18:11:46 Sure, I'll make a post 18:12:06 Note that that MRL paper list on getmonero will show the old version until the MR is merged 18:12:22 but the IACR link always shows the most recent version 18:14:59 https://www.reddit.com/r/Monero/comments/frvyro/updated_clsag_preprint/ 18:15:58 ^ selsta 18:19:26 ty 18:24:10 AFAIK 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 20:01:34 moneromooo: do you consider your clsag branch (with the last commit of my clsag-device branch added) suitable for audit/review? 20:03:29 I think so. I really forgot whether I still wanted to do something now, so I'll consider it done :) 20:04:10 The one thing I remembered is to move the fork from 12 to 13, and it's done. 20:40:49 Do you plan to wait on that device_default commit until trezor/ledger support is done? 20:41:11 Presumably any audit should include that particular commit, since it offloads some crypto functions to device_default 23:21:42 I can add it when done. 23:29:46 OK, so I should rebased my `clsag-device` to your `clsag` for the fork update, and use that for audit? 23:30:17 That way auditors have the device-specific function structure, even without the ledger/trezor code 23:30:23 (which seems out of scope anyway) 23:30:55 ^ moneromooo 23:37:29 You 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. 23:38:21 Might be best if the branch that gets reviewed is in your tree since you'll likely be involved in the review directly. 23:48:54 OK, I suppose it depends on the audit timing