Hi Jean-Frederic, Regarding Brian's request below for your +1 on the Milagro crypto-c release: we will commit to fixing the following issues for any subsequent releases:
- Get Brian's key signed, update our KEYS file and get ourselves into the "strong set" (as per your and Nick Kew's request) And the following as requested by Justin McClean: - Remove author tags - Update copyright year in the LICENSE & NOTICES files - Add missing ASF headers to 4 x source files Regards, John > -----Original Message----- > From: Brian Spector <br...@qredo.com> > Sent: 30 January 2020 13:34 > To: jean-frederic clere <jfcl...@gmail.com>; > dev@milagro.incubator.apache.org; d...@milagro.apache.org > Subject: Re: Multi-Party Computation Repo > > > +1 but won't it be possible to contribute and develop directly in a sandbox > under Apache Milagro directly? > > Hi Jean-Frederic, I think we have our wires crossed because that's exactly > what we are proposing. We can't develop it from scratch in the ASF repo > unfortunately because we've done a lot code already. Next time we'll make > sure we do it straight from ASF from the get go. > > Thanks for the +1. > > Also I think John is chasing you for the Milagro crypto-C release. Could you > +1 on this? We're itching to get this release out. > > Thanks > Brian > > On 28/01/2020, 15:50, "jean-frederic clere" <jfcl...@gmail.com> wrote: > > On 19/01/2020 12:37, Brian Spector wrote: > > Hi Everyone, > > > > Multi-party computation (MPC) is becoming a very hot topic within the > distributed ledger and blockchain areas. > > > > Multi-party computation (MPC) is a branch of cryptography which deals > with scenarios of multiple distrustful parties performing a single > computation. There is a vast amount of recent research into applying MPC > techniques to digital signing, with immediate applications to securing crypto > assets. Simply put, MPC gets rid of private keys that are used to generate > cryptocurrency signatures. > > > > No private keys, no private key theft. > > > > MPC can be used to provide a threshold signature functionality in the > following way: > > > > 1. Several parties follow a specific protocol to generate multiple > independent secrets, which are never shared. > > 2. These secrets are used in another protocol to produce a public key, > and if the protocol continues, a single digital signature, which for all > intents > and purposes, looks and verifies as if it was created by a singular private > key, > when in fact, no private key exists. It’s replaced by the MPC protocol. > > > > The simplest, yet arguably most useful application of MPC signing is > 2-of- > 2 threshold scheme from the following paper at: > https://eprint.iacr.org/2019/114 > > > > This is where a single wallet address containing crypto assets is > controlled by two secrets, both of which are required to produce a > signature. > > > > We at Qredo have been working on an implementation of MPC in this 2 > out of 2 scenario which uses the Apache Milagro crypto-c library extensively. > > > > We would like to contribute this code we have singularly developed to > the Apache Milagro project. We believe it would have value to the > community using Apache Milagro and gives the project further relevance in > the blockchain and distributed ledger communities. > > > > Assuming there are no objections, Qredo will sign a new IP grant to the > Apache Foundation, create a new repo, and the submit its contribution into > the repo, while continuing to develop the protocol there. Hopefully this will > attract others to helping us flesh out the development as it is quite a > valuable bit of technology. > > +1 but won't it be possible to contribute and develop directly in a > sandbox under Apache Milagro directly? > > > > Please let me know your thoughts when you can. > > > > Best regards, > > Brian > > > > > -- > Cheers > > Jean-Frederic >
smime.p7s
Description: S/MIME cryptographic signature
