Benjamin Mord [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-25 📝 Original message: Related, I am also ...
📅 Original date posted:2018-01-25
📝 Original message:
Related, I am also interested in the differences between the three major
lightning implementations: lnd, eclair, and c-lightning. I understand they
are implemented in Go, Scala, and C, respectively. Are there other
important differences for early adopters to consider, when selecting an
implementation?
(Christian, I believe of these three implementations, you happen to work on
c-lightning. Correct? Are there contributors from lnd and eclair on this
list as well?)
On Jan 25, 2018 3:48 PM, "v e" <veligeti999 at gmail.com> wrote:
Thanks Christian,
I do know that i should not expose lighteningd to multiple tenants however,
I am still trying to understand:
1) How merchant wallet is tied up to an invoice?
2) How consumer wallet can send satoshi to that invoice id?
If you have any code examples that would be great.
On Sat, Jan 20, 2018 at 5:41 AM, Christian Decker <
decker.christian at gmail.com> wrote:
> v e <veligeti999 at gmail.com> writes:
> > Will do as you suggested. one another question, when you say customers do
> > you mean end clients who are buying goods and services?
>
> Yes, they'll need to have clients that understand the Lightning protocol
> just like anyone else in the network.
>
> > Also i am building an server-client model where i am trying to host
> > multiple merchants who can accepts payments from end customers.
> > Does that mean i need to have (bitcoins node, c-lightning + charge) node
> > per merchant?
>
> Neither c-lightning nor Lightning Charge (or any other implementation
> for that matter) is multi-tenant, which is what you're
> describing. Someone with access to the RPC has full control over all
> channels and all funds in the daemon. Just like you wouldn't expose a
> raw bitcoind RPC interface to multiple users, you shouldn't directly
> expose lightningd to multiple tenants. You can build a layer inbetween
> that differentiates the tenants and controls access to individual
> resources though, but we don't currently support it directly.
>
> Notive also that we'd like to encourage every users, be it customer or
> shop, to run their own nodes, not rely on large managed infrastructure.
>
> Cheers,
> Christian
>
_______________________________________________
Lightning-dev mailing list
Lightning-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180125/71b22b08/attachment-0001.html>;
📝 Original message:
Related, I am also interested in the differences between the three major
lightning implementations: lnd, eclair, and c-lightning. I understand they
are implemented in Go, Scala, and C, respectively. Are there other
important differences for early adopters to consider, when selecting an
implementation?
(Christian, I believe of these three implementations, you happen to work on
c-lightning. Correct? Are there contributors from lnd and eclair on this
list as well?)
On Jan 25, 2018 3:48 PM, "v e" <veligeti999 at gmail.com> wrote:
Thanks Christian,
I do know that i should not expose lighteningd to multiple tenants however,
I am still trying to understand:
1) How merchant wallet is tied up to an invoice?
2) How consumer wallet can send satoshi to that invoice id?
If you have any code examples that would be great.
On Sat, Jan 20, 2018 at 5:41 AM, Christian Decker <
decker.christian at gmail.com> wrote:
> v e <veligeti999 at gmail.com> writes:
> > Will do as you suggested. one another question, when you say customers do
> > you mean end clients who are buying goods and services?
>
> Yes, they'll need to have clients that understand the Lightning protocol
> just like anyone else in the network.
>
> > Also i am building an server-client model where i am trying to host
> > multiple merchants who can accepts payments from end customers.
> > Does that mean i need to have (bitcoins node, c-lightning + charge) node
> > per merchant?
>
> Neither c-lightning nor Lightning Charge (or any other implementation
> for that matter) is multi-tenant, which is what you're
> describing. Someone with access to the RPC has full control over all
> channels and all funds in the daemon. Just like you wouldn't expose a
> raw bitcoind RPC interface to multiple users, you shouldn't directly
> expose lightningd to multiple tenants. You can build a layer inbetween
> that differentiates the tenants and controls access to individual
> resources though, but we don't currently support it directly.
>
> Notive also that we'd like to encourage every users, be it customer or
> shop, to run their own nodes, not rely on large managed infrastructure.
>
> Cheers,
> Christian
>
_______________________________________________
Lightning-dev mailing list
Lightning-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180125/71b22b08/attachment-0001.html>;