10:32:00 <sech1> Some questions for people here to answer, this is way over my head https://www.reddit.com/r/Monero/comments/1r65w5f/how_fcmp_simplifies_multisig_coordination/
15:06:37 <br-m> <jeffro256> Can you plz paste the questions here? Reddit is network blocked for me 
15:30:42 <DataHoarder> I maintain mirrors of repositories I use on my git instance (forgejo makes it easy to make mirrors either way) but I kept some private
15:30:44 <DataHoarder> If the purpose is to do code submission workflows maybe should do good old git email
15:42:02 <sech1> jeffro256 https://paste.debian.net/hidden/d9ac7e21
15:44:30 <br-m> <intr:unredacted.org> @jeffro256: redlib.catsarch.com btw
16:53:43 <br-m> <jeffro256> sech1: Yes the y scalar (over the T generator) is the only one that is "thresholded". Each participant can know the x scalar (over the G generator) in its entirety. This allows participants to calculate key images, and thus balance, without needing to disseminate partial key images amongst each other each time an enote is received .
16:53:43 <br-m> <jeffro256> The membership proof can be completed by any one participant once the tx is signed.
16:53:43 <br-m> <jeffro256> Wallet2 may be refactored eventually to do this, but it requires new keys . I.e. for wallets already generated , multisig after FCMP++ mostly remains the same with all the partial key images and such. The current plan is to ship such that the existing wallets work, but not support the new multisig out of the gate .