jpk68 opened pull request #11408: db_lmdb: fix unaligned read of pruning seed

> monero-project/monero #11408

<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

<ofrnxmr> Wrong place. Try #monero:monero.social

.merge+ 11007 11261 11346 11347 11348 11349 11350 11351 11352 11355 11356 11359 11360

Added

Ap4sh opened pull request #11409: wallet-rpc: bind before loading the wallet

> monero-project/monero #11409

.merges

10964 11007 11261 11306 11343 11346 11347 11348 11349 11350 11351 11352 11355 11356 11359 11360

<thomasbuilds:matrix.org> 11343 has a review in #monero-slop:monero.social

.merges

10964 11007 11306 11343

<pyxmr2025:mozilla.org> 11345 has review, too.

<ofrnxmr:xmr.mx> does it have 2 reviews

only a couple left until we can tag monero-project/monero #11009

<pyxmr2025:mozilla.org> @ofrnxmr:xmr.mx: yes

<pyxmr2025:mozilla.org> mrelay.p2pool.observer/m/mozilla.or…143bf95887a32103883503811690496.png (image.png)

<ofrnxmr:xmr.mx> it only has 1 since your force push

<ofrnxmr:xmr.mx> (9but was just a test change)

<pyxmr2025:mozilla.org> yeah

<ofrnxmr:xmr.mx> anwyay, dont be pushy

<pyxmr2025:mozilla.org> ok, I known

<pyxmr2025:mozilla.org> what should I do now

<ofrnxmr:xmr.mx> nothing, just be patient

<pyxmr2025:mozilla.org> wait for another reviewer or venerd?

<jpk68:matrix.org> Just wait, lol

<jpk68:matrix.org> It's not an emergency

<pyxmr2025:mozilla.org> ok. thanks

<pyxmr2025:mozilla.org> why some PR's title have [release-v0.18]

<ofrnxmr:xmr.mx> because they are bug fixes for the release builds

<ofrnxmr:xmr.mx> opened against the release-v0.18 branch

<pyxmr2025:mozilla.org> what relationship between master and release-v0.18 branch

<ofrnxmr:xmr.mx> release is for the binaries that are distributred, master includes all new features and is the "bleeding edge"

<ofrnxmr:xmr.mx> master supports newer c++(17), newer dependencies, new features, etc

<pyxmr2025:mozilla.org> when master can be release (0.19 or next version）

<ofrnxmr:xmr.mx> release is more like an LTS that typically just gets bug fixes with no breakage to existing workflows

<ofrnxmr:xmr.mx> release v0.19 is based on master, yes

<pyxmr2025:mozilla.org> oh. thanks. I known

<ofrnxmr:xmr.mx> if you think your auth pr belongs in v0.19, you can ask selsta to add the "needs backport" label

<pyxmr2025:mozilla.org> Will we release a beta version?

<ofrnxmr:xmr.mx> we dont do betas

<pyxmr2025:mozilla.org> What if it's not needs backport

<ofrnxmr:xmr.mx> v0.18.5.3 will be the last v0.18 series release (unless it is broken), followed by v0.19

<ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: then it will only be in master and not v0.19

<pyxmr2025:mozilla.org> PR without needed backports will always stay in the master, rather than the released version?

<ofrnxmr:xmr.mx> not always

<ofrnxmr:xmr.mx> the needsbackport label is temporary. only for v0.19 staging

<pyxmr2025:mozilla.org> what it means

<ofrnxmr:xmr.mx> after we release this last v.018, then submissions to v0.19 will be done by the author

<pyxmr2025:mozilla.org> ok, I known

<ofrnxmr:xmr.mx> so there will be a [release-v0.19] paired with the master version

<pyxmr2025:mozilla.org> There are already 0.19 branches, why not submit now

<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

<pyxmr2025:mozilla.org> I understand, thank you very much

<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

<pyxmr2025:mozilla.org> #11328

<pyxmr2025:mozilla.org> mrelay.p2pool.observer/m/mozilla.or…89764dfd50e92103899690419355648.png (image.png)

<pyxmr2025:mozilla.org> why there both 0.18 and need backport

<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!" (arxiv.org/pdf/2609.10260) ? I wrote a patch that seems to defeat the attack.

can you send it to me on matrix?

I have not seen it yet

<jpk68:matrix.org> Will this first be discussed in a research meeting, or otherwise publicly explained?

<rucknium> Yes I will send it.

<jpk68:matrix.org> Prior to being included in a release, I mean

<rucknium> It can easily be publicly explained.

<rucknium> I want to make diagrams, but I don't know how much time I have for that.

<ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: Bcuz it needs to be ported to v0.19 too

<pyxmr2025:mozilla.org> ok

jpk68 opened pull request #11410: multisig: cover wrong-content-same-count import rejection

> monero-project/monero #11410