--- Day changed Thu Aug 09 2018 00:43 -!- ken2812221 [~User@1.200.203.30] has joined #c-lightning 01:01 -!- ken2812221 [~User@1.200.203.30] has quit [Ping timeout: 240 seconds] 01:03 -!- ken2812221 [~User@1.200.203.30] has joined #c-lightning 01:45 < blockstream_bot> [Denys, Blockstream] Hello everyone! Could you please answer few questions about LN and its technology? 01:45 < blockstream_bot> 1. What cryptography in the network is used? RSA, post-quantum cryptography or something else? 01:45 < blockstream_bot> 2. What will be with the participant’s state if he goes offline? Is there any mechanism to prevent fraud from the second party? for example, state guardians or smth else? 01:45 < blockstream_bot> 3. What theoretically is the maximum path length? What routing algorithm is used? 01:45 < blockstream_bot> 4. What traffic/data transfer protocol is used? e.g. TCP/IP, OSI, FTP or smth else? 01:45 < blockstream_bot> 5. How data for path is obtained? What is the method of topology collection? 01:45 < blockstream_bot> 6. What is the average time for payment transaction between 2/5/more participants? 01:45 < blockstream_bot> 7. What are the target platforms for the technology? e.g. Windows, Linux, Mac OS etc 01:45 < blockstream_bot> 8. What programming languages are used? 01:45 < blockstream_bot> 9. Are there any something like payment cycles? The system like clearing 01:45 < blockstream_bot> If yes, the way of cycle finding? What is the frequency of cycle closing? 01:45 < blockstream_bot> 10. Is it possible to handle more than 1 operation in 1channel simultaneously? 02:11 < molz> Denys that's not a few questions, that's a spam, you should have a website to list your questions and only politely post your link if you want help, and you've done on multiple channels on LND slack, now you're doing on Blockstream slack, just stop it 02:12 < molz> and this is being shown on channel #c-lightning on IRC, not going to help you 02:13 < molz> plus you already got help on the LND slack, go do some reading on your own 02:15 < blockstream_bot> [Denys, Blockstream] Hello everyone! Could you please answer few questions about LN and its technology? 02:15 < blockstream_bot> 1. What is the average time for payment transaction between 2/5/more participants? 02:15 < blockstream_bot> 2. Are there any something like payment cycles? The system like clearing 02:15 < blockstream_bot> If yes, the way of cycle finding? What is the frequency of cycle closing? 02:15 < blockstream_bot> 3. Is it possible to handle more than 1 operation in 1channel simultaneously? 02:15 < molz> stop it 03:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:32 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 03:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 255 seconds] 04:23 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 04:32 < blockstream_bot> [Parth Choudhary, Blockstream] so I get this this response when I use `pay` method from pylightning: `{'id': 5, 'payment_hash': '9b8b29990be81d7547209e73fa9264d9743904ffb44988fec39603e8e8452ecc', 'destination': '031d8a6fb6e59bf512b913533edbe2b3e40da6e41d8ca43c2420c849bba8acabd3', 'msatoshi': 12345000, 'msatoshi_sent': 12354363, 'timestamp': 1533814248, 'created_at': 1533814248, 'status': 'complete', 'payment_preima 04:33 < blockstream_bot> [Parth Choudhary, Blockstream] But when I check the walletbalance of destination `031d8a6fb6e59bf512b913533edbe2b3e40da6e41d8ca43c2420c849bba8acabd3` the balance does not increase. 04:33 < blockstream_bot> [Parth Choudhary, Blockstream] What's going on here? Am I missing something? 04:40 < blockstream_bot> [Parth Choudhary, Blockstream] my bad, it is updating now :) 04:43 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 05:17 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:22 -!- annonch [d82f98f2@gateway/web/freenode/ip.216.47.152.242] has quit [Ping timeout: 252 seconds] 05:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:35 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 05:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:54 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 06:11 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.6+deb1 - http://znc.in] 06:22 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 06:38 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 06:46 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 06:51 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Ping timeout: 256 seconds] 06:57 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 07:04 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Ping timeout: 276 seconds] 07:04 -!- provoost- [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 07:04 -!- provoost- is now known as provoostenator 07:24 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:e0ad:51ff:fea6:f1fa] has joined #c-lightning 07:25 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Ping timeout: 265 seconds] 08:29 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-ygjzuvgauuuzlrzm] has joined #c-lightning 08:37 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:e0ad:51ff:fea6:f1fa] has quit [Quit: Leaving] 09:00 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 09:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:36 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 10:42 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 10:50 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-upavfsyjeujznrba] has quit [Quit: Connection closed for inactivity] 10:59 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-ygjzuvgauuuzlrzm] has quit [Quit: Connection closed for inactivity] 11:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-jukuymyuxgveswpx] has left #c-lightning [] 11:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-jukuymyuxgveswpx] has joined #c-lightning 11:42 -!- farmerwampum [~farmerwam@104.129.28.58] has joined #c-lightning 11:42 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-jukuymyuxgveswpx] has quit [Remote host closed the connection] 11:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-jtjntvxxfpmmnlvc] has joined #c-lightning 11:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-jtjntvxxfpmmnlvc] has quit [Ping timeout: 240 seconds] 12:01 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-iqzzhuaailmwwryy] has joined #c-lightning 12:01 < Lightblock_> hello 12:01 < Lightblock_> when you are looking at some channel data 12:01 < Lightblock_> for example 12:01 < Lightblock_> { 12:01 < Lightblock_> "source": "03e50492eab4107a773141bb419e107bda3de3d55652e6e1a41225f06a0bbf2d56", 12:01 < Lightblock_> "destination": "021deedd44ba443c655d454b0d8f90791e12a0ffe07dbaa52016dc40f2d310c55c", 12:01 < Lightblock_> "short_channel_id": "534370:1704:1", 12:01 < Lightblock_> "public": true, 12:01 < Lightblock_> "satoshis": 999000, 12:01 < Lightblock_> "flags": 1, 12:01 < Lightblock_> "active": true, 12:01 < Lightblock_> "last_update": 1532939061, 12:01 < Lightblock_> "base_fee_millisatoshi": 1000, 12:02 < Lightblock_> "fee_per_millionth": 2500, 12:02 < Lightblock_> the parameters like base_fee, fee_per_mill etc. 12:02 < Lightblock_> do they refer to source or destination node? 12:10 < Lightblock_> should be for source I guess? 12:15 < Lightblock_> I found this https://github.com/ElementsProject/lightning/issues/939 explains the question from above well 12:53 <@cdecker> Just to add the short gist of it here: both fees apply to the direction from source to destination, but one is a fixed fee that is leveraged per transfer, while the other is proportional to the transferred amount 13:37 -!- ebx [~ebx@unaffiliated/ebex] has quit [Ping timeout: 256 seconds] 13:49 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 248 seconds] 13:58 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 14:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-rtaiueclejieboou] has joined #c-lightning 14:39 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-iqzzhuaailmwwryy] has quit [Quit: Connection closed for inactivity] 14:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-rtaiueclejieboou] has left #c-lightning [] 14:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-rtaiueclejieboou] has joined #c-lightning 16:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 16:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 17:23 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:53 -!- ThunderDomeWV [~ThunderDo@45.41.65.36] has joined #c-lightning 19:54 < ThunderDomeWV> Hi all! I have two nodes running. One has spendable balance, the other doesn't. Tried to fund a channel on the one with no spendable msatoshi, but it says there's already a channel that's normal and doesn't let me fundchannel with the other node. How do I "rebalance" the channel after paying invoices with the node that will spend to show a spendable balance on the other node? 20:03 < rusty> ThunderDomeWV: You can try establishing a channel via a third node and push funds. Or close & reopen, of course. Splicing in/out of channels is planned for 1.1. 20:06 < ThunderDomeWV> Closing and reopening will incur another on-chain tx fee, I'm assuming? Definitely want to avoid that if it's the case. What am I supposed to do after I add a third node? Not sure what you mean by "push funds". Do I have to send all the available funds from node 2 to node 3, then I can use node 1 and 3 to send back and forth? Or am I misunderstanding. I just started learning all of this today, my brain is on overload right now. 20:06 < rusty> ThunderDomeWV: I understand, it's pretty overwhelming at the moment! 20:08 < rusty> ThunderDomeWV: If all your channel funds are on one side, you can try to route a payment through the other way to push them back, yes. And yes, close and open means two onchain fees, which is definitely suboptimal. 20:09 < ThunderDomeWV> rusty, why is that I'm not seeing any balance increase on my node making invoices? I see them paid, but see no indication that satoshi have been shuffled over? Do you not see that happen until closing the channel? I don't understand why this thing isn't "full duplex" and why the invoicing node's "spendable_msatoshi" isn't increased when it receives an invoice payment. What's making that so hard? It seems like the network would see a payment 20:09 < ThunderDomeWV> has been made, then just increase that variable on the other side? 20:12 < rusty> ThunderDomeWV: Ah! You're underneath the 1% channel reserve, perhaps? 20:13 < rusty> ThunderDomeWV: the reserve ("our_channel_reserve_satoshs") can't be spent, so you until you pass that amount you can't spend any. 20:14 < ThunderDomeWV> rusty, Someone else told me that on Slack so I tried sending an invoice for 40%+ of the channel balance, paid it, saw the spendable_msatoshi go down on the paying node, but nothing on the other node that made the 40%-of-channel invoice. 20:14 < ThunderDomeWV> rusty, 546 is the reserve 20:14 < ThunderDomeWV> definitely over that 20:15 < rusty> ThunderDomeWV: really? That's super-weird... want to pastebin the listfunds output for me? 20:15 < rusty> Or /msg 20:41 < rusty> ... ThunderDomeWV's issue is resolved, but I've filed https://github.com/ElementsProject/lightning/issues/1818 21:19 -!- ThunderDomeWV [~ThunderDo@45.41.65.36] has quit [Ping timeout: 240 seconds]