01:16:20 @UkoeHB the methods wallet2::get_multisig_seed() and wallet2::restore() (the multisig overload), haven't been touched in 5 years and do not store/load the field m_multisig_derivations. I might be wrong, but it's probably necessary to use this field to restore multisig wallets from scratch (and skip the initial key exchange / preparation stages), yeah? 01:16:45 * @UkoeHB the methods wallet2::get_multisig_seed() and wallet2::generate() (the multisig overload), haven't been touched in 5 years and do not store/load the field m_multisig_derivations. I might be wrong, but it's probably necessary to use this field to restore multisig wallets from scratch (and skip the initial key exchange / preparation stages), yeah? 01:17:22 * @UkoeHB the methods wallet2::get_multisig_seed() and wallet2::generate() (the multisig overload), haven't been touched in 5 years and do not store/load the field m_multisig_derivations. I might be wrong, but it's probably necessary to use this field to restore multisig wallets from scratch, skipping the initial multisig setup, yeah? 01:39:33 Nvm it seems the derivations aren't needed after finalization 03:18:52 jeffro256[m]: right 03:20:02 How many multisig private keys should there be given M/N? 03:25:07 (after setup) 06:41:44 Koe could you pretty please double check that https://github.com/monero-project/monero/pull/8914 is correct? 12:16:50 jeffro256[m]: one for every group of size N - M + 1 12:40:27 so I guess N choose (N - M + 1) would do it (there is n choose k in seraphis_lib src/seraphis_crypto/math_utils.h)