Christian Decker [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-20 📝 Original message: v e <veligeti999 at ...

📅 Original date posted:2018-01-20
📝 Original message:
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