01:22:56 <m-relay> <m​ilas900:matrix.org> For Fcmp++ is it hard fork or soft fork and do we expect two chains at the end ?
01:29:00 <m-relay> <v​tnerd:monero.social> Hard fork. Two chains if something is contentious, which remains to be seen. OVK may be the trigger, if reddit comments are an indication
01:29:26 <jpk68> The Reddit comments are AI slop
02:13:43 <m-relay> <k​iersten5821:matrix.org> how will i know when to upgrade? if i don't upgrade and send a tx will it nuke my privacy once i upgrade and have to send it again on the hard forked chain?
02:16:10 <jpk68> The software does it automatically at the agreed-upon block height for the hardfork. You'll have like 6 months to download the software that supports it before the fork actually happens
02:17:34 <m-relay> <j​effro256:monero.social> ^^^
02:29:40 <m-relay> <j​effro256:monero.social> As for the privacy issue, your send privacy may be "nuked" depending on what your definition of "nuked" is. If it has been multiple days / weeks since the HF, and you try to spend an output pre-fork, your wallet will likely choose decoys solely from the ring-specific chain. If you then spend that output on the FCMP-specific chain, then it would reveal the output <-> key image asso<clipped message>
02:29:40 <m-relay> <j​effro256:monero.social> ciation, which ruins spend privacy on both chains. You could mitigate this by doing a churn to oneself on both chains before spending.
02:34:44 <m-relay> <j​effro256:monero.social> The wallet decoy selection should, if aware of the upcoming fork, pick all decoys from before the fork if spending an output before the fork
15:15:16 -xmr-pr- selsta opened pull request #10335: windows_service: quote service executable path
15:15:16 -xmr-pr- > https://github.com/monero-project/monero/pull/10335
15:17:18 <sech1> That's AI bullying :D
15:30:16 -xmr-pr- selsta opened pull request #10336: windows_service: quote service executable path [release-v0.18]
15:30:16 -xmr-pr- > https://github.com/monero-project/monero/pull/10336
15:30:39 <selsta> at this point I'm tempted to just instantly close every single majority-AI contribution
15:32:36 <m-relay> <o​frnxmr:xmr.mx> Right.. the contributors of them are lazy ah
15:34:19 <selsta> unless it's a clear bug or logic fix it is starting to become really noisy and the review effort is not worth it, we have enough open PRs
15:35:32 <m-relay> <o​frnxmr:xmr.mx> Just claude running on autopilot with a prompt of "send prs for anything you think can be improved"
15:37:49 <selsta> that other person kept trying to edit out the fact he was using claude from the description :D
15:41:55 <m-relay> <o​frnxmr:xmr.mx> Lmao
18:13:23 <selsta> small reminder for those that do gitian builds, it would be great if we have 2-3 more tomorrow
18:14:05 <m-relay> <o​frnxmr:xmr.mx> Will put up in a cpl hrs
18:25:47 <m-relay> <j​effro256:monero.social> Same
18:27:12 <m-relay> <j​effro256:monero.social> Can I review beg for https://github.com/monero-project/monero/pull/10220 ? The actual change is like 9 lines, the rest is unit test cases. It fixes a bug which is needed by the Carrot code
18:58:07 <sech1> looks good, just a couple small comments
20:45:34 <selsta> .merge+ 10220
20:45:34 <xmr-pr> Added
21:45:16 -xmr-pr- jeffro256 opened pull request #10337: cryptonote_basic: fix add_extra_nonce_to_tx_extra() length [RELEASE]
21:45:16 -xmr-pr- > https://github.com/monero-project/monero/pull/10337