01:44:29 <afungible[m]> Hi guys, does anyone else face a similar issue as reported here.. I noticed multiple exceptions in log when monerod is started.
01:44:29 <afungible[m]> https://github.com/monero-project/monero/issues/8702
01:44:29 <afungible[m]> I saw it esp. when using locally compiled v0.18.1.2 on linux.
01:56:10 <selsta> afungible[m]: do you run into any actual issues apart from exceptions in the logs?
02:07:43 <afungible[m]> I did not test it much yet, but noticed send/recv tx went through fine. Not sure if daemon automatically restarts after catching these (weak_ptr) exceptions. I can try to enable more log-level tomorrow.
02:07:43 <afungible[m]> Anyhow, curious why this occurs continuously with compiled code, coz didn't notice this with official bin.
02:34:19 <selsta> afungible[m]: I'm not sure if the released binaries are released with libunwind / stack_trace enabled
02:34:33 <selsta> *are compiled with
02:35:09 <selsta> an uncaught exchange generally isn't an issue, it doesn't cause the daemon to restart
02:51:29 <afungible[m]> <selsta> "afungible: I'm not sure if the..." <- Would make sense if libunwind isn't used with released binary, then we won't see it. I didn't notice this in pre-HF compiled version btw. Though, it wld be nice to find why this occurs now. I'll see if I can do some debugging tomorrow.
15:29:09 <john_r365[m]> rbrunner: Question regarding multisig. With a multisig wallet, when you type seed in the CLI, you get a long string, as opposed to the regular mnemonic seed. Is it possible to use this string to re-create the multisig wallet in the future?
15:29:24 <john_r365[m]> The reason I ask is that I only see the command to import a multisig file. However, the ability to import one would, presumably, be dependent on having backed one up in the first place.
15:30:18 <john_r365[m]> So I'm curious if there's a way to backup a multisig wallet via the storage of a string, akin to mnemonic seeds for regular wallets
15:38:48 <moneromoooo> This will recreate the same wallet, yes. There's a lot more info needed in this case, so it was unwieldy when turned into words.
16:38:46 <john_r365[m]> Oh, fantastic, thank you. That makes sense.
18:00:47 <rbrunner> john_r365[m]: I guess it depends how far you look into the future. moneromooo's answer is certainly correct as long as good old `wallet2` is doing duty
18:01:43 <rbrunner> However, if we want Seraphis wallets to be able to import those quite special multisig "seeds", we will have to think of this and then program restore again from scratch
18:02:46 <rbrunner> "think of this" -> "not forget this"
18:08:15 <rbrunner> Or, maybe not necessarily. We will have "old" wallet import capability indefinitely. So if you can get hold of some "old" Monero software to restore using your multisig seed, you can later convert the resulting wallet up