From datkins at securerf.com Fri Oct 9 17:55:13 2015 From: datkins at securerf.com (Derek Atkins) Date: Fri, 9 Oct 2015 17:55:13 +0000 Subject: [Lightning-dev] Negotiating & Committing Signatures In-Reply-To: <87mvx8p3pc.fsf@rustcorp.com.au> References: <87mvx8p3pc.fsf@rustcorp.com.au> Message-ID: <1444413312.2789.372.camel@SecureRF.com> Hi Rusty, I was considering creating a prototype of using AEDSA here, just to see how well it might fit in and see if I can gauge the performance. Do you think that would be a reasonable project? I was hoping to possibly get this done and make measurements in time to present at the next Scaling Bitcoin workshop. If you agree this is a reasonable experiment, is it something I would only need to change within lightning or would I also need to update bitcoind/alphad? Thanks, -derek On Mon, 2015-08-31 at 12:24 +0930, Rusty Russell wrote: > Jeremy Rubin writes: > > Negotiating & Committing Signatures > > ============================ > > > > In this proposal, I suggest the addition of new types of signature schemes > > to Bitcoin, and running lightning over multi signature of the > > variants to utilize the advantages of multiple signature schemes without > > the drawbacks. > > Hi Jeremy, > > Such a hybrid would certainly be possible (though getting novel > crypto into bitcoin is a large task). > > You refer to an "order or magnitude" increase in pubkey and signature > sizes, but signatures of even 64k wouldn't make much logistical > difference to the LN. Giant pubkeys might be a logistical issue, though > using the bitcoin trick of referring to them via their RIPEMD160 should > work there, too. > > Cheers, > Rusty. -- Derek Atkins Chief Technology Officer SecureRF Corporation Office: 203.227.3151 x1343 Direct: 617.623.3745 Mobile: 617.290.5355 Email: DAtkins at SecureRF.com This email message may contain confidential, proprietary and / or legally privileged information and intended only for the use of the intended recipient(s) and others specifically authorized. Any disclosure, dissemination, copying, distribution or use of the information contained in this email message, including any attachments, to or by anyone other than the intended recipient is strictly prohibited. If you received this in error, please immediately advise the sender by reply email or at the telephone number above, and then delete, shred, or otherwise dispose of this message.