MuSig is only one part of Schnorr signatures that focuses on an alternative and safer way of "multi signature" features of Schnorr signatures which is used for aggregating signatures and for example offer the possibility of having a 50 of 50 multi sign transaction but only with the size of a single key tx since there will only be 1 signature and 1 public key and that will increase scaling of bitcoin drastically considering currently a lot of the transactions in blocks are multisignature with at least 3 signatures so using Schnorr can drop at least 2 sig + 2 public keys from each of them (considering they are 2 of 3) and that is 2*(32+32+7)+2*(33+1) = 210 bytes per tx! also considering this will probably be released with new SegWit version and SegWit has some overhead we can effectively be saving about 205 bytes per transaction per block and that is great.
Thanks for detailed explanation
but Schnorr is a lot more than just MuSig! https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki
the main thing i am excited about is batch verification. not to mention that creating signature is so much faster with ECSDSA compared to ECDSA because it doesn't have the modular multiplicative inverse.
the main thing i am excited about is batch verification. not to mention that creating signature is so much faster with ECSDSA compared to ECDSA because it doesn't have the modular multiplicative inverse.
True, but specifically MuSig is used together with Schnorr because naive/default Schnorr multiple key aggregation have security/privacy flaws.
