11:20:47 <gingeropolous> whats the size of an ringsize equivalent triptych tx? i keep losing that image with the graphs
11:24:30 <gingeropolous> oh its in the paper sweet
11:25:47 <gingeropolous> well kindaq
12:34:56 <sarang> What do you mean "size of ringsize equivalent" gingeropolous
12:35:31 <gingeropolous> ringsize 11 ,
12:38:59 <sarang> Oh you'd need to use ringsize 16 or some other exponent decomposition
12:45:29 <tevador> AFAIK triptych is log-size, the limiting factor is verification performance, not proof size
12:46:41 <sarang> correct
12:59:00 <sarang> gingeropolous: for `N=16` a CLSAG signature would be 576 bytes, while a Triptych proof would be 640 bytes
12:59:32 <sarang> Sizes for other transaction elements (keys, linking tag, range proof, auxiliary data) would not change
13:00:01 <sarang> For multi-input transactions you add additional signatures/proofs to accommodate
13:41:01 <gingeropolous> roight roight
15:25:26 <sarang> So how's research today?
15:25:31 <sarang> I'm rewriting a CLSAG proof :)
19:10:54 <rbrunner> So after the info from Turtle Coin's IBurnMyCD I copied some code from here to try: https://github.com/turtlecoin/cs-turtlecoin/tree/master/CantiLib/Cryptography/Native
19:11:26 <rbrunner> Result: Works perfectly. Starting with a private key, I get everything else, the view key and both public keys.
19:12:09 <rbrunner> So whatever this does, and does differently than the packages that I tried so far, being a more or less direct port of the Monero C++ code, this does "the right thing"
19:12:30 <moneromooo> Too bad adding more code for MS' trojan is not "the right thing" though.
19:13:10 <rbrunner> It will run on .NET core, on a Linux server. The whole C# stuff is still Microsoft of course however.
19:15:40 <rbrunner> And for what it's worth, the C# compiler and the .NET framework are open source. Microsoft even switched to Git internally a while ago.
19:16:38 * moneromooo winces
19:16:48 <rbrunner> Why so?
19:17:04 <rbrunner> Maybe time to switch to #monero :)
21:55:13 <sarang> Anyone feel like reading over a security proof before I send it off to the CLSAG auditors for their comments?
21:55:41 <sarang> They suggested expanding on the proof of Theorem 1 from the preprint, which I've done in much more detail
22:34:46 <sarang> Updated proof of CLSAG Theorem 1: https://usercontent.irccloud-cdn.com/file/karoRzRt/proof-theorem-1.pdf
22:37:32 <sarang> The only change of note is that in the first part of the proof, there are an extra `q` signing oracle queries