Jasper Hugunin [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-12 📝 Original message: Sorry for the wait. Here ...
📅 Original date posted:2015-08-12
📝 Original message:
Sorry for the wait.
Here is the repo: https://github.com/hashplex/Lightning
This version is meant to be a minimal node able to send payment across
multiple hops in the network. I intend to follow Rusty's micro-payment
channel design, but revocation and HTLCs have not yet been implemented.
Routing also uses an insecure payment forwarding algorithm (since HTLCs are
missing), and does not handle channels closing. See the GitHub issue
tracker for more details.
I have attempted to split the server, the UI, the channel protocol, and the
routing protocol into separate modules so that they can be developed
independently. My hope is that someone interested in routing can work on
the routing protocol before micro-payment channels are fully secured.
I look forward to working with you all,
- Jasper
On Tue, Aug 11, 2015 at 10:58 AM, Joseph Poon <joseph at lightning.network>
wrote:
> Hi Jasper,
>
> On Tue, Aug 11, 2015 at 10:48:57AM -0700, Jasper Hugunin wrote:
> > I'm Jasper Hugunin, a developer at HashPlex. I have implemented a full
> > prototype Lightning node in Python and will be releasing tomorrow.
> >
> > Features include:
> > Micropayment channels supporting unilateral close.
> > Basic routing support which allows payment to be routed multiple hops.
> > Integration tests.
> > MIT License.
>
> Very cool, I'm looking forward to it!!
>
> --
> Joseph Poon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20150812/53aab9cc/attachment.html>
📝 Original message:
Sorry for the wait.
Here is the repo: https://github.com/hashplex/Lightning
This version is meant to be a minimal node able to send payment across
multiple hops in the network. I intend to follow Rusty's micro-payment
channel design, but revocation and HTLCs have not yet been implemented.
Routing also uses an insecure payment forwarding algorithm (since HTLCs are
missing), and does not handle channels closing. See the GitHub issue
tracker for more details.
I have attempted to split the server, the UI, the channel protocol, and the
routing protocol into separate modules so that they can be developed
independently. My hope is that someone interested in routing can work on
the routing protocol before micro-payment channels are fully secured.
I look forward to working with you all,
- Jasper
On Tue, Aug 11, 2015 at 10:58 AM, Joseph Poon <joseph at lightning.network>
wrote:
> Hi Jasper,
>
> On Tue, Aug 11, 2015 at 10:48:57AM -0700, Jasper Hugunin wrote:
> > I'm Jasper Hugunin, a developer at HashPlex. I have implemented a full
> > prototype Lightning node in Python and will be releasing tomorrow.
> >
> > Features include:
> > Micropayment channels supporting unilateral close.
> > Basic routing support which allows payment to be routed multiple hops.
> > Integration tests.
> > MIT License.
>
> Very cool, I'm looking forward to it!!
>
> --
> Joseph Poon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20150812/53aab9cc/attachment.html>