📅 Original date posted:2018-07-24
📝 Original message:
Dear list, pardon me that I haven't investigated the Lightning implementations in depth yet, but one discussion has made me wonder how you approach the below described situation.
Rene was talking about virtual channels in his article [1]. His motivation was that a company running multiple nodes has to open channels between its own nodes in order to transact between them.
My vision of LN was to allow for much heterogeneity. Not only a company should be able to transact between its own nodes, but also with other entities it has a trust relationship with. Let me give you an example.
Say I trust you unconditionally. Alice asks me to send a satoshi to Bob. I don't have a channel with him, but you do. No channel between us. I receive HTLC from Alice, give you the image. You create HTLC with Bob, using that image. Bob checks - everything is OK. Bob executes.
The problem is source routing. Alice creates the whole payment chain, so she should be aware of our relationship. A solution could be advertising our trust as being a single node or introducing virtual channels as Rene suggests, constantly figuring out our respective balances. Is there a way to do so or do you see any other solution?
I understand the word 'trust' is repulsive, but think of the case with a single company running multiple nodes for whatever reason.
Thanks,
Dima
[1] https://www.rene-pickhardt.de/virtual-payment-channels-for-the-lightning-network-a-lightning-network-improvement-proposal-draft/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180724/b6bbe1ca/attachment.html>;
Dmytro Piatkivskyi [ARCHIVE] /
npub1sc…t408l
2023-06-09 12:51:14
in reply to nevent1q…xj6j
Author Public Key
npub1sc9gs5n8f65yfp7xyjcwd4kqqm7q6lm8vq9d6fszvuk8plyh59ms8t408lPublished at
2023-06-09 12:51:14Event JSON
{
"id": "2aa3c352b1871fec93f455a4ed14c3292a6d69dba13588efaf0ebc0c4e2c3e85",
"pubkey": "860a8852674ea84487c624b0e6d6c006fc0d7f67600add2602672c70fc97a177",
"created_at": 1686315074,
"kind": 1,
"tags": [
[
"e",
"03c6af191de569b1f7db318c7239632dcd9685fce6e5f214b28c1ffd8c9452a5",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2018-07-24\n📝 Original message:\nDear list, pardon me that I haven't investigated the Lightning implementations in depth yet, but one discussion has made me wonder how you approach the below described situation.\n\nRene was talking about virtual channels in his article [1]. His motivation was that a company running multiple nodes has to open channels between its own nodes in order to transact between them.\nMy vision of LN was to allow for much heterogeneity. Not only a company should be able to transact between its own nodes, but also with other entities it has a trust relationship with. Let me give you an example.\n\nSay I trust you unconditionally. Alice asks me to send a satoshi to Bob. I don't have a channel with him, but you do. No channel between us. I receive HTLC from Alice, give you the image. You create HTLC with Bob, using that image. Bob checks - everything is OK. Bob executes.\n\nThe problem is source routing. Alice creates the whole payment chain, so she should be aware of our relationship. A solution could be advertising our trust as being a single node or introducing virtual channels as Rene suggests, constantly figuring out our respective balances. Is there a way to do so or do you see any other solution?\n\nI understand the word 'trust' is repulsive, but think of the case with a single company running multiple nodes for whatever reason.\n\nThanks,\nDima\n\n[1] https://www.rene-pickhardt.de/virtual-payment-channels-for-the-lightning-network-a-lightning-network-improvement-proposal-draft/\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180724/b6bbe1ca/attachment.html\u003e",
"sig": "b896951c5f5b42cf127422079b4dec63c10f4c3b019eadca555b3b4ef81fa6682969cebdc0ffb1653b884252b268d1044b13a65456b7c017b1fa83f50b6a2eaa"
}