📅 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
Christian Decker [ARCHIVE] /
npub1wt…gtuyn
2023-06-09 12:48:38
in reply to nevent1q…yeu3
Author Public Key
npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuynPublished at
2023-06-09 12:48:38Event JSON
{
"id": "0302aca6c00bce534c71bf1760d2b624bc8db0d5eb5098540e21cbdc5e6a20f4",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686314918,
"kind": 1,
"tags": [
[
"e",
"c602e30480cd254be8c2e99d312a8988a46d9694329c6f63434d02447b7e3258",
"",
"root"
],
[
"e",
"089eb313b514aa00670bd23e9ac4fded388cea4523baf1893d0c7ab877f0d899",
"",
"reply"
],
[
"p",
"a9925e4b87828bb802b55a6c28db0c3e72005f43023f00ba89ed76d20f3c607b"
]
],
"content": "📅 Original date posted:2018-01-20\n📝 Original message:\nv e \u003cveligeti999 at gmail.com\u003e writes:\n\u003e Will do as you suggested. one another question, when you say customers do\n\u003e you mean end clients who are buying goods and services?\n\nYes, they'll need to have clients that understand the Lightning protocol\njust like anyone else in the network.\n\n\u003e Also i am building an server-client model where i am trying to host\n\u003e multiple merchants who can accepts payments from end customers.\n\u003e Does that mean i need to have (bitcoins node, c-lightning + charge) node\n\u003e per merchant?\n\nNeither c-lightning nor Lightning Charge (or any other implementation\nfor that matter) is multi-tenant, which is what you're\ndescribing. Someone with access to the RPC has full control over all\nchannels and all funds in the daemon. Just like you wouldn't expose a\nraw bitcoind RPC interface to multiple users, you shouldn't directly\nexpose lightningd to multiple tenants. You can build a layer inbetween\nthat differentiates the tenants and controls access to individual\nresources though, but we don't currently support it directly.\n\nNotive also that we'd like to encourage every users, be it customer or\nshop, to run their own nodes, not rely on large managed infrastructure.\n\nCheers,\nChristian",
"sig": "dff99fd717b372deb52338fab4ed7928472ba247e13775e55a6f53f196710af5b4c53697d0efabde588fd7ce147ce79f41bba7d4f5ea97d4e1d1fd4ceef94ed7"
}