Derek Atkins [ARCHIVE] on Nostr: đ Original date posted:2015-10-09 đ Original message: Hi Rusty, I was ...
đ
Original date posted:2015-10-09
đ Original message:
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 <jr at mit.edu> 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.
đ Original message:
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 <jr at mit.edu> 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.