{"action":"created","issue":{"url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/192","repository_url":"https://api.github.com/repos/btcpayserver/btcpayserver","labels_url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/192/labels{/name}","comments_url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/192/comments","events_url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/192/events","html_url":"https://github.com/btcpayserver/btcpayserver/issues/192","id":326758100,"number":192,"title":"Open Lightning payment channel as option [Feature request]","user":{"login":"charlespax","id":281642,"avatar_url":"https://avatars0.githubusercontent.com/u/281642?v=4","gravatar_id":"","url":"https://api.github.com/users/charlespax","html_url":"https://github.com/charlespax","followers_url":"https://api.github.com/users/charlespax/followers","following_url":"https://api.github.com/users/charlespax/following{/other_user}","gists_url":"https://api.github.com/users/charlespax/gists{/gist_id}","starred_url":"https://api.github.com/users/charlespax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/charlespax/subscriptions","organizations_url":"https://api.github.com/users/charlespax/orgs","repos_url":"https://api.github.com/users/charlespax/repos","events_url":"https://api.github.com/users/charlespax/events{/privacy}","received_events_url":"https://api.github.com/users/charlespax/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-05-26T18:25:23Z","updated_at":"2018-05-27T14:12:47Z","closed_at":null,"author_association":"NONE","body":"Use case: Alice is ordering a t-shirt online from example.com for 2.65 mBTC. She has Bitcoin, but does not have any funds on the Lightning Network. During checkout she is presented with the option to convert her payment to a Lightning Network channel for an additional small fee of 0.05 mBTC. She agrees and her total is now 2.70 mBTC. After her transaction is complete there is an open Lightning Network channel between Alice and example.com with 2.67 mBTC on the example.com side and 0.00 mBTC on Alice's side. Example.com has an additional 0.02 mBTC on their side as a fee and the remaining 0.03 mBTC is spent for the on-chain transaction fee.\r\n\r\nAdditionally, on checkout there could be an option for Alice to add additional funds to the channel. For example, if Alice added an additional 1.0 mBTC to the transaction the balance would be 2.67 mBTC for example.com and 1.0 mBTC for Alice.\r\n\r\nBenefits:\r\n* Receive Lightning Network funds - Not that Alice has a Lightning Network channel open she will be able to receive a Lightning payment from another individual, employer, exchange, etc..\r\n* Refunds - If example.com wants to issue a refund to Alice, it can be done via Lightning rather than an additional on-chain transaction.\r\n* Using sunk cost - An on-chain payment requires *x* bytes of data and opening a Lightning Network channel requires *y* bytes. Since this transaction would have happened on-chain anyway, there is a sunk cost of *x*. In principle, the additional cost *= y - x*. This is better than making a transaction for the sole purpose of creating a channel.\r\n* Merchants have an incentive to become well-connected nodes and keep funds on the Lightning Network because they can charge an additional fee.\r\n"},"comment":{"url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/comments/392333933","html_url":"https://github.com/btcpayserver/btcpayserver/issues/192#issuecomment-392333933","issue_url":"https://api.github.com/repos/btcpayserver/btcpayserver/issues/192","id":392333933,"user":{"login":"Technifocal","id":20205745,"avatar_url":"https://avatars2.githubusercontent.com/u/20205745?v=4","gravatar_id":"","url":"https://api.github.com/users/Technifocal","html_url":"https://github.com/Technifocal","followers_url":"https://api.github.com/users/Technifocal/followers","following_url":"https://api.github.com/users/Technifocal/following{/other_user}","gists_url":"https://api.github.com/users/Technifocal/gists{/gist_id}","starred_url":"https://api.github.com/users/Technifocal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Technifocal/subscriptions","organizations_url":"https://api.github.com/users/Technifocal/orgs","repos_url":"https://api.github.com/users/Technifocal/repos","events_url":"https://api.github.com/users/Technifocal/events{/privacy}","received_events_url":"https://api.github.com/users/Technifocal/received_events","type":"User","site_admin":false},"created_at":"2018-05-27T14:12:47Z","updated_at":"2018-05-27T14:12:47Z","author_association":"NONE","body":"Two issues I see with that:\r\n\r\n1. I (personally) see no method of identifying a user who pays through that method\r\n2. This is a channel-opening option, and as the buyer (I.E. Alice) will be opening the channel, this should be in her client, not the merchant software\r\n3. How would you recommend performing this action? Currently BOLT11 only covers encoding transactions to nodes you can route to, but if you cannot route to them, you'll need to open a channel and provide an IP address/port if you cannot find them on the network. There's no defined URI for this, other than a standard `${PUBKEY}@${IP}:${PORT}`, and even that lacks an amount to push."}}
{"actor":{"display_login":"Technifocal"}}