14:09:42 <koe> what happens when the total money supply exceeds 64bits? it should happen 2 years after the emission tail begins, so about 2024
14:11:02 <kovri-slack> <woodser> does monero-wallet-rpc currently support https through config options to certificates, or is this left to nginx?
14:12:20 <kovri-slack> <woodser> (nginx or similar)
14:24:02 <moneromooo> monero-wallet-rpc supports SSL.
14:34:36 <kovri-slack> <woodser> to clarify, a client can connect to monero-wallet-rpc using SSL?
14:34:50 <kovri-slack> <woodser> I added `--rpc-ssl enabled` to monero-wallet-rpc’s startup args which should generate a temporary self signed certificate per https://github.com/monero-project/monero/pull/4852 but the client throws “TypeError [ERR_INVALID_PROTOCOL]: Protocol ‘https:’ not supported. Expected ‘http:’”
14:34:58 <kovri-slack> <woodser> how is SSL enabled?
14:53:05 <kovri-slack> <woodser> nevermind `--rpc-ssl enabled` worked to enable SSL on monero-wallet-rpc.  The client was not using it correctly
16:58:39 <rehrar> Meeting in a couple of minutes?>
17:00:24 <rehrar> Ok. Meeting time. Anyone around today?
17:00:40 <rbrunner> Yup.
17:00:44 <selsta> yes
17:00:47 <jtgrassie> hi
17:01:06 <rehrar> woohoo
17:01:35 <rehrar> So, tell me, compatriots in attendance...what have you done these past couple of weeks?
17:02:48 <rbrunner> Watch the new year arrive?
17:02:58 <rehrar> 2020 baybee
17:03:04 <rbrunner> Does that count :)
17:03:20 <rehrar> Yeah. I didn't think that there would be too much what with the holidays and all. But maybe someone will have done their homework and surprise me.
17:03:38 <rehrar> I've got the Revuo Periodical to work on (the past half year's worth of stuff)
17:04:16 <selsta> After new year PRs went back to their usual pace again.
17:04:33 <rbrunner> Quite a number of PR's waiting, yes?
17:04:40 <selsta> Work was done mostly on bug fixes.
17:04:51 <rehrar> Snipa you around?
17:05:22 <jtgrassie> I've been doing a few pool things, answering a fair few of koe's q's for z2m revision
17:05:36 <rehrar> oh, he's working on that? Awesome! How's it coming along jtgrassie?
17:05:49 <jtgrassie> looking good
17:05:53 <selsta> He did some merges yesterday so I guess the others will also be merged soon.
17:05:58 <rbrunner> What is "z2m revision"?
17:06:00 <rehrar> Is there any sort of ETA or no?
17:06:04 <rehrar> Zero to Monero
17:06:19 <rehrar> the author (koe) wrote before bulletproofs were implemented and the protocol has evolved since then.
17:06:29 <rehrar> so it's being updated. There was a CCS for it.
17:06:29 <rbrunner> Ah, ok
17:06:53 <jtgrassie> there was also a fair few little things missing
17:07:13 <jtgrassie> those gaps are being plugged
17:08:06 <rehrar> Cool. Well good to know it's being worked on.
17:08:26 <rehrar> We may need a third revision if we ever come to a decision regarding modifying our ring sigs.
17:08:41 <jtgrassie> ^ right!
17:09:07 <rehrar> And then we can just link to it when people ask to "see the white paper"
17:09:32 <rehrar> as that would be more accurate than the bytecoin stuff despite being more of a technical breakdown.
17:09:44 <rehrar> What you been up to selsta?
17:09:55 <rehrar> Did you make the GUI have a brown theme yet?
17:10:05 <selsta> noo
17:10:39 <selsta> I’ve looked into some build stuff / buildbot replacements
17:11:58 <jtgrassie> have you looked into github actions?
17:12:15 <rehrar> Well, unless anyone has anything else to say, maybe...
17:12:39 <rehrar> I think people either forget we have these meetings or think they're not very useful.
17:13:01 <rehrar> Let me ask this question. Should these meetings continue?
17:13:08 <selsta> jtgrassie: yes
17:13:22 <rehrar> The "dev meetings" in their original form was when there was a lot of action from core and devs in the early days of Monero.
17:13:23 <selsta> I have a PR for it open.
17:13:35 <rehrar> So the coordination was helpful.
17:13:48 <jtgrassie> selsta: oh I missed that
17:14:05 <selsta> Windows was a bit of work.
17:14:06 <rehrar> Since then, core team has been taking steps back, dev stuff has been happening more organically. In other words, now that a "culture" of Monero has been established, it seems like these are less necessary.
17:14:47 <jtgrassie> rehrar: meeting still useful, people join when they can
17:14:51 <selsta> I think they can be useful before releases / hardforks.
17:15:09 <rehrar> Perhaps I should give a reminder the day before.
17:15:37 <rehrar> Ok. I'll leave this question open for discussion for those who pop in and out over the course of the days. Perhaps open a meta issue for discussion.
17:15:41 <rehrar> Anything else to report?
17:15:59 <rbrunner> Meta issue for discussion sounds good
17:16:07 <jtgrassie> agreed
17:16:25 <rehrar> Alright. I'll make it.
17:16:40 <rehrar> Well, it looks like we can break unless anyone has anything to say or question to ask.
17:16:53 <rehrar> The four of us should meet up for drinks afterwards.
17:17:16 <rbrunner> Maybe at Konferenco :)
17:17:27 <rbrunner> Is the location known in the meantime?
17:17:50 <rbrunner> And date of course
17:17:51 <rehrar> I think Berlin, but don't quote me on that. I'm kind of purposefully not keeping up with the planning in hopes of not being roped in. :D
17:18:01 <rbrunner> Hah
17:18:03 <jtgrassie> lol
17:18:05 <rehrar> #monero-konferenco is where it's being discussed though. Logs are on mattermost.
17:22:00 <nioc> rbrunner: there will be a meeting in #monero-konferenco Wed the 15th at 19:00 UTC
17:22:17 <rbrunner> Ok, thanks
17:22:21 <nioc> and date and location will be discussed
17:22:58 <jtgrassie> selsta: can you make the test job use the build output?
17:23:37 <selsta> Can be done later with caches. Didn’t look into it yet.
17:23:58 <jtgrassie> https://help.github.com/en/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts#passing-data-between-jobs-in-a-workflow
17:26:14 <selsta> Artifacts is more for single files.
17:27:19 <jtgrassie> I've found the documentation a little difficult to navigate!
17:31:03 <jtgrassie> This seems to suggest artifacts are probably more appropriate for build then tests: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
17:31:06 <selsta> Creating an archive of the build output and uploading it as an artifact could work. Will look into it once it’s merged.
17:33:01 <selsta> It takes 1 to 2 minutes to install dependencies so I’ve found dependency caching not worth it. ccache could be interesting.
17:34:11 <jtgrassie> You don't need to create an archive of build output, just specify the path to upload (which can be a dir).
17:35:22 <jtgrassie> (from looking at the docs briefly)
17:36:35 <selsta> Not clear to me from the docs.
17:37:00 <selsta> It looks like we can specify a path but usually artifacts are single files.
17:38:26 <jtgrassie> They have an example on that page using a path:dist
17:40:10 <selsta> yep looks like it
17:41:54 <jtgrassie> these actions are some way off gitlab's cicd
17:42:20 <jtgrassie> from my casual look over the docs
17:42:53 <jtgrassie> but makes sense to use them if we can for sure
17:46:29 <selsta> The downside of Gitlab CI is that it doesn’t trigger on merge requests: https://gitlab.com/gitlab-org/gitlab-foss/issues/23902
17:46:35 <selsta> so basically useless for us
17:46:52 <selsta> Wrote a comment up here: https://github.com/monero-project/meta/issues/236#issuecomment-572720802
17:56:05 <vtnerd> oh crud the meeting was at noon localtime not 1 -> I've got the amd ASM speedups compiling again against the separate monero-project/supercop repo
17:57:10 <vtnerd> the downside is that the redirections to the ASM must be done in the "device" library which is dependency on a few places (ringct, cryptonote_core) which it arguably shouldn't be
17:57:30 <vtnerd> resulting in unnecessary assembly in monerod. but otherwise it should be working
17:58:08 <jtgrassie> selsta: seems gitlab can do MR pipelines now: https://docs.gitlab.com/ee/ci/merge_request_pipelines/index.html
17:59:33 <selsta> jtgrassie: The problem is that it runs it on the users Gitlab runner.
17:59:48 <selsta> And the average user has no runner setup on a server.
18:00:04 <selsta> You can’t share a single runner with all users.
18:00:20 <selsta> We tested it on the monero-site repo.
18:00:37 <jtgrassie> gotcha
18:06:36 <jtgrassie> vtnerd: cool. what kind of speed difference are you seeing?
18:11:05 <vtnerd> 134% increase for a standard 2-output transaction
18:11:22 <vtnerd> Im doing a _direct_ benchmark though, so I dont know how much it speeds up wallet2 yet
18:11:56 <jtgrassie> great!
18:12:00 <vtnerd> it was easier to compare the crypto steps directly in a separate process
18:12:24 <vtnerd> or no it was ~140% on this laptop. I'm curious what the ryzen will do because the other library might be faster due to the bigger cache