Blog

Schnorr aggregate signatures can be nestled in other Schnorr aggregate signatures?

Schnorr signatures are a type of digital signature used in different blockchain and cryptocurrency applications. They are designed to provide a safe and effective way to verify the authenticity and integrity of the messages without having their content. One of the key characteristics of Schnorr signatures is that they can combine the signatures of several parts in a single shared signature, known as aggregate signature. In this article, we will explore if it is possible to nest aggregated signatures in other aggregate signatures using Schnorr protocols.

understanding Schnorr signatures

Schnorr signatures are based on the concept of “blind signature”, which allows the parties to sign messages without revealing the contents of others. They consist of three components: a private key (P), a public value (P) and a Hash (H) function. The public value P is derived from the private key p using the Hash Schnorr H (P) = R + P^K function, where K is an entire parameter.

aggregate signatures

Schnorr aggregate signatures are used to combine the signatures of multiple parties in a single shared signature. An aggregate signature consists of a list of signatures (S_I), and the Hash Schnorr function for each signature is combined using a Hash Haggregate (S_I) function.

** Can aggregate signatures be nestled in other aggregate signatures?

In theory, it is possible to nestate the aggregated signatures in other aggregated signatures using Schnorr protocols. However, there are some potential limitations and problems to be considered.

An approach to aggregated nesting signatures is the use of a combination of hash Schnorr function and a new hash haggngag2 (s_i) function. The idea is to create a new public value P2 by combining two private keys P1 and P2 using the Hash Schnorr function: P2 = Haggregate2 (P1, P2). Then we can get an aggregate S2 signature of this public value using the same Hash Schnorr function.

However, there are potential issues to consider:

* Security : The aggregate nesting signatures can introduce new security risks, such as increased complexity and vulnerability to attacks. The nestled aggregate signature may be more difficult to verify or to extract from.

* Performance

: Creating and checking the nestled aggregate signatures can be calculated, especially for large inputs. This can make them less practical for applications in the real world.

Example of case use

To illustrate this concept, consider a case of use in which we have two parties (Alice and Bob) who want to sign a message together using Schnorr signatures. We will create an aggregate signature nestled inside another aggregate signature.

Suppose Alice has the private key p1 = e1^p2^K1, where E1 is the public value for signing. She wants to combine her signature with Bob’s signature to form an aggregate signature S_nested (S1, S2), where S1 and S2 are individual Schnorr signatures.

We create a new public value P2 combining Alice’s private key p1 = E1^P2^K1 with the private key of Bob P2: P2 = haggregate2 (P1, P2) = E1^haggregate (S1, S2).

Then we derive an aggregate signature s_nested using the Hash Schnorr function: s_nested = haggregate (S1, S2)

The public value for this nestled aggregate signature is P3 = E1^P2.

Conclusion

In conclusion, it is possible to nestate the aggregated signatures in other aggregated signatures using Schnorr protocols. However, there are potential security and performance problems that need to be considered when creating, such as nestled signatures. It is essential to carefully evaluate the compromises and limitations of this approach before applying it in a scenario in the real world.

Recommendations

• Carefully consider the security risks and the potential vulnerabilities introduced by nesting aggregated signatures.

HEDERA ISOLATED MARGIN ORDER