14:09:42 I did some testing for this question about the GUI's node pruning behavior: https://libera.monerologs.net/monero-gui/20240401 14:10:20 I used latest GUI release on Linux. I changed the name of the .bitmonero directory and the monero-core.conf file between tests. 14:10:57 When I choose "Simple mode (bootstrap)", there is no screen for configuring the daemon. The monero-core.conf file has pruneBlockchain=true once the wallet is set up. So far, so good. 14:11:15 When I choose "Advanced mode", the "Daemon settings" screen has a "Prune blockchain" checkbox. It is unchecked by default. When I check it, pruneBlockchain in monero-core.conf changes from false to true. 14:11:33 If we wanted to encourage pruning by default more, the "Advanced mode" checkbox for pruning could be checked by default. 14:18:14 hmm I thought it is enabled by default 14:18:30 or maybe not will confirm it 14:19:11 Feel free to double check my tests :) 15:00:06 yes seems I misremembered 15:00:32 but now I'm confused how the current code works 15:02:44 rucknium: we start monerod with the --prune-blockchain flag, how did you find it written into a moneor-core.conf file? 15:03:24 ok seems monero-core.conf is used for persistentsettings, make sense 15:07:06 I noticed that the GUI kept the simple/bootstrap/advanced mode even if I changed the .bitmonero directory name and changed wallet files. So I looked for a config file and found monero-core.conf 15:08:33 https://github.com/monero-project/monero-gui/pull/4320 that should work but not tested yet 15:10:39 Thank you :) 15:12:44 I am writing about different options for increasing the ring size and/or fee to defeat black marble flooding. "Encourage pruning" is one of the options that would reduce the storage impact of larger rings. So now I have something specific to mention about the software instead of just "make memes saying it's ok to prune". 15:18:08 I'm skeptical of inreasing ring size before we fixed performance issues in monerod 15:18:28 we already have issues with nodes falling behind, nodes going out of memory during high tx volume 15:18:39 this is just going to get worse if this isn't fixed before we increase ring sizes 15:39:30 That is an issue. Do you think it will have to be fixed before FCMP? 15:52:55 I don't know. We need someone to investiage it, xFFFC0000 worked on some lock changes but it's unclear if that improves things 15:53:04 it's difficult to reproduce in the first place 23:20:18 .merge+ 4321 23:20:18 Added