00:22:36 <ksk> I think when I initially encountered multisigs I came in here and asked how to use them via RPC ;)
00:30:19 <moneromooo> To be clear, multisig RPC do exist.
06:44:52 <M5M400> here's a weird one... tried to connect to my public node with new monerujo. connection error. ssh'd into the node box to check. simply reattached the screen and it went from "stalled since yesterday" to immediately syncing?
06:44:59 <M5M400> https://i.imgur.com/P3WWmOM.jpg
06:48:06 <rbrunner> What do people think of mms rpc ? <- For interested parties: Ongoing discussion and some more background info here: https://github.com/monero-project/monero/pull/6180
06:48:35 <rbrunner> Python program that shows how these new RPC calls are meant to get used here: https://github.com/rbrunner7/rbrunner7.github.io/blob/master/mms.py
06:49:44 <rbrunner> The later is "work in progress" and will change over the next few days, but is already functional.
07:07:55 <rbrunner> The most interesting feature of that "mms.py": If you let it wait for messages and auto-process them, it will "sync" wallets fully automatically after an incoming payment to get them ready to spend that
07:08:52 <rbrunner> (In this point it goes beyond the MMS integration of the CLI wallet which can't do that fully automatically.)
09:41:10 <rbrunner> I have written an explanation of my MMS RPC PR that I should have written right at the start already, my bad: "What the heck is this thing?"
09:41:33 <rbrunner> I have added this to the topmost post of the PR: https://github.com/monero-project/monero/pull/6180#issue-345167243
12:46:07 <gingeropolous> M5M400, run the daemon as a proper service
12:49:05 <M5M400> gingeropolous: you think that would have prevented stuff?
12:49:30 <M5M400> it's been running in a screen since v.0.10 in a screen. that never happened
12:54:39 <asymptotically> you need to get systemd to run supervisord to run pm2 to run s6 to run monerod
13:11:14 <fluffypony> https://crates.io/crates/randomx-rs
13:11:23 <fluffypony> Rust RandomX crate in case anyone needs it
16:24:53 <peach34> what is the proper way to convert from a crypto::public_key to a ge_p3 in Monero
16:26:36 <peach34> I see the function
16:26:37 <peach34> void hash_to_ec(const public_key &key, ge_p3 &res) {    hash h;    ge_p2 point;    ge_p1p1 point2;    cn_fast_hash(std::addressof(key), sizeof(public_key), h);    ge_fromfe_frombytes_vartime(&point, reinterpret_cast<const unsigned char *>(&h));    ge_mul8(&point2, &point);    ge_p1p1_to_p3(&res, &point2);  }
16:26:48 <moneromooo> ge_fromfe_frombytes_vartime <- that one
16:26:51 <peach34> Not sure if this is the one I want though?
16:27:06 <moneromooo> er, wait. fe doens't seem right...
16:28:50 <peach34> thanks mm
16:29:00 <moneromooo> ge_frombytes_vartime
16:30:08 <peach34> Are you sure? We use it for (ge_frombytes_vartime(&image_unp, &image) where image is a const crypto::key_image &image
16:30:32 <moneromooo> It's what I use for multiexp in bulletproofs, so it better be.
16:30:45 <moneromooo> sarang or luigi will know for sure.
16:32:22 <peach34> can you link me to a line you used it MM?
16:32:44 <moneromooo> CHECK_AND_ASSERT_THROW_MES(ge_frombytes_vartime(&point, p.bytes) == 0, "ge_frombytes_vartime failed");
16:33:22 <peach34> you're using an rct key
16:33:32 <peach34> I'm talking about a straight up crypto::public_key
16:34:01 <moneromooo> Add (const crypto::public_key&)
16:35:13 <peach34> What do you mean by add?
16:36:06 <moneromooo> CHECK_AND_ASSERT_THROW_MES(ge_frombytes_vartime(&point, (const crypto::public_key&)p) == 0, "ge_frombytes_vartime failed");
16:39:33 <moneromooo> Wait. If your p is already a public_key, you don't need that.
16:39:42 <moneromooo> The cast I mean.
16:39:43 <peach34> I thought so
16:39:44 <peach34> yeah
16:39:47 <peach34> cheers dude
16:39:50 <luigi1111w> they are the same
16:39:55 <luigi1111w> cast aside
16:40:03 <peach34> yes :P
16:40:34 <moneromooo> luigi1111w: what's ge_fromfe_frombytes_vartime for ? Scalars are hte same as field elements, right ? And scalars are never compressed AFAIK ?
16:41:01 <luigi1111w> ge_fromfe is the key image base computation
16:41:02 <peach34> it's the same thing in a different com[pressed form
16:41:16 <peach34> I'm using this
16:41:17 <peach34> https://coinpaprika.com/storage/cdn/whitepapers/39.pdf
16:41:24 <moneromooo> Ah, so just a weird name then. OK.
16:41:25 <luigi1111w> it's to constrain a random byte sequence to a curve point
16:41:32 <luigi1111w> where ge_frombytes will fail if invalid
16:42:24 <moneromooo> Ah, Hp. Of course. I'm so stupid -_-
16:42:55 <peach34> luigi1111w what is the difference between a ge_p3 and a ge_p2
17:16:42 <luigi1111w> different forms for different functions knaccc or vtnerd can tell you more
17:17:25 <knaccc> peach34 different ec operations work best in particular coordinate spaces
17:17:46 <knaccc> peach34 p2/p3/etc are coordinate spaces
17:18:22 <knaccc> in practice you just decide what operations you want to do, look at what coordinate spaces they input and output, and convert between coordinate spaces when necessary
17:19:50 <knaccc> so e.g. if you want to subtract two ec points, the only implementation available is one that takes p3 as an argument
17:20:17 <knaccc> and the other arg has to be in cached form
17:20:40 <knaccc> you don't need to understand the performance reasons, you just have to observe what the method wants and give it what it wants
17:38:57 <peach34> moneromooo so if i wanted to use ge_frombytes_vartime to get from a crypto::key_image to a ge_p3, i'd just static cast to crypto::public_key first?
17:48:50 <peach34> please pm me as i dont have a fixed nick on this irc, and i have to shut the comptuer off
18:10:30 <moneromooo> To a const crypto::public_key&, yes. It's the same data in memory.
18:25:19 <sarang> Ah seems all questions were answered already
20:46:22 <M5M400> sniderd you're telling people that integrated addresses will be discontinued too with v0.15?
20:49:42 <M5M400> sigh. wrong channel again
20:49:59 <moneromooo> And the claim is false fwiw.
20:50:24 <M5M400> that's what I wanted to tell him :)