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.

<UkoeHB> "nahnahnah722828: The tx size..." <- so +10-20% twice?

<r4v3r23[m]> "so +10-20% twice?" <- No, the same size as after the upcoming hard-fork.

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).

So if you’re using the Monero Gui in simple node using Tor, you really don’t lose any privacy/security.

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.

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

Nvm it is 50%. Triptych would be 95% bigger.

nahnahnah722828[: please keep the GUI messages in the GUI channel, this is unrelated to dev

<UkoeHB> "From 11 -> 16 is one increase..." <- that's how i understood it, as 2 increases

<selsta> "whatever fits better for you..." <- Saturday is good for me. Is it ok for people? Saturday 17 UTC?

ErCiccione: Tomorrow 17:00 UTC would be ok for me. I just hope it's not on too short a notice for key people ...

Sunday would be fine as well, but i don't know if there are other meetings

monerokon planning meeting is Sun 1800 UTC

then saturday makes more sense i guess

either should work, not much crossover

<rbrunner> "ErCiccione: Tomorrow 17:00 UTC..." <- ping or msg them

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"?

I don't have anything prepared for that

So just make some noise :)

But such a meeting does seem to make sense, right?

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.

<rbrunner> "selsta: For a tentative dev..." <- How do I join the dev meeting

you just read

there isn't anything you have to do to join

If you PR 5 to 49 good PRs, you can read. 50-99, you can write. 100+, we read what you write :D

(but yes, you just show up at the stated time, just keep on topic)

moneromooo: how's the output PR going? does your latest commit fix the issue jberman94 mentioned?

The export size one ? I think so.

yes

Except the "doing this would save some more", not enough gain/effort IMHO.

what do you mean?

I mean I did not do one thing he mentioned to save more space.

ok. the savings are already killer, anything more is a bonus

The floodgates open...

As far as I can see the biggest insecurity right now regarding the hardfork is multisig, with 2 PRs from UkoeHB

monero-project/monero #8149, reviewed by vtnerd

monero-project/monero #8220, tested by myself just today

The third one looks like it could wait until after the hardfork without big loss: monero-project/monero #8203

rbrunner: these require a hard fork?

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

Because then you can be sure that any prospective multisig partner of yours is on the same level of functionalility

if that's the case, i think its a good idea to update the hardfork planning page with confirmed features along with updated timelines

if anybody is looking for a project, ShapeShift DAO is now open source twitter.com/hyc_symas/status/1507392436976246785

Thinking about it, a hardfork date fixing dev meeting not tomorrow, but tomorrow in 1 week, i.e. April 2, would be better IMHO

We would have time to properly announce it in a meta, with more than 1 day of headstart for people who want to attend

I could offer to go over the PRs on Sunday and try to write an overview

And maybe some multisig stuff could be cleared up already in Wednesday's MRL meeting

Where will the dev meeting be hosted?

Here.