[bch-dev] Schnorr algorithm selection

[Tomas]

Hi all,

Thanks Shammah, for opening the discussion on the mailing list. Much
appreciated.
I have a question regarding the choice of algorithm selection mechanism
for Schnorr. In the spec it is stated that the first byte of the
signature serialization is 0x73 to mark the signature as using the
Schnorr algorithm.
As better algorithms may arise in the future I wonder whether this
mechanism is suitable for future extensions; specifically compared to
adding an (optional) algorithm-number argument to the checksig family
of OPcodes.
A flaw of putting the algorithm in the signature seems to be that the
security of signing becomes as weak as the weakest algorithm. As such it
seems more natural to use an argument; the choice of algorithm is
clearly part of the OPeration.
Maybe I am late to the game, but I am wondering whether this has been
taken into consideration?
Tomas van der Wansem


On Sat, Dec 1, 2018, at 17:10, Shammah Chancellor wrote:
> Hello Gentlepeople,
> 
> In the spirit of enabling others to work, I'd like to get the draft
> specification for May MERGED into the Bitcoincash.org repository.
> Please review the existing spec here:
> https://github.com/bitcoincashorg/bitcoincash.org/pull/179> 
> And either explicitly reject, or approve it.  The hope is that it will
> get merged, and then further people can do pull requests on top of
> that to improve it before Jan 3rd.> 
> If you're unable to start a review in Github for some reason, please
> let me know.  However, I believe anyone is able to do it at this time.> 
> Kind Regards,
> Shammah Chancellor
> Bitcoin-ABC
> _________________________________________________
> bch-dev mailing list
> bch-dev at lists.bitcoinunlimited.info
> https://lists.bitcoinunlimited.info/cgi-bin/mailman/listinfo/bch-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bitcoinunlimited.info/pipermail/bch-dev/attachments/20181206/471650fd/attachment.html>