00:03:07 <koe> moneromooo can you even make a spend key with 0*G?
00:04:02 <koe> it should be identity but does the function work?
00:04:03 <moneromooo> It is invalid I think, technically.
00:04:41 <moneromooo> You might not be able to do much of anything, I don't really care. I want to know whether you can break anything that's not yours.
00:05:04 <moneromooo> (and I expect the answer to be "no", but I have a reason for asking)
00:06:57 <koe> Ill let the cryptographers answer that. My guess is no
00:07:50 <moneromooo> Yes, sorry, I wasn't asking you in particular :)
00:08:02 <koe> :p
00:10:43 <sarang> Are there transactions suspected of having this property?
00:11:21 <moneromooo> No.
00:12:06 <sarang> Off the top of my head, it would provide easier-to-identify outputs and permit spending with only the view key, for example
00:13:09 <moneromooo> Which is also the case for "I pick a very random spend key then publish it". So I'm not interested in those things.
00:14:36 <sarang> From a ring signature perspective, output public keys are output public keys
00:41:56 <sarang> You can already select any output pubkey you want... the protocol can't check that such a pubkey corresponds to an "expected" user public key
15:46:00 <suraeNoether> Good morning everyone... Today I am finishing finishing finishing finishing my CLSAG review and debugging debugging debugging matching, in that order.
15:46:56 <derpy_bridge> [keybase] <kaylasu>: mornin' and GL and on those thingies :3
15:47:07 <Kayla-Cypherpunk> UwU
15:47:30 <sarang> How's the CLSAG review going so far, suraeNoether?
15:48:56 <suraeNoether> Slowly 😥 it's getting to the point where rereading the same paragraphs over and over is yielding reduced returns on copy editing value
15:49:10 <suraeNoether> But I have a list of comments that I'm going to send you later today
15:49:23 <sarang> Thanks
15:50:16 <suraeNoether> When did the keybase bridge get added?
15:50:23 <suraeNoether> And how do I get in on that
15:51:15 <Kayla-Cypherpunk> just right now, still still setting it up, is that okay with you? can shut it down at any point, that aint an official bridge but also with the "Cypherpunk & Cryptoanarchy Club" discord
15:51:39 <suraeNoether> I'm fine with it until it gets swamped with a bunch of up-country degens
15:51:51 <suraeNoether> Add me on keybase, I am surae
15:52:08 <suraeNoether> If there's going to be a bridge, I feel like it should be managed by one of the Monero team members. That's my primary concern
15:52:11 <Kayla-Cypherpunk> alrighty, awesome and will do :)
15:52:32 <suraeNoether> We need some sense of accountability to the community so that it's not just a random room controlled by a third party
15:53:02 <suraeNoether> Who's in charge of the other bridges like matrix?
15:53:48 <Kayla-Cypherpunk> whole point of the discord is that there is no hierarchy, we're on an anarchist model, everyone having the permissions, as for right now tho set the discord <-> irc to be readonly on the #monero-research-lab
15:54:33 <sarang> IMO there needs to be a way to remove spammers etc. from the channel
15:54:52 <sarang> I have no interest in getting spam or hateful nonsense that nobody can stop
15:56:20 <sarang> AFAIK it's possible to turn off the matrix bridge with some sort of matrix-bridge bot user that's on the network
15:56:23 <Kayla-Cypherpunk> i hear ya, on discord side like mentioned everyone having the permissions, its kinda self-regulating to avoid that kind of scenarios
15:56:33 <Kayla-Cypherpunk> btw, added you on keybase :)
15:56:50 <sarang> And I suppose if needed, from the IRC side the bridge user could simply be kicked/banned?
15:57:07 <Kayla-Cypherpunk> for now i havent set up matrix yet, its kind of a first time for me on irc, tried it once 10 years ago for 2 days and thats about it, never again
15:57:33 <Kayla-Cypherpunk> sure, kick is a thing yes
15:57:50 <sarang> ok
15:58:14 <sarang> Hopefully there won't be any issues with anyone violating the "be excellent to each other" guideline
15:58:51 <Kayla-Cypherpunk> :)
15:59:05 <camthegeek> there's at least 3 other bridges in here, that I'm certain aren't controlled by MRL. Just peeps spying on ye' ol' Monero
15:59:55 <sarang> suraeNoether: you saw vtnerd's PR from yesterday?
16:00:58 <suraeNoether> No, I was Sundaying. Linky?
16:01:06 <suraeNoether> (not home yet)
16:01:20 <sarang> https://github.com/monero-project/supercop/pull/3
16:02:22 <sarang> I did a separate @-mention for you
16:23:37 <derpy_bridge> [keybase] <kaylasu>: test
16:24:18 <derpy_bridge> [keybase] <kaylasu>: :)
16:24:43 <sarang> test succeeded
16:24:52 <derpy_bridge> [keybase] <surae>: Yay
16:34:48 <SerHack> :)
18:01:26 <sarang> Reminder that our weekly meetings are now held on Wednesdays at 18:00 UTC (see topic for the usual agenda link)
18:01:48 <sarang> You can read previous message logs on the corresponding GitHub issues
18:02:17 <sarang> I'll be working on encrypted timelock proof-of-concept stuff and timing estimates
23:28:38 <vtnerd> sarang suraeNoether : I forgot about tweetnacl! after chopping the unused parts and adding a few functions, view key scanning (except for derivation_to_scalar :/) for Monero can be done in 301 lines of C
23:29:47 <vtnerd> very slow though, 2300% percent slower for 2-output transactions (just the crypto ops) than the existing scanning crypto used by wallet2