00:18:27 left a comment here: https://github.com/monero-project/monero/pull/8513/files#r952031123 01:20:29 .merges 01:20:29 -xmr-pr- 8299 8323 8333 8352 8359 8379 8381 8415 8419 8427 8428 8442 8444 8450 8460 8462 8464 8465 8486 8490 8491 8495 8496 8497 03:53:08 .merge- 8464 03:53:08 Removed 06:56:08 Who handles the gitlab server at repo.getmonero.org? There are a ton of spam repos and groups 06:59:29 I do. Kinda. If you find a way to remove them easily, let me know. 07:38:49 Not familiar with gitlab server, I'm afraid :/ 13:13:43 Hi.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5beca1d1db815988f29ffde0502f155d17de2a85) 13:19:15 I also passed `disable-dns-checkpoints=1` and `enable-dns-blocklist=1` to my config file. Maybe this is the reason of disconnect? 13:24:26 "after calling `scan_tx` with ids..." <- opened an issue for this problem: https://github.com/monero-project/monero/issues/8531 14:37:27 Hello guys just curious, why can't we get Monero mathematically proven and formally verified to be correct from its specification to C implementation to binary code? If we treat software program as mathematical proofs to a theorem, then using the rules of induction along with automated theorem prover we can mathematical prove that Monero is secure and correct without relying on cat and mouse game of finding bugs through auditing and bug 14:37:27 bounty 14:56:41 Are you talking about "formal verification"? It sounds like it. As far as I know, that is only possible for programs that are significantly simpler than a code like monero's source. 15:52:50 I assume sometimes the secret spend key must be sent from a client to the daemon. What security precautions are taken for that? I know there is TLS between wallet rpc and daemon, but that's optional. What else is there? I see temp storage in `epee::wipeable_string` as in `wallet_rpc_server::on_query_key()`. Other precaution on the wire? Encryption maybe? 15:53:49 When you say daemon... which daemon do you mean ? wallet daemon or node daemon ? 15:54:10 Because the node doesn't need to see your keys. If one asks, you can be sure they're a scammer. 15:54:53 IIRC query_key was added because someone wanted to be able to get the keys, not sure why. It should not be needed. 15:55:07 Assume that if the keys go over the wire, they're compromised. 15:55:48 Unless SSL with whitelisted certs. Because all that goes through the network stack, and we have no idea where it gets copied to. 15:56:39 And even if SSL with whitelisted certs, the other side may be merrily copying them all over memory. 15:59:01 Also, TLS is encryption. 16:00:02 Ah, actually, thinking about it, there is one good reason to send keys over the wire: creating a new wallet. 16:00:12 Same thing applies. 16:05:10 Hey congrats on passing 11K commits y'all ! 16:06:04 "Are you talking about "formal..." <- That's not true. It may be difficult to formally verify large programs but it's not impossible. Gernot Heiser has proven that formal verification scales decently even with software with millions of lines of code. It's just expensive but otherwise very well worth it especially for a software like Monero committed to financial privacy 16:09:59 dark: You can submit a CCS funding proposal to perform such a verification. 16:29:49 I mean the node daemon. I assumed (maybe I'm wrong) that when you create a transaction from a wallet and broadcast that to the network, you broadcast that to a daemon and that broadcast needs a private spend key. Does it not? 16:31:50 the transactions gets created on the wallet side, the daemon does not need any key 16:35:38 dark: I'm obviously no expert in formal verification. If this is possible, by all means that would be great. I just thought that formal verification is only possible if you can actually come up with a mathematically precise specification of what the program does and then you verify that and so that is only possible for simpler programs. The problem I see with this is that a code like monero is not written based on some specification. It 16:35:38 is written based on what it needs to do. How do you described that with the language of formal mathematics? Some parts of the math, yes, but every functionality? Sounds science & and fiction to me. But I'm happy to be proven wrong. 16:37:23 selsta: Okay, so the private spend key never leaves the wallet. That's reassuring. 18:15:51 moneromooo: updated with your suggestion https://github.com/monero-project/monero/pull/8519 18:19:16 hmm have to double check if it gets initialized correctly 18:21:14 and have to check if it works correctly on testnet and stagenet 19:51:20 selsta: builds fine on my machine, tests and benchmarks run fine 19:51:48 the library on its own builds fine* idk what's wrong when included as a submodule 19:51:57 what command do you use to build https://github.com/UkoeHB/monero/commit/f7c53b83a22f6d301e105058a490c541fc0e5a0c ? 19:51:59 some cmake voodoo 19:52:06 i'll try to get it working 19:52:32 just regular make 19:53:12 the CI doesn't like it either: https://github.com/UkoeHB/monero/actions/runs/2907157096 19:53:27 some CMake stuff is missing 19:54:39 yeah but it's dying before it even gets to unit tests 19:55:15 clangd also doesn't like that `asm` 20:41:28 UkoeHB: [ OK ] seraphis_crypto.mx25519_sample_tests (0 ms) 20:41:32 will send you the diff 20:43:30 monero changes: https://paste.debian.net/hidden/974b0f33/ mx25519 changes: https://paste.debian.net/hidden/1744bb63/ 21:34:52 selsta: thanks that worked 22:56:12 hi I made a exchange on changlly xmr 1.22 from my monero gui account to changlly and there saying they didn't get it 22:56:44 JB[m]12: do you have a transaction id? 22:57:03 also can you join the monero support channel on matrix? 22:57:53 a47e131c1a58f573de04bd1e58e0e0c7be28ed54239780ca15527370515db50c 22:59:00 * JB[m]12 posted a file: (4554KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/zKWruzldIXsDXtThxlErcbKc/54E498DC-70E5-45A9-8A8E-2AD27855632B.heic > 22:59:21 please join #monero-support:monero.social 22:59:25 #monero-support:monero.social 23:28:14 sorry I got logged off