@n1ckler @RCasatta It turns out this construction is quite interesting as it supports a “mirror” curve (which we call “SecQ”) that in turn is a mirror of SecP, potentially offering some recursive Bulletproofs not easily possible with other curves: <a href="https://github.com/BlockchainCommons/secp256k1/issues/1#issuecomment-410482607">https://github.com/BlockchainCommons/secp256k1/issues/1#issuecomment-410482607</a>

Christopher Allen

@ChristopherA

@n1ckler @RCasatta It turns out this construction is quite interesting as it supports a “mirror” curve (which we call “SecQ”) that in turn is a mirror of SecP, potentially offering some recursive Bulletproofs not easily possible with other curves: https://github.com/BlockchainCommons/secp256k1/issues/1#issuecomment-410482607

9/13/2018, 5:41:17 PM

Favs: 0

Retweets: 0

link

Christopher Allen

@ChristopherA

@n1ckler @RCasatta I was not CTO of Certicom yet when the secp256k1 parameters were selected. I’ll ask Paul Lambert who I think was at Certicom at the time if he knows.

9/13/2018, 5:50:01 PM

Favs: 0

Retweets: 0

link