00:51:43 <TheCharlatan> has there ever been a proposal made to combat fee sniping in a similar way as with bitcoin's nlocktime?
15:40:02 <moneromooo> binaryFate: did you have --limit* options on your node which hanged with negative expiry ?
15:40:17 <moneromooo> (or a later set_limit command or RPC)
15:41:38 <moneromooo> Oh nvm, it's actually on by default.
15:44:37 <binaryFate> nope did not
16:22:38 <i_a> hello, I am seeking a bit of help with my monero related problem.
16:22:42 <i_a> https://monero.stackexchange.com/questions/11834/help-needed-with-calculating-a-key-image
16:24:10 <i_a> I still cannot get through, is anybode here who would be willing to discuss it?
16:28:17 <moneromooo> Have you tried running the C++ code with that data and logging all intermediate steps to see where it starts to diverge ?
16:29:19 <i_a> moneromooo: I was trying to do this obvious step last two hours, but working with c++ codebase is hard for me. I am trying to cheat here :P
16:31:09 <i_a> I have never worked with a such a big C++ codebase as monero is now, so every time I try something, there is an error when compiling..
16:31:22 <endogenic> i_a I'm able to lend a hand somewhat. here is how we hook into key img generation
16:31:23 <endogenic> https://github.com/mymonero/mymonero-core-cpp/blob/68ec454ee95ca9d05c1250967e3ca43ebb01f69c/src/monero_key_image_utils.cpp#L40
16:31:43 <endogenic> we were able to embed a stripped down version of monero core
16:32:10 <endogenic> mooo's advice of stepping through is good - you can place logs in the function to calc the key img
16:33:44 <moneromooo> The C++ code uses ge_fromfe_frombytes_vartime, mininero multiplies by G. Are these two things the same ?
16:33:56 <i_a> endogenic: hmm thank you, looking into it and it looks much more readable for me,)
16:34:14 <endogenic> you'll still have to get into the key img calc function ofc as we were able to converge with that
16:34:35 <endogenic> in any case, pleased to be able to help
16:40:03 <i_a> endogenic: thank you, I will try to compile it and get a bit familiar, hopefully it helps, otherwise I will be back here soon:)
16:40:37 <endogenic> ok cool - you can simply run the tests via the script in bin and it'll handle compilation
16:40:52 <endogenic> dont forget to setup the repo with update_submodules
17:00:02 <i_a> endogenic: Compiled, do you have any recommendation how to use it for my purpose?
17:22:55 <i_a> endogenic: I just created a main.cpp, compiled and I will try to add functions and test them with my strings. Thank you, looks like I am on the right direction!
17:24:09 <endogenic> coolio - just a heads up mooo sent you a msg before, want to make sure you saw it
17:27:58 <i_a> endogenic: yes moneromooo is faster than legends say :) but for me main codebase is really overkill. Maybe next year. Anyway, thank you both!
17:28:27 <endogenic> for confirmation's sake I mean this one "The C++ code uses ge_fromfe_frombytes_vartime, mininero multiplies by G. Are these two things the same?"
22:59:14 <kovri-slack> <woodser> I am seeing that sweep_unlocked with a specific subaddress is leaving behind dust even if the initial balance was enough to cover the fee.  Is this expected?
23:00:56 <moneromooo> Probably not based on your short description.
23:03:57 <kovri-slack> <woodser> actually it does not need to be with a specific subaddress.  same behavior with an account and all of its subaddresses; dust is left behind in the account
23:20:32 <kovri-slack> <woodser> also sweep_all returns “No unlocked balance in the specified subaddress(es)” when there is unlocked dust across the subaddresses.  maybe that is expected behavior with a slightly inaccurate message