07:45:55 <m-relay> <s​darioz:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/wTGOzaCpbfqKpfAbvkvBYqUx
07:45:58 <m-relay> <s​darioz:matrix.org> (from exch.pw)
07:46:08 <m-relay> <s​darioz:matrix.org> Can someone clarify that statement?
07:47:58 <m-relay> <s​darioz:matrix.org> What they mean with "serious infosec issues"?
07:51:04 <sech1> They can compile v0.18.3.3 themselves, all instructions are out there
08:42:12 <sech1> I don't know why they quote infosec issues as a reason for not using the binaries. We have reproducible builds double checked by several people every time, and they can build exactly (byte to byte) the same binaries themselves.
09:25:15 <m-relay> <1​23bob123:matrix.org> There talking shit, ignore
09:34:58 <rbrunner> Don't waste any chance for a little jab against Monero
09:51:12 <plowsof> Some bugs only happen on self compiled versions, let them do their thing at their own detriment.. the freedom of FOSS (no issues opened or reports) maybe they can sponsor a fix/investigation just like they where a monerokon sponsor 
09:53:45 <sech1> Actually I did have a wallet crashing (self-compiled) when trying to consolidate a lot of testnet inputs. Release binary worked just fine.
10:33:34 <m-relay> <s​darioz:matrix.org> Yeah. 
10:33:34 <m-relay> <s​darioz:matrix.org> That was interesting
10:33:34 <m-relay> <s​darioz:matrix.org> I'm genuinely curious to know about what they have to say haha, if they are so concerned about a binary that was tested thoroughly by the community and the core team, they must have way more than just a single argument,, I want to see that
11:38:07 <m-relay> <s​yntheticbird:monero.social> bold claims requires bold proofs, indeed.
12:51:09 <m-relay> <s​iren:kernal.eu> https://www.bitdefender.com/blog/hotforsecurity/cryptocurrency-monero-website-hacked-original-binaries-replaced/
12:51:09 <m-relay> <s​iren:kernal.eu> https://github.com/monero-project/meta/issues/916#issuecomment-1791756009
21:28:34 <aog> is it possible for a monero wallet to generate a subaddress via jsonrpc that then I cannot find in the wallet issuing the `address all` command?
21:31:54 <moneromooo> If you're using an out of date wallet cache.
21:32:54 <aog> where is this cache stored? I just opened the wallet using ./monero-wallet-cli
21:33:14 <moneromooo> . or wherever you specify.
21:33:23 <moneromooo> So, probably . here.
21:33:35 <moneromooo> If your wallet is X.keys, the cache is X.
21:34:09 <moneromooo> You also need to save it if you use monero-wallet-rpc in directory mode. In single file mode, it's already saved on exit.
21:34:29 <moneromooo> Subaddresses are deterministic anyway, so you can just generate it again, it'll be the same.
21:34:29 <aog> and X is a binary file?
21:34:36 <moneromooo> Yes.
21:34:52 <aog> the `refresh` command doesn't update the cache?
21:35:01 <moneromooo> Correct.
21:36:18 <aog> interesting, the address I generated programmatically using ./monero-wallet-rpc was not shown in -cli though as soon as I typed: address new -- the same address appeared
21:36:34 <aog> though I still cannot see the payment sent to that address, even if the wallet is synced
21:36:54 <moneromooo> That wallet probably refreshed hte block wiht that payment before it knew about the subaddress.
21:37:20 <moneromooo> You can use... rescan_tx IIRC ? A new command which scans just one tx. Avoids rescanning all.
21:38:15 <aog> trying...
21:38:49 <aog> Error: Unknown command 'rescan_tx': it's probably time to update the wallet :)
21:47:40 <aog> moneromooo, I got the latest cli wallet, though I cannot seem to find the rescan_tx command
21:57:25 <moneromooo> Might be another name. I did not add it.
21:57:34 <moneromooo> scan_tx maybe ?
22:02:14 <aog> thank you very much moneromooo for passing over your knowledge, appreciate
22:04:06 <moneromooo> yw
23:42:12 <Mochi101> moneromooo, have you ever seen this?
23:42:13 <Mochi101> Synced 3103841/3105910 (99%, 2069 left)
23:42:14 <Mochi101> 2024-03-15 23:35:04.856 I [110.40.229.103:18080 OUT] Sync data returned a new top block candidate: 3103841 -> 4557091 [Your node is 1453250 blocks (5.5 years) behind]
23:42:51 <Mochi101> There are a few of them.
23:52:24 <m-relay> <g​fdshygti53:monero.social> Yeah, normal fake nodes