00:30:34 <xmr-pr> jpk68 opened pull request #11408: db_lmdb: fix unaligned read of pruning seed
00:30:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11408
11:06:16 <br-m> <milas900:matrix.org> Hello I am not sure if this is the right form but I’m trying to develop monero market analysis. I need data like web socket what Binance provides , where I can get this for xmr. Happy to hear if you have the input please
12:13:16 <br-m> <ofrnxmr> Wrong place. Try #monero:monero.social
14:19:38 <selsta> .merge+ 11007 11261 11346 11347 11348 11349 11350 11351 11352 11355 11356 11359 11360 
14:19:39 <xmr-pr> Added
14:30:33 <xmr-pr> Ap4sh opened pull request #11409: wallet-rpc: bind before loading the wallet
14:30:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11409
15:51:28 <tobtoht> .merges
15:51:28 <xmr-pr> 10964 11007 11261 11306 11343 11346 11347 11348 11349 11350 11351 11352 11355 11356 11359 11360
16:15:10 <br-m> <thomasbuilds:matrix.org> 11343 has a review in #monero-slop:monero.social
16:20:18 <tobtoht> .merges
16:20:18 <xmr-pr> 10964 11007 11306 11343
16:23:52 <br-m> <pyxmr2025:mozilla.org> 11345 has review, too.
16:24:07 <br-m> <ofrnxmr:xmr.mx> does it have 2 reviews
16:24:13 <selsta> only a couple left until we can tag https://github.com/monero-project/monero/issues/11009
16:24:37 <br-m> <pyxmr2025:mozilla.org> @ofrnxmr:xmr.mx: yes
16:24:52 <br-m> <pyxmr2025:mozilla.org> https://mrelay.p2pool.observer/m/mozilla.org/be736b558789e179195ecacfddf0143bf95887a32103883503811690496.png (image.png)
16:25:28 <br-m> <ofrnxmr:xmr.mx> it only has 1 since your force push
16:25:49 <br-m> <ofrnxmr:xmr.mx> (9but was just a test change)
16:26:08 <br-m> <pyxmr2025:mozilla.org> yeah
16:26:21 <br-m> <ofrnxmr:xmr.mx> anwyay, dont be pushy
16:26:46 <br-m> <pyxmr2025:mozilla.org> ok, I known
16:26:59 <br-m> <pyxmr2025:mozilla.org> what should I do now
16:27:07 <br-m> <ofrnxmr:xmr.mx> nothing, just be patient 
16:27:50 <br-m> <pyxmr2025:mozilla.org> wait for another reviewer or venerd?
16:28:12 <br-m> <jpk68:matrix.org> Just wait, lol
16:28:15 <br-m> <jpk68:matrix.org> It's not an emergency
16:28:35 <br-m> <pyxmr2025:mozilla.org> ok. thanks
17:05:17 <br-m> <pyxmr2025:mozilla.org> why some PR's title have [release-v0.18]
17:05:51 <br-m> <ofrnxmr:xmr.mx> because they are bug fixes for the release builds
17:06:09 <br-m> <ofrnxmr:xmr.mx> opened against the release-v0.18 branch
17:07:42 <br-m> <pyxmr2025:mozilla.org> what relationship between master and release-v0.18 branch
17:08:33 <br-m> <ofrnxmr:xmr.mx> release is for the binaries that are distributred, master includes all new features and is the "bleeding edge"
17:09:40 <br-m> <ofrnxmr:xmr.mx> master supports newer c++(17), newer dependencies, new features, etc
17:10:45 <br-m> <pyxmr2025:mozilla.org> when master can be release (0.19 or next version）
17:10:46 <br-m> <ofrnxmr:xmr.mx> release is more like an LTS that typically just gets bug fixes with no breakage to existing workflows
17:10:56 <br-m> <ofrnxmr:xmr.mx> release v0.19 is based on master, yes
17:11:13 <br-m> <pyxmr2025:mozilla.org> oh. thanks. I known
17:12:17 <br-m> <ofrnxmr:xmr.mx> if you think your auth pr belongs in v0.19, you can ask selsta to add the "needs backport" label
17:12:21 <br-m> <pyxmr2025:mozilla.org> Will we release a beta version?
17:12:30 <br-m> <ofrnxmr:xmr.mx> we dont do betas
17:13:26 <br-m> <pyxmr2025:mozilla.org> What if it's not  needs backport
17:13:35 <br-m> <ofrnxmr:xmr.mx> v0.18.5.3 will be the last v0.18 series release (unless it is broken), followed by v0.19
17:13:52 <br-m> <ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: then it will only be in master and not v0.19
17:14:37 <br-m> <pyxmr2025:mozilla.org> PR without needed backports will always stay in the master, rather than the released version?
17:17:47 <br-m> <ofrnxmr:xmr.mx> not always
17:18:05 <br-m> <ofrnxmr:xmr.mx> the needsbackport label is temporary. only for v0.19 staging
17:18:06 <br-m> <pyxmr2025:mozilla.org> what it means
17:18:29 <br-m> <ofrnxmr:xmr.mx> after we release this last v.018, then submissions to v0.19 will be done by the author
17:19:00 <br-m> <pyxmr2025:mozilla.org> ok, I known
17:19:02 <br-m> <ofrnxmr:xmr.mx> so there will be a [release-v0.19] paired with the master version
17:19:25 <br-m> <pyxmr2025:mozilla.org> There are already 0.19 branches, why not submit now
17:19:51 <br-m> <ofrnxmr:xmr.mx> because we havent released the latest v0.18 yet, and there is a v0.19 staging pr that these commits are backported to
17:20:30 <br-m> <pyxmr2025:mozilla.org> I understand, thank you very much
17:21:19 <br-m> <ofrnxmr:xmr.mx> release final v0.18  -> merge the v0.19 backport pr -> then we will start doing the separate pr for each v0.19 fix
17:29:07 <br-m> <pyxmr2025:mozilla.org> #11328
17:29:11 <br-m> <pyxmr2025:mozilla.org> https://mrelay.p2pool.observer/m/mozilla.org/98d782b72eab197cbc302894474e89764dfd50e92103899690419355648.png (image.png)
17:29:29 <br-m> <pyxmr2025:mozilla.org> why there both 0.18 and need backport
17:31:11 <br-m> <rucknium> selsta: selsta: Is there a chance v0.18.5.3 could include a defense against Shi et al. (2026) "Are Unreachable Nodes Truly Safe? Fully Eclipsing Monero’s P2P Network!" (https://arxiv.org/pdf/2609.10260) ? I wrote a patch that seems to defeat the attack.
17:31:51 <selsta> can you send it to me on matrix?
17:31:57 <selsta> I have not seen it yet
17:32:55 <br-m> <jpk68:matrix.org> Will this first be discussed in a research meeting, or otherwise publicly explained?
17:33:00 <br-m> <rucknium> Yes I will send it.
17:33:03 <br-m> <jpk68:matrix.org> Prior to being included in a release, I mean
17:33:23 <br-m> <rucknium> It can easily be publicly explained.
17:33:41 <br-m> <rucknium> I want to make diagrams, but I don't know how much time I have for that.
17:59:06 <br-m> <ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: Bcuz it needs to be ported to v0.19 too
18:00:32 <br-m> <pyxmr2025:mozilla.org> ok
18:00:33 <xmr-pr> jpk68 opened pull request #11410: multisig: cover wrong-content-same-count import rejection
18:00:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11410