06:24:01 rbrunner7: i have unclear if i'm expected to moderate the meeting on Saturday. I'm not sure because i should have moderated the meeting this meeting is replacing 🙂 I'm available in any case, so please let me know 07:40:51 ErCiccione: I would be glad if you could moderate the coming dev meeting this Saturday, yes 07:50:17 Ok, no problem 🙂 13:57:05 is it possible for export_multisig_info to work with unconfirmed funds, so a multisig tx can be created when the funds unlock without re-exchanging the multisig info? 14:10:31 No. 14:11:36 However, that info could plausibly piggy back on the multisig tx itself, similarly to the output and key image info piggybacking onto cold signing data. 14:22:48 However, that info could plausibly piggy back on the multisig tx itself, similarly to the output and key image info piggybacking onto cold signing data. (got dc'd, not sure if that went through) 14:23:00 yes, thanks 14:30:50 that would allow the multisig tx to be created without exchanging info after receiving funds, and then the co-signer could update their wallet from the piggybacked info, sign, and broadcast? 14:31:24 peers are likely to go offline in our case, so as is, the tx can't be signed and broadcast until completing a round trip, potentially waiting for each peer to come back online. it would be great to remove a trip, by allowing the tx to be created before exchanging multisig info 14:33:14 Yes. You'd stlil exchange ms info technically, just not as a separate step. I can't think of a reason it would not work. Hopefully there are none. 14:45:17 woodser[m]: are you trying to speed up the part where you learn key images? 14:46:50 I just want to avoid needing a round trip in order to create, sign, and broadcast a tx, as this can add a lot of time if participants offline and return online later 14:48:48 hoping to create the tx and share with participants to sign and broadcast without needing their updated multisig info 15:17:11 I created an issue for it: https://github.com/monero-project/monero/issues/8230 15:23:16 Looks like I messed up rebase on 8149, and some submodule junk got added in https://github.com/monero-project/monero/pull/8149/files . Anyone know how I can fix it? 15:43:20 git reset --soft HEAD~1 15:43:24 git checkout -- external/randomx 15:43:31 git commit -S -m "cleanup" 15:43:45 not 100% sure though 15:47:17 selsta: is that second one missing a command? 15:48:22 wait it's wrong I think 15:48:25 does `git restore --staged external/randomx` work? 15:49:01 or just enter `git reset --soft HEAD~1` and then check with `git status` how to remove the submodule changes 15:51:14 thanks fixed it :) 16:07:06 when using ` --bootstrap-daemon-address auto` is there a way to see which node was chosen? 16:14:56 status 16:16:18 ah i see, thanks selsta 18:15:20 .merges 18:15:20 -xmr-pr- 8222 18:26:44 .merge+ 7936 7937 8053 8166 8177 8179 8180 8195 8196 8197 8205 8207 8211 8212 8213 8215 18:26:44 Added 18:27:42 moneromooo: did you see https://github.com/monero-project/monero/pull/8175#issuecomment-1081829296 ? 18:29:03 jeffro256[m]: could you squash the 8223 and 8228 to a single commit? 19:23:23 I did not, thanks.