<oembed><type>rich</type><version>1.0</version><title>MoneroResearchLab wrote</title><author_name>MoneroResearchLab (npub1m0…gcfay)</author_name><author_url>https://yabu.me/npub1m0ner0mtjgs74aghus7qxrxl7mqv06d4v8rz9pmnux2dpr4cmhmsjgcfay</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Code is ready. Target fork Monday 5 Oct 2026; binaries expected within a day. jeffro256 proposed a 10 MB initial penalty-free zone (20 MB blocks if full penalty paid) to skip warm-up and resume prior spam volumes; leftover bugs should match the earlier raise to 625K. RandomX v2 will be in v3. sech1 will ship P2Pool v5.0-beta after pulling Carrot K^j_v rebind (https://github.com/seraphis-migration/monero/pull/456), generator T (https://github.com/monero-project/monero/pull/10963), and carrot_convergence tests. &#xA;&#xA;jberman: We can schedule beta v3 launch during this meeting. The code is now ready to go. Can see all the items we knocked out in that checklist there&#xA;jberman: I think it would be nice to have some testing done on current testnet before the fork as well, but caution that we don&#39;t want people stress testing current testnet&#xA;jberman: Another test that would be good to have people check is migrating a testnet wallet from current testnet to a fork compatible wallet (i.e. create and use a wallet now on current testnet, and then open that wallet with the new beta v3 software)&#xA;jberman: So with that in mind, how about we target Monday Oct 5th for the fork to give people some time to get set up again with current testnet and with the new beta v3 software before the fork. We should be able to get binaries released within the next day&#xA;jeffro256: We also wanted to discuss the initial penalty free zone parameter. Is 10MB okay? Would allow for 20MB blocks at HF if full penalty is paid. A 10MB param would help us skip the initial &#34;warm-up&#34; phase and get back to spamming at volumes similar to when we left off&#xA;rucknium: Oct 5th sounds good to me&#xA;sech1: If RandomX v2 is merged into the stage branch, then version 3 will have it too, right?&#xA;jeffro256: Yes&#xA;sech1: P2Pool&#39;s v5 branch (FCMP++/Carrot/RandomX v2 compatible) is ready for testing then&#xA;sech1: Oct 5th sounds good&#xA;rucknium: jeffro256: Have all the bugs have been fixed with that? (the hard way?)&#xA;sech1: I&#39;ll have P2Pool v5.0-beta release before that&#xA;jeffro256: sech1: Does that branch have this change in it?: https://github.com/seraphis-migration/monero/pull/456.&#xA;jeffro256: Or at least uses the carrot_core code that is up-to-date with fcmp++-stage?&#xA;jeffro256: If using an up-to-date carrot_core, then nothing else needs to be done&#xA;sech1: No, it doesn&#39;t&#xA;sech1: I&#39;ll go through all the changes and update P2Pool side&#xA;sech1: It doesn&#39;t use carrot_core code. All math is tailor-made for P2Pool&#xA;jeffro256: IIRC that&#39;s the only backwards-incompatible change to Carrot since beta v2&#xA;sech1: yeah, if it was merged 15 hours ago, P2Pool definitely doesn&#39;t have it yet&#xA;jeffro256: Changes are posted to the spec repo, the tweak is very simple on the sender side&#xA;jeffro256: Does p2pool implement scanning code?&#xA;sech1: No&#xA;sech1: It does &#34;scanning&#34; by reconstructing the sender side for each output. But it&#39;s only used to display &#34;this wallet got this much XMR in this block&#34; message&#xA;jeffro256: Ok sweet, then hopefully it shouldn&#39;t be too hard. In the d_e derivation, simply include K^j_v right after K^j_s&#xA;sech1: sounds simple enough&#xA;jeffro256: There was also the T generator change: https://github.com/monero-project/monero/pull/10963, so make sure that that value matches upstream&#xA;jeffro256: The T value was also updated in the spec&#xA;jeffro256: I&#39;m sure you know, but there&#39;s always the carrot_convergence tests to verify impls against: https://github.com/seraphis-migration/monero/blob/fcmp%2B%2B-stage/tests/unit_tests/carrot_convergence.cpp&#xA;jeffro256: rucknium: It should be the same bugs that we fixed increaseing it to 625&#xA;jeffro256: 625K&#xA;sech1: jeffor256 yes, I know about generator T, and I did integrate the convergence tests&#xA;https://libera.monerologs.net/monero-research-lab/20260923#c710138&#xA;nostr:nevent1qvzqqqqqqypzpkl8jxlkhy3pat630epuqvxdlakqcl5m2cwxy2rh8cv56z8t3h0hqqsw7cdr6ed3y3v2ku0uplp20fhm5qx2jd0fyyrgp8guamscu4zhptqy226wd </html></oembed>