Panel of the day on Main Stage at nostr:npub1dwah6u025f2yy9dgwlsndntlfy85vf0t2eze5rdg2mxg99k4mucqxz7c52 Lightning++ Edition: nostr:npub1e0z776cpe0gllgktjk54fuzv8pdfxmq6smsmh8xd7t8s7n474n9smk0txy ofnostr:npub1dwah6u025f2yy9dgwlsndntlfy85vf0t2eze5rdg2mxg99k4mucqxz7c52 moderates the panel "Implementing Lightning" with

nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp of Spiral, Christian Decker of nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n and Nickolas Goline of

nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f

Reply to this note

Please Login to reply.

Discussion

Fabrice Drouin of Acinq joined the panel!

Matt started working on Lightning because that's where he thought he could have more impact on people lives.

Nickolas was just a user that wanted to understand how Lightning worked. The best way to learn about it was to build his own implementation.

Acinq has two LN implementations. Eclair for big nodes is great, but they also wanted something for native wallet development without all the routing stuff, that's why they built phoenixd.

Core-lightning was born as a test platform for specification proposals, opening up the node for experimentation and custom tailoring.

LDK is super-flexible and can be used on any platform, like in the web.

It became the default for servers and enterprise-level nodes due to the high number of bindings to other languages.

NLightning will be both a library and a full-node.

It will be possible to build on top of the library, but the goal is also to have a node implementation.

Having new eyes on the specifications, like NLightning's, is very good to discover possible issues. This can help making the specs and the network more robust.

It has been a while since new implementation came in.

Most exciting updates for the future:

- Fabrice: 0-fee transactions

- Christian and Nickolas agreed: multy-parties channels

- Matt: gossip v2