New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aggregating multisig partial signatures #9318
Comments
Is it even possible to aggregate partial signatures from one wallet? or should it have this sequential order? |
ANYONE? |
@UkoeHB can you answer this? |
The current implementation does round-robin signing. The 16-signer limit exists because wallet setup becomes extremely slow with larger group sizes. I have aggregation-style signing implemented for CLSAG in the Seraphis library, but actually changing the wallet workflow to use it would require quite a lot of implementation and review work. I wouldn't bet on seeing it in the monero repo for at least a year. |
@UkoeHB Do you have an implementation of this aggregation-style for CLSAG? |
Yes, here is a test for it. |
Thank you, @UkoeHB I appreciate it. Is it true that changing the key aggregation style from MuSig2 to FROST would require changings in the wallet functions that handle multisig operations? or are they both endup with each participant having And about the Seraphis library, does it provide the siggnature aggregation command through RPC API? |
You'd need an entirely new multisig account management/setup API.
No, only the backend functionality is implemented. |
I ran a M/N multi signature account locally. From what I noticed, there is no aggregation command in cli-wallet or RPC to aggregate partial signatures and the process of finalizing transactions has a sequential order. Alice who generates the transaction needs to send it to Bob, Bob needs to sign and pass to Carol and so on, until the transaction is signed by the threshold size and ready to be submitted. Are there any commands or RPC API for Alice to be able to gather all the signatures from collaborators and aggregate them to make and submit the final transaction? In other words, I want the process to be done not in sequential order but in parallel.
Also, I noticed that there is a maximum limit(16) on signer numbers participating in the multisig account. You have mentioned that in order to be able to support more signers efficiently, the key exchange phase should be done FROST style. Is there an implementation of this? how can I remove the limit of signers?
The text was updated successfully, but these errors were encountered: