01:01:23 <jberman[m]> Try this out dangerousfreedom: https://paste.debian.net/1231686/
10:53:34 <slave_blocker2> hello
10:53:39 <slave_blocker2> good daz
10:53:53 <slave_blocker2> *day
18:43:21 <slave_blocker2> i want to learn more about monero 0.15.x.x , i have seen that there is a mininero repo. It does not run ! says lots of import errors and so on in python...
18:43:47 <slave_blocker2> i have a lot of questions...
18:44:28 <slave_blocker2> i guess if i can run mininero then i can see ringct step by step ?
18:45:49 <slave_blocker2> what is the difference between a pseudo output commitment and a normal one? it is not explained anywhere in ztm i guess :(
18:51:07 <moneromooo> Try with python 2.
18:53:39 <slave_blocker2> python2 Test.py HPow2
18:53:56 <slave_blocker2> import Crypto.Random.random as rand
18:53:56 <slave_blocker2> ImportError: No module named Crypto.Random.random
18:56:48 <moneromooo> Without wanting to sound paternalistic, I assume you installed all dependencies ?
18:59:06 <slave_blocker2> dont know ...
18:59:10 <UkoeHB> slave_blocker2: section 5.4
19:01:12 <slave_blocker2> hello UkoeHB ! :)
19:10:26 <slave_blocker2> i did a sudo apt install python2
19:11:29 <slave_blocker2> i dont know wich dependencys you are mentioning. The mininero repo does not ccontain instructions...
19:11:57 <moneromooo> import foo -> dnf search foo (or similar for your distro)
19:19:34 <slave_blocker2> import bar -> apt-cache search crypto
19:19:48 <slave_blocker2> and now it spits import AggregateSchnorr
19:19:48 <slave_blocker2> ImportError: No module named AggregateSchnorr
19:29:01 <slave_blocker2> ...
19:30:13 <slave_blocker2> anyway, it works now :) . There is a bug there should be : import ASNL in the RingCT.py file .
19:31:14 <moneromooo> Nice :) Not sure anyone is maintaining this, but a PR can't hurt.
19:36:33 <slave_blocker2> are you saying a pull request ? never done that...
19:39:09 <slave_blocker2> Another question, assuming that i finished this translation to portuguese of ztm 2.0, how can i hash the pdf and put that hash in the xmr chain? such that i could prove that it was me who owned it first?
19:41:25 <slave_blocker2> This is even aluded to in the mininero repo :
19:41:38 <slave_blocker2> "This written up research is hashed into the blockchain for timestamping purposes."
19:42:29 <moneromooo> It was probably added in a plaintext payment id. They are now obsolete. 
19:43:25 <moneromooo> You could instead... sign the PDF itself with your secret key, and publish the signature alongside the PDF.
19:43:45 <moneromooo> Then people can verify your monero address is the one that verifies the message.
19:44:26 <moneromooo> Oh. I guess it doesn't include a height, which is what you want... So... sign height || PDF-contents.
19:45:17 <moneromooo> You can also sign using a subaddress IIRC. If you have a recent enough monero tree.
19:51:35 <slave_blocker2> hum,
20:04:37 <UkoeHB> updated seraphis perf results with some optimizations: https://github.com/monero-project/research-lab/issues/91#issuecomment-1047191259
20:32:52 <moneromooo> Thanks for working on this.
20:47:34 <koe000[m]> Ah, it turns out partial-batch-verifying grootle proofs led to ~30% speedup, since adding multiple proofs to one pippinger multiexponentiation is a speedup just by itself.
21:14:22 <sethforprivacy> > The grootle proof verification optimization means Sp-Squashed at 128 ring size can be batch-verified faster than CLSAG with 16 ring size.
21:14:23 <sethforprivacy> A bit over my head, but does this mean there is not a verification hit for jumping to 128 via Seraphis compared to verification after the next HF bumping to ring size 16?
21:14:40 <sethforprivacy> That seems... big, as verification times were still much higher than current in previous estimates.
21:15:30 <sethforprivacy> My main focus in learning more about the verification time implications of moves is to keep up with what to expect for IBD.
21:18:48 <UkoeHB> yes, 128 seraphis-squashed would be faster on average if you have a bunch of txs you can batch-verify with
21:19:16 <UkoeHB> what is IBD?
21:21:00 <sethforprivacy> Initial block download, sorry
21:21:42 <sethforprivacy> UkoeHB: Which would mainly be the case with IBD and nodes that are behind catching up with chain-tip, correct? Well, also with new blocks being verified by nodes as well, I think.
21:23:34 <UkoeHB> iirc the existing code doesn't batch-verify between blocks, so blocks with few txs would take a hit
21:24:06 <sethforprivacy> Makes sense! Still huge news, wasn't aware of that being the case.
21:24:17 <slave_blocker2> https://xmrmemes.com/uploads/memes/f1e9dcb040c97553a70abf0b60bd4079.png
21:24:28 <sethforprivacy> Makes me even more excited for Seraphis, as I was expecting a relatively large verification time hit :D
21:28:32 <merope> slave_blocker2: meme aside, it's really not necessary. Sending back to yourself is the same as sending to a different wallet, from the pov of the anonimity set
21:28:35 <UkoeHB> There is probably a bit more room for optimization, if you combine the BP+ and Grootle pippinger operations into one.