14:06:45 I think everyone here knows that most Monero exchange withdrawals and desposits are traceable (Breaking Monero - poisoned outputs). How does it feel to go out and lie to people that they are private and then earn less than holding BTC on your bag? 15:29:53 https://usercontent.irccloud-cdn.com/file/WRIjqKTZ/RoughTimeline 15:30:05 Rough times of the two major options ^ 15:30:57 dEBRUYNE knaccc ArticMine sarang sethsimmons 15:31:04 sorry I don't have Project anymore :p 15:40:55 sgp_ very cool 15:42:02 this is my best attempt a putting pen to paper 15:43:32 oh yeah, i really enjoyed your presentation on kyc/etc stuff 15:46:43 thanks! the one from yesterday? 16:06:45 yes the one one youtube 16:14:13 cool 16:14:18 any thoughts on the timeline? 16:24:20 i like the latesummer HF for BP+ just merely to get the network on the same client asap 16:25:35 i really can't speak to the timelines for triptych R&D. 16:25:56 re: BP+ audits, did you reach out to the same folks that did randomx? 16:26:15 gingeropolous: yes, not trailofbits though 16:26:20 I don't have trailofbits contact 16:26:26 hyc, ^ ? 16:26:37 let me paste the email I sent 16:26:46 i wanna re-read those docs they provided, but I remember that some of them just seemed more better than others 16:27:00 though, this is a different beast i guess 16:27:01 https://www.irccloud.com/pastebin/8y0QgCNS/email 16:28:38 email addies for tob in old audits: https://github.com/tevador/RandomX/blob/master/audits/Report-TrailOfBits.pdf 16:28:42 unless those don't work no more 16:29:38 good catch, emailing now 16:30:46 SoWs are still online too 16:31:00 emailed 16:31:06 https://github.com/hyc/RandomxAudits/ 16:31:53 2 years ago. wow 16:31:53 so I contacted JP, QuarksLab, Kudelski, TrailofBits 16:32:21 yeah, time is flying... 16:32:24 emailing X41 now 16:34:12 sent 16:37:36 so code exists for triptych right? 16:37:47 https://www.reddit.com/r/Monero/comments/l7x3gn/looking_for_another_bulletproofs_auditor/ 16:37:56 gingeropolous: yes, sarang would know best 17:38:57 Triptych prove and verify routines are coded 17:41:43 Is that code intended to be production quality ? 21:01:36 There may be additional optimizations possible, but it should be close to auditable as is 21:01:49 I'd need to give it a once-over after reviewing optimizations 21:41:52 Great, thanks. I meant it as "is it a suitable candidate to plug into consensus". Since you often point out research code is not suitable for production :) 22:10:21 At this point I think the function structure is suitable for consensus code 22:10:31 Internal guts of functions may be subject to more optimization 22:13:36 Sure, that's totally fine.