02:44:33 <jeffro256[m]> > https://github.com/monero-project/monero/issues/8360 can someone check if this makes sense? should if there is an rpc error, should there also be an error with the HTTP status code instead of 200?
02:44:33 <jeffro256[m]> I agree with that stack exchange answer. HTTP 200 should be used if the API was accessed and the backend returns a response (whether the user likes it or not) which runs as intended without any kind of backend errors or transport errors or access errors, etc
02:44:44 <jeffro256[m]> It it's only an error on the application layer, code should be 200. That's pretty typically I think
02:45:03 <jeffro256[m]> The error message "failed to open wallet" sucks ass though
04:13:25 <HenryHollingwort> I suppose this is the difference between RPC and REST - it is after wall the wallet rpc - which typically does not use HTTP error code semantics, so I would say that it's best to leave as-is
05:08:44 <MeowingCat> i derived private view key from private spend key
05:08:49 <MeowingCat> it is correct butt
05:09:03 <MeowingCat> my derivation: 85F0891ADF3AACE53525D3227B33417CA74787BDD8C3151DA6AC7B6831E7E5
05:09:36 <MeowingCat> https://xmr.llcoins.net/addresstests.html's derivation: 85f0891adf3aace53525d3227b33417ca74787bdd8c3151da6ac7b6831e7e500
05:10:02 <MeowingCat> what is that "00" at the end???
05:10:30 <MeowingCat> ohhh
05:10:31 <MeowingCat> waittt
05:10:36 <MeowingCat> it is
05:10:46 <MeowingCat> 85F0891ADF3AACE53525D3227B33417CA74787BDD8C3151DA6AC7B6831E7E5000000000000000000000000000000000000000000000000000000000000000000
05:11:01 <MeowingCat> this is derived from 64 bit reducer
05:12:33 <MeowingCat> half of that is 85F0891ADF3AACE53525D3227B33417CA74787BDD8C3151DA6AC7B6831E7E500
05:12:38 <MeowingCat> it is ok
05:16:28 <MeowingCat> or maybe i can remove half things of 64 byte reducer
05:44:50 <luigi1112> 64 byte reducer is mostly artifact from eddsa reference afaik
06:22:25 <MeowingCat> is this reducer thing doing something like moving the point onto curve function?
06:23:48 <MeowingCat> i think scalar value for reducer is x or y of the point
06:42:07 <luigi1112> reducer only acts on private keys which is just a simple integer
08:29:57 <MeowingCat> i have to make words portable somehow
08:30:28 <MeowingCat> i have words for ETH and BTC
08:30:37 <MeowingCat> it will be for Monero too
09:11:25 <sech1> #7760 needs serious and thorough review, the code quality is low from my point of view
09:11:30 <sech1> see my comments there
09:12:58 <sech1> I haven't looked at 7999 yet, but I'll probably find similar problems
11:08:02 <selsta> sech1: is the rng seed issue already in existing code? not jusr 7760?
11:14:41 <sech1> hmm, actually yes :D
11:15:09 <selsta> yes like i thought
11:15:44 <sech1> https://github.com/monero-project/monero/blob/master/contrib/epee/include/net/abstract_tcp_server2.inl#L633
11:15:57 <sech1> either way, the "perfect" daemon should've fixed this too
11:17:18 <sech1> I'll make a PR to fix this in the meantime
11:17:23 <sech1> because this is unacceptable
11:28:56 <sech1> selsta https://github.com/monero-project/monero/pull/8365
11:37:24 <selsta> ty
15:10:18 <woodser[m]> I just noticed the wallet caches get bigger with age. for example, an old, lightly used wallet >40 mbs. anyone know why?
15:29:10 <moneromooo> It stores block hashes. Though, IIRC, it prunes...
15:29:29 <moneromooo> Probably to double check reorgs. I forget exactly why.
15:31:57 <moneromooo> Hmm. It's used to build the shortchain when refreshing. Odd. I thought I added that, but this implies it was here from the beginning.
15:33:52 <moneromooo> Ah, right. I added it indeed. To trim the block hashes to avoid that constant size increase. So maybe it broke.
15:34:31 <moneromooo> Though it uses the last known hard checkpoint to know where to trim so maybe it'll slim back down once you update to a new version.
16:01:32 <UkoeHB> it should only be ~70mb for all block hashes in the chain
16:03:05 <UkoeHB> woodser[m] are you using 4yr old wallet software?
16:04:34 <woodser[m]> this is with the latest v0.17.3.2 gui. I'm loading the wallets in the gui to see if the size reduces
16:10:55 <woodser[m]> the size stays at >40 mbs after loading in the gui
16:14:10 <woodser[m]> > Though it uses the last known hard checkpoint to know where to trim so maybe it'll slim back down once you update to a new version.
16:14:10 <woodser[m]> the new version is the next checkpoint, or hard fork? the wallet software is the latest version
16:15:31 <moneromooo> IIRC it's the last hard checkpoint.
16:16:16 <moneromooo> It is. See trim_hashchain in wallet2.cpp.
19:55:58 <selsta> https://github.com/monero-project/monero/issues/8366
19:56:01 <selsta> issue about cache size
20:18:07 <hyc> sounds like normal operation, the cache has to keep track of the last N block hashes it has seen
20:18:26 <hyc> to know where to pick up from on the next sync with a daemon, and to detect reorgs
22:45:50 <philip_foss[m]> Hello there. I've been working as a C++ software engineer on embedded Linux for a couple years now and I'm interested in contributing to Monero. I've looked through some of the Issues on GitHub but it's a bit overwhelming getting into a new project like this. How do you all recommend that I get started?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/f0f16fdf7d172d6cae5c3765788ffb37a75f787a)
22:53:30 <UkoeHB> philip_foss[m]: hi philip, nice to have you. The general advice is usually 'find something you want to improve and then do it'. Is there a bug you hate? Fix it. Is there a feature you want? Implement it. Not sure? Find someone else's bug or feature that gets you energized.
23:03:08 <philip_foss[m]> Ok, I will see what I can find.
23:13:20 <kayabaNerve> I have a simple enough bug open in the RPC code, which should let you look through that code and learn how to check if a TX is a miner TX or not. https://github.com/monero-project/monero/issues/8311 Posting it to be self-serving, though it does seem like "good first issue" type of content
23:13:46 <kayabaNerve> But koe's statement on finding something that makes you excited is best. Don't work on a project you don't want to work on ;) Work on something you do :)