Feature/version 3.0

[borislav-itskov]

Change log:

• remove multiSigSign
• rename multiSigSignHash to multiSigSign
• do the same with verify and verifyHash

Problem: we have a lot of methods that do kind of the same but with small differences. Combine those methods into one.

[LorhanSohaky]

Why do you want to remove musig?

In my use case it is very important

[borislav-itskov]

@LorhanSohaky Currently, we have two multisig methods:

multiSigSign()
multiSigSignHash()

And on top of that, multiSigSign has an additional parameter hashFn: Function|null = null. We have 3 ways to make a signature and in my opinion, this is very confusing.
I propose we omit the multiSigSign function and rename the multiSigSignHash function to multiSigSign in version 3.0. This way, we will have 1 function for making a multisigner signature and it would be more straightforward.
What do you think? I'm open to suggestions

[LorhanSohaky]

@borislav-itskov Okay, I had only read the changelog and the last time I saw the project did not exists the hashFn parameter.

My only suggestion is to have a hash function just for convenience

export const hash = (msg: string) => ethers.utils.solidityKeccak256(['string'], [msg])