00:21:41 For the past couple of weeks, quotes were solicited from the following parties (in order of received SoW): 00:21:43 - Least Authority: Review of Eagen's commentary on correctness and the specified R1CS gadget. 55,960 EUR + 31,541 EUR if paid in a timely fashion. 00:21:45 - Veridise: Review of Eagen's commentary, an explicit proof or counterexample of Eagen's work, and review correct transformation into a R1CS gadget. $250 an hour, across 8-24 hours, with +$4,000 upon said proof or counterexample. 00:21:47 - Trail of Bits: Review of Eagen's commentary on correctness and the specified R1CS gadget. $50,000. 00:21:49 - Cypher Stack: Review of Eagen's commentary on correctness and the specified R1CS gadget. 210 XMR. 00:21:51 - Quarkslab: Review of Eagen's commentary on correctness and the specified R1CS gadget. $48,500. 00:21:53 - Brandon Goodell: A formal write-up and review of Eagen's commentary on correctness and the specified R1CS gadget, with a proof if possible. $185 hourly, 130-150 hours ($24050 - $27750). 00:21:55 We also solicited a SoW from JP Aumasson, yet they aren't actively working as an auditor. 00:21:57 Believing the researcher at Veridise competent (having been involved with a variety of academic works on fields), and given their cost being significantly less than the other options, jberman and mine's endorsement at this time is Veridise. When asked if they truly believe the work feasible in that amount of time, they do believe it amenable (though it may end up requiring an exte nsion, as anything may, see how the recent GBPs work risked being inconclusive) and a payment is conditional to a result in order to create the proper incentive structure and preserve value upon an inconclusive result. 00:22:01 Depending on how their work goes, we'd ideally move on to contracting another group for review of their output (a couple candidates standing out as preferred). This is expected to be discussed at the next MRL meeting yet is posted here now for review ahead of time. 00:59:44 Also, Veridise quoted payment via a wire transfer or USDC/USDT. Payment would be handled through MAGIC who has volunteered their facilitation. It's partially up front, partially within the conclusion of the scope of work. I'd call for the full amount to be transferred to MAGIC at time of consensus as necessary to secure the USD valuation. cc sgp_ if they'd like to further comment. 02:22:03 Wow Veridise quote is max 10k? 03:13:41 There do be a reason they're endorsed. 08:18:29 Is it not worth getting two independent reviews done, for comparison? 08:20:39 as opposed to a peer review of one output. I understand there will be redundancy with concurrent reviewing, but i think it a more robust strategy (though could be wrong). It's also what we did with RandomX, iirc. 09:31:30 <3​21bob321:monero.social> Double spend 09:48:14 midipoet this is true. example https://rekt.news/raft-rekt/ "Raft had been extensively audited by four organisations, including > Trail of Bits < and a Hats Finance contest." 09:57:19 We actually funded three concurrent audits for RandomX 09:57:19 https://ccs.getmonero.org/proposals/RandomX-audit.html 09:58:11 And there was a fourth done also, for comparison (but paid for by Arweave it seems). 10:51:15 i think those were done when the code was ready? is the current effort at the same place? or is this like a preliminary 3rd party review of the underlying whatsits? to me it seems the second, based on this specificity "Review of Eagen's commentary on correctness and the specified R1CS gadget." 12:16:44 midipoet: We can obtain two reviews of the underlying which say the same thing, or we can get one review and have that reviewed. The distinction is that instead of independently coming to stronger commentary which isn't yet strong enough, we can achieve stronger commentary, than secondary reviee _and_ the sufficiently strong comments. 12:17:09 Like, literally, two independent proofs of this does not help us. Any proof *with peer review* does. 12:18:55 kayabanerve: Thank you for doing the work to get these quotes! "Eagen's commentary" is https://eprint.iacr.org/2022/596 and R1CS is what? Is it this? https://github.com/monero-project/research-lab/issues/116 12:19:13 If we were not potentially soliciting proofs, this would not be necessary except for distinct concerns of it being financially irresponsible. If one party tells us it's completely insecure and broken, do not touch, we don't need to hear from a second party we gave $30k and a month of time the exact same just a few days after the first party reports that. 12:20:32 It's the correctness section of that paper for the first numbered equation. 12:20:33 No. That issue has nothing to do with this. At all. 12:20:35 It's the R1CS gadget specified in the FCMP++ paper. 12:20:53 *the R1CS gadget specified for proving discrete logarithms 12:21:28 I ctrl+F for r1cs in the FCMP++ and didn't see any matches 12:22:16 Said gadget is an R1CS evaluation of Eagen's equation 1 (and implied protocol). If the math follows, this specification is what we'd actually implement in-circuit. 12:23:36 Section 4.3 is a R1CS constraint system. 12:24:13 The following gadgets are R1CS gadgets, 4.4.2 being the one relevant here. 12:25:33 Could you make a gist explaining exactly what's proposed to be reviewed? You can point to the sections in Eagan's paper and your own. 12:28:00 And for the quote-proposals that will attempt to write proofs, which proposition(s) will attempt to be proven? 12:28:38 Attempt to write proofs or create counterexample(s), I mean. 12:32:50 About the options to (1) have one proof written plus the proof reviewed compared to (2) two proofs written by independent entities: Mathematics and code are different. IMHO, having a second independent proof attempt in (2) doesn't have zero value, but it is not as good as reviewing a single proof in (1). 12:35:29 1) It depends on which is being discussed. It's always Eagen's... 3.3.1? (the section on correctness for equation 1) and the R1CS gadget. 12:35:31 2) The statement Eagen proves for in statement 1 is effectively that points sum to 0. I formalized this in https://github.com/kayabaNerve/fcmp-ringct/blob/divisor-paper/divisors.pdf. It leaves a spot for a proof premised on witness extraction. Not all proofs proposed are so premised, but the proof discussion is functionally equivalent as far as we're concerned. 12:37:56 That document is a summary of the background, a formalized protocol (not simply an equation), and the R1CS gadget. Accordingly, it is the best reference. 12:37:57 Please note it came after some proposals were solicited so some proposals are scoped to the background and the gadget included in the paper, not the paper itself. 12:59:06 Thank you. Could you create a gist of the quotes summary you gave above and the expected scope of work to provide a reference to everything in one place? Especially since your divisors.pdf is in a separate git branch of `fcmp-ringct`. 13:10:16 When I'm around next 👍 13:11:05 Thanks a bunch :D 13:14:11 Of course