-
xmr-pr
Ap4sh opened pull request #11361: rpc: handle embedded NULs in ZMQ JSON
-
xmr-pr
-
br-m
<pyxmr2025:mozilla.org> .merge+ 11131 what it means? what can xmr-pr do?
-
br-m
<pyxmr2025:mozilla.org> Ugh, seriously. PR #11345 is ready for review now.
-
br-m
<pyxmr2025:mozilla.org> I kept getting CI errors for this at school, even though it worked fine the first time.
-
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).🤣🤣🤣
-
br-m
<entropyhoover:matrix.org> xmr-pr is just a bot reporting new issues and prs
-
br-m
<pyxmr2025:mozilla.org> sure. but what .merge+ **** means
-
br-m
<ofrnxmr:xmr.mx> @entropyhoover:matrix.org: And tracks the merge queue
-
br-m
<ofrnxmr:xmr.mx> @pyxmr2025:mozilla.org: Adds a pr to the queue
-
br-m
<ofrnxmr:xmr.mx> .merge- removes
-
br-m
<pyxmr2025:mozilla.org> what queue do?
-
br-m
<pyxmr2025:mozilla.org> for core to watch more easily?
-
br-m
<ofrnxmr:xmr.mx> Nothing
-
br-m
<jpk68:matrix.org> Thanks, we can tell > <@pyxmr2025:mozilla.org> Ugh, seriously. PR #11345 is ready for review now.
-
br-m
<ofrnxmr:xmr.mx> for maintainers to track what is ready
-
br-m
<pyxmr2025:mozilla.org> ok, I known now.
-
br-m
<pyxmr2025:mozilla.org> thanks!
-
xmr-pr
selsta opened pull request #11363: wallet2: reset scan status for already processed outputs [release-v0.1...
-
xmr-pr
-
xmr-pr
selsta opened pull request #11362: wallet2: reset scan status for already processed outputs
-
xmr-pr
-
xmr-pr
selsta opened pull request #11364: wallet2: ignore long PIDs when block version is unknown
-
xmr-pr
-
br-m
<entropyhoover:matrix.org> Are some members only on irc?
-
br-m
<entropyhoover:matrix.org> Does the relay bot create dummy account on matrix side for bridging the message?
-
br-m
<jpk68:matrix.org> Yes
-
br-m
<ofrnxmr:xmr.mx> @entropyhoover:matrix.org: Yes
-
br-m
<jeffro256> .merges
-
br-m
<jeffro256> sudo .merges
-
br-m
<jpk68:matrix.org> Only works on IRC :)
-
jeffro256
.merges
-
xmr-pr
10864 10964 11131 11248 11263 11264 11265 11290 11291 11292 11306 11307 11321
-
jeffro256
Can we add 11155 plz?
-
chmod
Hello, is there any additional places that can be used to get security announcements/news outside of this channel and mailing list?
-
xmr-pr
SNeedlewoods opened pull request #11365: wallet_rpc: get wallet info
-
xmr-pr
-
selsta
chmod: mailing list is the best place for high severity issues
-
selsta
otherwise release notes
-
chmod
selsta: okay, so what I was expecting :) thank you!
-
selsta
on our hackerone older stuff also gets disclosed
-
chmod
ah, mostly just if I need to update something immediately.
-
selsta
I would still from time to time update monerod.
-
chmod
of course.
-
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.
-
chmod
is there any better option than to
-
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?
-
br-m
<ofrnxmr> You can query for the tx hash
-
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.
-
br-m
<ofrnxmr:xmr.mx> i dont think downloading blocks is mroe efficient than a simple tx lookup
-
chmod
Ah, I am referring to the monero-rpc-wallet, not directly with monerod.
-
br-m
-
Semisol
Ah, yeah, not that. Also, sorry, my connection seems to be going down too much
-
xmr-pr
thomasbuilds opened pull request #11366: wallet2: bound the timestamp-to-height search
-
xmr-pr