17:59:58 b​oog900:monero.social: !meeting
18:00:01 m​oo:monero.social: Starting meeting: https://github.com/monero-project/meta/issues/1348
18:00:03 b​oog900:monero.social: 1) greetings
18:01:59 h​into:monero.social: hello
18:03:06 b​oog900:monero.social: 2) updates
18:05:13 b​oog900:monero.social: Me: ported the wip RPC changes to the new db branch, on the RPC stage branch. Also found and fixed a bug in the tapes
18:06:35 h​into:monero.social: me: testing new DB changes
18:06:42 h​into:monero.social: It synced <24hr with max 2GB, no OOMs and has been stable - this is full verification fyi, IIRC it took ~4 days with old cuprated although I'll be testing it again
18:07:09 s​bt:nope.chat: meow
18:07:16 b​oog900:monero.social: Wow
18:07:23 b​oog900:monero.social: That's crazy
18:07:35 b​oog900:monero.social: How many threads?
18:07:35 h​into:monero.social: 🎉
18:08:01 h​into:monero.social: 6
18:08:39 b​oog900:monero.social: I didn't realize how much it would improve full verification sync
18:09:10 h​into:monero.social: I wonder if I could get away with 1GB...
18:09:58 b​oog900:monero.social: I would try fast sync first
18:10:09 h​into:monero.social: although we still don't have numbers on memory usage of a public `cuprated` getting hit with a bunch of RPC requests
18:10:25 h​into:monero.social: I assume OOMs will occur there
18:11:43 b​oog900:monero.social: Yeah with 2GBs. Although we could and will add a rate limit to prevent this.
18:11:58 b​oog900:monero.social: 3) Project: What is next for Cuprate?
18:12:23 b​oog900:monero.social: I'll be opening a CCS soon to work on RPC
18:13:13 b​oog900:monero.social: Current numbers are with cuprate a local wallet can fully sync in under 23 minutes, with monerod it was over an hour.
18:13:34 h​into:monero.social: do you plan on making any large changes to the existing RPC system?
18:13:56 b​oog900:monero.social: No not really
18:14:03 b​oog900:monero.social: Just filling in what's already there
18:14:33 b​oog900:monero.social: This can be self tested with the RPC stage branch too
18:15:10 b​oog900:monero.social: Also we will no longer have 0xFFC working on RPC, they closed their CCS
18:17:23 j​babb:cypherstack.com: I have been cleaning up and cherrypicking old work forward, porting it from the original monero-serai to monero-wallet. here's an example:
18:17:25 j​babb:cypherstack.com: https://github.com/sneurlax/cuprate/tree/feat/regtest
18:18:16 j​babb:cypherstack.com: idk if this is going to be useful for or suitable in mainline cuprate but I am using it to test monero wallet development and multisig stuff using something very similar to this. but the older code is called cuprate-simnet and is pretty dirty, I didn't want to show that yet, personal project stuff
18:18:34 j​babb:cypherstack.com: anyways that included some very very minor mostly-mock rpc stuff. what all's needed for rpc?
18:19:07 j​babb:cypherstack.com: and should I update this by merging new-db into it or is it just a dead end tech demo at this point?
18:19:49 j​babb:cypherstack.com: this is an example of the point: https://github.com/Cuprate/cuprate/compare/main...sneurlax:cuprate:feat/regtest#diff-0fae4dcac8928774cbb0c9feac8a6173077c2f66624cf2574984dd3aae75ceb9
18:20:12 j​babb:cypherstack.com: motivation: I was doing some Alice, Bob, and Charlie multisig experiments and needed something quicker than stagenet for testing
18:22:56 j​babb:cypherstack.com: finally, I wonder if the RPC work lines up with this because ideally we could control this regtest node over RPC and that's where I was going to go with it next
18:24:25 b​oog900:monero.social: hmm is that code filling in monero-oxide's RPC traits with our DB backend?
18:26:28 j​babb:cypherstack.com: yes lol
18:26:50 b​oog900:monero.social: ah nice kayaba has been asking me to do something like that
18:27:12 j​babb:cypherstack.com: I considered it just a hack to get what I wanted
18:27:36 b​oog900:monero.social: it wont help with the real RPC sadly though
18:28:52 j​babb:cypherstack.com: can I find out about RPC work needed via https://github.com/Cuprate/cuprate/issues?q=is%3Aissue%20state%3Aopen%20rpc ?
18:29:12 b​oog900:monero.social: As our DB currently only allows 1 process to access it, I don't know if it will be usable in a real world project ngl
18:29:20 b​oog900:monero.social: but it is still cool
18:29:25 j​babb:cypherstack.com: does that apply to new-db, too?
18:29:40 j​babb:cypherstack.com: I had merged that in and resolved conflicts enough for it to run last night but need to clean it up before pushing
18:30:11 j​babb:cypherstack.com: then I wondered if I even needed to do that--that is, if it should even be PRed at all (I think no, not in this state, anyways)
18:30:27 b​oog900:monero.social: the old DB alllows multi-process access, the new one (on the new-db branch) does not.
18:30:52 h​into:monero.social: current (LMDB) allows multi-process access, redb and new-db (fjall) both do not
18:31:05 h​into:monero.social: off by 1 second
18:32:17 b​oog900:monero.social: I think if you impl the traits for the tower::Service DB interface it could be useful
18:32:50 b​oog900:monero.social: as that will be exposed when people embed cuprated
18:33:55 j​babb:cypherstack.com: it was useful just personally for playing with a new p2pool-rs and some sharechain work in addition to testing multisig tx flows but idk what a "real" cuprate regtest mode would look like or enable
18:34:34 j​babb:cypherstack.com: would such a mode or some end-to-end tests enabled by that be helpful at all or is everything else needed more important?
18:34:53 j​babb:cypherstack.com: would such a mode or some end-to-end tests enabled by that be helpful at all or is everything else that's* needed more important atm?
18:36:53 b​oog900:monero.social: it would be helpful, especially for the people already using monerod in regtest mode. I think it should work in the same way to monerod.
18:37:29 b​oog900:monero.social: I have already thought of making a kind of tx fuzzer and testing them against both nodes, that sort of mode will be needed I think
18:39:16 b​oog900:monero.social: anything else to discuss today?
18:42:19 b​oog900:monero.social: I think we can end here, thanks everyone!
18:42:42 b​oog900:monero.social: !meeting
18:42:50 m​oo:monero.social: - Logs: https://github.com/monero-project/meta/issues/1348#issuecomment-4033650689
18:42:50 m​oo:monero.social: - Next meeting: https://github.com/monero-project/meta/issues/1351
18:43:31 j​babb:cypherstack.com: oh, sorry, I didn't realize it was a meeting, damn
18:43:36 j​babb:cypherstack.com: dang, now I'm logged 😭
18:51:49 b​oog900:monero.social: lol
18:52:38 b​oog900:monero.social: it was a valid discussion, now the world can see your work :p