17:14:31 b​oog900:monero.social: meeting here in 45 minutes
17:59:11 b​oog900:monero.social: !meeting
17:59:12 m​oo:monero.social: Starting meeting: https://github.com/monero-project/meta/issues/1332
17:59:19 b​oog900:monero.social: 1) greetings
18:00:13 h​into:monero.social: hello
18:01:04 plowsof: 👋
18:01:39 s​yntheticbird:monero.social: hello
18:02:13 b​oog900:monero.social: 2) updates
18:03:30 s​yntheticbird:monero.social: Me: realized one proptest in the onion_addr.rs was wrongly implemented. `addr in [a-z][2-7]{56}` should be `addr in [[a-z][2-7]]{56}`
18:03:41 b​oog900:monero.social: I had a busy week but I managed to add block popping and alt block handling to the new DB, I will PR it in the next couple of days.
18:04:22 h​into:monero.social: me: posted a CCS update: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/591#note_34171 - I've opened PoWER for initial review and will be fixing the merge conflicts then start focusing on Cuprate again
18:05:07 s​yntheticbird:monero.social: Nice. I was confused on if it was ready to review or not ngl
18:06:04 b​oog900:monero.social: > Project: What is next for Cuprate?
18:06:15 b​oog900:monero.social: 3. Project: What is next for Cuprate?
18:06:40 h​into:monero.social: to be clear the `seraphis-migration` PR is open, the Cuprate crate and integration will wait until it's merged
18:06:53 b​oog900:monero.social: With the new database done I will be back on the RPC
18:07:33 b​oog900:monero.social: Wallet catch up is already done and is quick
18:08:01 s​yntheticbird:monero.social: Did you test multiple simultaneous clients scenario ?
18:08:09 s​yntheticbird:monero.social: or is this with only one wallet?
18:08:18 b​oog900:monero.social: Nope, just one
18:08:35 b​oog900:monero.social: Although I think that would be even faster
18:08:49 s​yntheticbird:monero.social: because of cache?
18:08:51 b​oog900:monero.social: Comparing to monerod
18:08:59 s​yntheticbird:monero.social: ah ok
18:09:58 b​oog900:monero.social: Ah yeah it'll be slower than just 1 most likely, maybe on a HDD it would be quicker though as yeah data could be cached
18:11:47 b​oog900:monero.social: Does anyone have anything they would like to discuss?
18:14:04 h​into:monero.social: I think I'll be continuing on bootstrappable builds and misc stuff
18:15:01 h​into:monero.social: not sure if that takes precedence over ZMQ although last time I was going through that code it was boring work :D
18:17:58 b​oog900:monero.social: I would put them at similar levels, ZMQ is only really used for lws and p2pool IIRC
18:19:06 b​oog900:monero.social: And reproducible builds would be needed for a beta release IMO
18:20:58 b​oog900:monero.social: Anything else to discuss today?
18:24:17 s​yntheticbird:monero.social: i think we're all good
18:24:39 b​oog900:monero.social: OK I'll end it here
18:24:42 b​oog900:monero.social: Thanks everyone
18:24:50 s​yntheticbird:monero.social: Thanks
18:24:57 b​oog900:monero.social: !meeting
18:25:00 m​oo:monero.social: - Logs: https://github.com/monero-project/meta/issues/1332#issuecomment-3842938723
18:25:02 m​oo:monero.social: - Next meeting: https://github.com/monero-project/meta/issues/1336
18:30:30 plowsof: Thanks boog900