08:45:33 <xmr-pr> Ap4sh opened pull request #11361: rpc: handle embedded NULs in ZMQ JSON
08:45:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11361
15:07:39 <br-m> <pyxmr2025:mozilla.org> .merge+ 11131 what it means? what can xmr-pr do?
15:19:41 <br-m> <pyxmr2025:mozilla.org> Ugh, seriously. PR #11345 is ready for review now.
15:19:43 <br-m> <pyxmr2025:mozilla.org> I kept getting CI errors for this at school, even though it worked fine the first time.
15:19:54 <br-m> <pyxmr2025:mozilla.org> Got home and figured out it’s because PR #11322 got merged. It changed make_request(args) to make_request(args, uri).🤣🤣🤣
15:21:18 <br-m> <entropyhoover:matrix.org> xmr-pr is just a bot reporting new issues and prs
15:22:31 <br-m> <pyxmr2025:mozilla.org> sure. but what .merge+ **** means
15:22:34 <br-m> <ofrnxmr:xmr.mx> @entropyhoover:matrix.org: And tracks the merge queue
15:22:40 <br-m> <ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: Adds a pr to the queue
15:23:02 <br-m> <ofrnxmr:xmr.mx> .merge- removes
15:23:46 <br-m> <pyxmr2025:mozilla.org> what queue do?
15:24:17 <br-m> <pyxmr2025:mozilla.org> for core to watch more easily?
15:24:20 <br-m> <ofrnxmr:xmr.mx> Nothing
15:24:41 <br-m> <jpk68:matrix.org> Thanks, we can tell > <@pyxmr2025:mozilla.org> Ugh, seriously. PR #11345 is ready for review now.
15:24:45 <br-m> <ofrnxmr:xmr.mx> for maintainers to track what is ready
15:25:18 <br-m> <pyxmr2025:mozilla.org> ok, I known now.
15:25:24 <br-m> <pyxmr2025:mozilla.org> thanks!
16:30:33 <xmr-pr> selsta opened pull request #11363: wallet2: reset scan status for already processed outputs [release-v0.1...
16:30:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11363
16:30:36 <xmr-pr> selsta opened pull request #11362: wallet2: reset scan status for already processed outputs
16:30:37 <xmr-pr> > https://github.com/monero-project/monero/pull/11362
17:00:33 <xmr-pr> selsta opened pull request #11364: wallet2: ignore long PIDs when block version is unknown
17:00:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11364
17:17:16 <br-m> <entropyhoover:matrix.org> Are some members only on irc? 
17:19:22 <br-m> <entropyhoover:matrix.org> Does the relay bot create dummy account on matrix side for bridging the message?
17:20:56 <br-m> <jpk68:matrix.org> Yes
17:21:02 <br-m> <ofrnxmr:xmr.mx> @entropyhoover:matrix.org: Yes
17:53:20 <br-m> <jeffro256> .merges 
17:53:37 <br-m> <jeffro256> sudo .merges
17:53:38 <br-m> <jpk68:matrix.org> Only works on IRC :)
17:54:28 <jeffro256> .merges
17:54:28 <xmr-pr> 10864 10964 11131 11248 11263 11264 11265 11290 11291 11292 11306 11307 11321
17:55:03 <jeffro256> Can we add 11155 plz?
18:23:29 <chmod> Hello, is there any additional places that can be used to get security announcements/news outside of this channel and mailing list?
18:30:33 <xmr-pr> SNeedlewoods opened pull request #11365: wallet_rpc: get wallet info
18:30:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11365
18:31:35 <selsta> chmod: mailing list is the best place for high severity issues
18:31:51 <selsta> otherwise release notes
18:31:54 <chmod> selsta: okay, so what I was expecting :) thank you!
18:32:08 <selsta> on our hackerone older stuff also gets disclosed
18:32:45 <chmod> ah, mostly just if I need to update something immediately.
18:33:46 <selsta> I would still from time to time update monerod.
18:34:00 <chmod> of course.
18:34:59 <chmod> also, I have a question: I am trying to implement payment processing using the monero-rpc-wallet, and I'd like to track payments to subaddresses that are in the mempool + not sufficiently confirmed yet.
18:35:31 <chmod> is there any better option than to
18:37:08 <chmod> 1. use the tx notify handler for new TXs, 2. check all transactions in the last n blocks every time a block notify handler is triggered (also in case of reorgs to delete TXs that go missing), and 3. poll unconfirmed transactions every so often to catch possibly dropped/double-spent transactions that no longer matter?
18:46:01 <br-m> <ofrnxmr> You can query for the tx hash
18:49:52 <chmod> Wouldn't polling the last n blocks of tx history be more efficient with many payments? Also would allow me to catch missed txs.
18:54:56 <br-m> <ofrnxmr:xmr.mx> i dont think downloading blocks is mroe efficient than a simple tx lookup
18:56:40 <chmod> Ah, I am referring to the monero-rpc-wallet, not directly with monerod.
18:58:23 <br-m> <ofrnxmr:xmr.mx> im referring to this https://docs.getmonero.org/rpc-library/monerod-rpc/#get_transactions
19:01:29 <Semisol> Ah, yeah, not that. Also, sorry, my connection seems to be going down too much
21:45:33 <xmr-pr> thomasbuilds opened pull request #11366: wallet2: bound the timestamp-to-height search
21:45:34 <xmr-pr> > https://github.com/monero-project/monero/pull/11366