Posted by waxwing/ AdamISZ
Apr 26, 2025/15:30 UTC
The discussion initiated by AdamISZ/waxwing revolves around the intricate details of a proposed cryptographic algorithm, which, although not exclusively designed for Bitcoin, is analyzed through its application within the Bitcoin framework. The focal point of this dialogue is the CISA (Compact Identities Schnorr Aggregation) algorithm, aimed at enhancing transaction efficiency without imposing linear costs on the blockchain's verification processes or significantly increasing the signature size relative to the number of signers.
One pivotal aspect of the CISA algorithm is its structure, specifically designed to aggregate signatures in a way that circumvents the linear cost dilemma associated with blockchain transactions involving multiple signers. This is achieved by publishing a combined (R, s) structure rather than individual components for each signer. The approach facilitates a more efficient verification process by aggregating the R-values and s-values, while keeping public keys separate, leveraging their implicit availability from existing blockchain records, as seen with taproot technology. This method avoids the complexities associated with key aggregation, opting instead for a sum of individual challenge hashes tied to each public key, a strategy aimed at maintaining performance without compromising security.
Concerns regarding potential performance issues due to verifier requirements to iterate through an extensive list of public keys are addressed by comparing the proposed method to batch verifying individual signatures, revealing a twofold increase in speed. Furthermore, to mitigate risks such as trivial key subtraction attacks or Wagner/ROS grinding, the nonce is divided into two components with an additional challenge hash, drawing parallels to MuSig2’s methodology but with explicit hashing of comprehensive context including individual public keys and messages, alongside the nonce's subcomponents.
This conversation also delves into client-side validation concepts, suggesting a shift towards complex calculations during the coordination phase before any on-chain actions, thus ensuring the use of a single, secure "R" value. Additionally, the discourse touches on the security of single-signer scenarios, questioning the inclusion of zero-knowledge proofs to affirm both the soundness and privacy of the final signature.
Further explorations include contemplating optimizations for single-party cases, acknowledging the need to consider potential party corruption, and discussing multi-component nonce techniques, specifically the feasibility of incorporating proofs of knowledge within the coordination step to simplify security proofs without imposing undue burdens on constrained devices.
Lastly, the discussion acknowledges unaddressed complexities related to ensuring keys and messages are uniquely represented in the context of multisig-to-aggregated-sig transformations, hinting at deeper challenges yet to be explored.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback