00:17:48 <UkoeHB> nahnahnah722828[: The tx size increase will be similar to the upcoming fork which increases ring size from 11 to 16. Around 10-20% I think.
00:23:58 <r4v3r23[m]> <UkoeHB> "nahnahnah722828: The tx size..." <- so +10-20% twice?
00:33:04 <sethforprivacy> <r4v3r23[m]> "so +10-20% twice?" <- No, the same size as after the upcoming hard-fork.
00:42:06 <UkoeHB> From 11 -> 16 is one increase, then 16 -> 128 (seraphis) is another increase. A seraphis tx would be around 70% larger than current txs I think. There aren't any next-gen protocols smaller than this (triptych would be a similar size).
00:44:19 <nahnahnah722828[> So if you’re using the Monero Gui in simple node using Tor, you really don’t lose any privacy/security.  
00:44:19 <nahnahnah722828[> Since it doesn’t give away your view key, the only thing a malicious actor could get is a Tor ip, and a transaction ID. They can’t see the sender’s address, receiver, or amount.
00:44:19 <nahnahnah722828[> Why isn’t this encouraged more ? The blockchain size is a huge pain in the ass for a lot of users, I think that for monero adoption we need a viable good alternative to downloading a whole 200gb blockchain that’s constantly increasing 
00:44:45 <UkoeHB> Nvm it is 50%. Triptych would be 95% bigger.
00:45:56 <selsta> nahnahnah722828[: please keep the GUI messages in the GUI channel, this is unrelated to dev
00:48:12 <r4v3r23[m]> <UkoeHB> "From 11 -> 16 is one increase..." <- that's how i understood it, as 2 increases
08:39:05 <ErCiccione> <selsta> "whatever fits better for you..." <- Saturday is good for me. Is it ok for people? Saturday 17 UTC?
09:27:58 <rbrunner> ErCiccione: Tomorrow 17:00 UTC would be ok for me. I just hope it's not on too short a notice for key people ...
09:28:21 <ErCiccione> Sunday would be fine as well, but i don't know if there are other meetings
09:32:59 <nioc> monerokon planning meeting is Sun 1800 UTC
09:41:30 <ErCiccione> then saturday makes more sense i guess
09:47:05 <nioc> either should work, not much crossover
15:56:33 <r4v3r23[m]> <rbrunner> "ErCiccione: Tomorrow 17:00 UTC..." <- ping or msg them
16:40:47 <rbrunner> selsta: For a tentative dev meeting tomorrow 17:00 UTC, do you have a nice workflow prepared to ping people, or does that usually work "ad hoc"?
16:44:44 <selsta> I don't have anything prepared for that
16:44:54 <rbrunner> So just make some noise :)
16:45:07 <rbrunner> But such a meeting does seem to make sense, right?
16:45:38 <selsta> I mean we can talk about the current hardfork status, on maybe make some decisions on some things that are not clear at the moment.
16:46:56 <nahnahnah722828[> <rbrunner> "selsta: For a tentative dev..." <- How do I join the dev meeting
16:47:18 <selsta> you just read
16:47:55 <selsta> there isn't anything you have to do to join
16:48:02 <moneromooo> If you PR 5 to 49 good PRs, you can read. 50-99, you can write. 100+, we read what you write :D
16:49:25 <moneromooo> (but yes, you just show up at the stated time, just keep on topic)
17:03:23 <r4v3r23[m]> moneromooo: how's the output PR going? does your latest commit fix the issue jberman94 mentioned?
17:03:56 <moneromooo> The export size one ? I think so.
17:04:34 <r4v3r23[m]> yes
17:04:36 <moneromooo> Except the "doing this would save some more", not enough gain/effort IMHO.
17:05:01 <r4v3r23[m]> what do you mean?
17:06:11 <moneromooo> I mean I did not do one thing he mentioned to save more space.
17:09:01 <r4v3r23[m]> ok. the savings are already killer, anything more is a bonus
17:15:18 -xmr-pr- jeffro256 opened pull request #8226: Fix typo: SERIALIZE_TYPE_DUOBLE
17:15:18 -xmr-pr- > https://github.com/monero-project/monero/pull/8226
17:17:01 <moneromooo> The floodgates open...
17:22:46 <rbrunner> As far as I can see the biggest insecurity right now regarding the hardfork is multisig, with 2 PRs from UkoeHB
17:23:04 <rbrunner> https://github.com/monero-project/monero/pull/8149, reviewed by vtnerd
17:23:25 <rbrunner> https://github.com/monero-project/monero/pull/8220, tested by myself just today
17:25:02 <rbrunner> The third one looks like it could wait until after the hardfork without big loss: https://github.com/monero-project/monero/pull/8203
17:26:03 <r4v3r23[m]> rbrunner: these require a hard fork? 
17:27:38 <rbrunner> Maybe not strictly, from a technical point of view, but I think a hardfork would be a very good point in time to let them go live
17:28:11 <rbrunner> Because then you can be sure that any prospective multisig partner of yours is on the same level of functionalility
17:30:18 -xmr-pr- jeffro256 opened pull request #8227: [release-v0.17] Don't require --rpc-login with --rpc-access-control-or...
17:30:18 -xmr-pr- > https://github.com/monero-project/monero/pull/8227
17:31:41 <r4v3r23[m]> if that's the case, i think its a good idea to update the hardfork planning page with confirmed features along with updated timelines
18:19:25 <hyc> if anybody is looking for a project, ShapeShift DAO is now open source https://twitter.com/hyc_symas/status/1507392436976246785
18:34:45 <rbrunner> Thinking about it, a hardfork date fixing dev meeting not tomorrow, but tomorrow in 1 week, i.e. April 2, would be better IMHO
18:35:10 <rbrunner> We would have time to properly announce it in a meta, with more than 1 day of headstart for people who want to attend
18:35:32 <rbrunner> I could offer to go over the PRs on Sunday and try to write an overview
18:35:55 <rbrunner> And maybe some multisig stuff could be cleared up already in Wednesday's MRL meeting
20:06:28 <nahnahnah722828[> Where will the dev meeting be hosted?
20:07:46 <moneromooo> Here.