--- Log opened Tue Oct 29 00:00:48 2019
00:15 -!- queip_ [~queip@unaffiliated/rezurus] has joined #c-lightning
00:16 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 252 seconds]
00:16 -!- queip_ is now known as queip
00:34 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 252 seconds]
00:36 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
01:01 -!- queip_ [~queip@unaffiliated/rezurus] has joined #c-lightning
01:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
01:02 -!- queip_ is now known as queip
01:17 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
01:23 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
01:32 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has quit [Ping timeout: 260 seconds]
01:34 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has joined #c-lightning
01:41 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 245 seconds]
02:21 -!- k3tan172 [~k3tan@unaffiliated/k3tan] has joined #c-lightning
02:24 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Ping timeout: 268 seconds]
02:30 -!- k3tan172 [~k3tan@unaffiliated/k3tan] has quit [Read error: Connection reset by peer]
02:31 -!- k3tan172 [~k3tan@unaffiliated/k3tan] has joined #c-lightning
02:35 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning
02:35 -!- k3tan172 [~k3tan@unaffiliated/k3tan] has quit [Read error: Connection reset by peer]
02:37 -!- jonatack [~jon@213.152.162.15] has joined #c-lightning
02:47 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Ping timeout: 246 seconds]
03:00 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 260 seconds]
03:01 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
03:22 -!- k3tan [~k3tan@unaffiliated/k3tan] has joined #c-lightning
03:34 -!- k3tan [~k3tan@unaffiliated/k3tan] has quit [Ping timeout: 240 seconds]
03:37 -!- k3tan [~k3tan@unaffiliated/k3tan] has joined #c-lightning
04:43 -!- k3tan [~k3tan@unaffiliated/k3tan] has quit [Ping timeout: 268 seconds]
04:51 -!- k3tan [~k3tan@unaffiliated/k3tan] has joined #c-lightning
05:20 < darosior> How comes that we derive the `remote_pubkey`, for the `to_remote` output, from OUR commitment point ?? It means that in order to recover a `to_remote` output to us we need to know the peer per_commitment_point .. Would it not make more sense to derive the `remote_pubkey` from the remote's `per_commitment_point` ?..
05:26 -!- jonatack [~jon@213.152.162.15] has quit [Ping timeout: 240 seconds]
06:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
06:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
06:24 < sword_smith> I am on 027ca7cd0ddc6a61cabcf6bef99f9f771dc66334c653a90d50960d16c3fe672a3d. Can anyone check if they are able to see my node?
06:24 < sword_smith> For some reason I couldn't find it on 1ML.
06:31 < m-schmoock> sword_smith: my node doesnt see it
06:31 < m-schmoock> do you already have channels open?
06:38 < sword_smith> m-schmoock: I am opening one right now. But it is not yet confirmed. The node i well-connect, though. To some big main net nodes.
07:30 < darosior> sword_smith: your node becomes publicly visible after having founded at least one channel
07:31 < sword_smith> darosior: I didn't know that. Thanks :)
07:51 < sword_smith> c-lightning created this funding transaction which I think is rather stingy with its transaction fee. commit-fee was set to 100 when I attempted to open the channel. Was I just unlucky, or is the 9.7 sat/vB an error?
07:52 < sword_smith> estimatesmartfee 2 returns 0.00025782 for me. Which I guess translates to 25.8 sat/vB?
08:20 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
08:31 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has quit [Read error: Connection reset by peer]
08:33 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has joined #c-lightning
08:48 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
08:51 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #c-lightning
09:26 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
09:32 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
09:45 -!- Amperture [~amp@65.79.129.113] has quit [Read error: Connection reset by peer]
10:06 < sword_smith> I seem to have a testnet transaction f177aa6b7b89a09f84382220d18541fa546e01472965d094cb3ddb741f88c587 that does not show up when I run the `listfunds` command.
10:06 < sword_smith> It has 16 confirmations.
10:06 < sword_smith> But listfunds claims that I have no unused outputs
10:07 < sword_smith> Ah. I restart may have solved it :/
10:12 < sword_smith> I seem to have a bug. Where I call fundchannel to 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f. Then it hangs and when I press ctrl+c, all the outputs in listfunds are gone.
10:12 < darosior> You can also use `dev-rescan-outputs`, but  FWIW I experienced this too
10:12 < darosior> I have to rescan more often
10:12 < darosior> than before
10:13 < sword_smith> darosior: Nice. Thanks. That's faster than restarting :)
10:13 < darosior> :)
10:16 < sword_smith> OK. New weird error: Then sent error channel <hex>: Unknon chain=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 . Supported chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
10:17 < sword_smith> My bitcoin test net agrees with blockstream.info about latest block.
10:21 < sword_smith> Sorry. I am fucking it up. Was looking at 1ML on main net.
10:21 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:21 < sword_smith> Should have recognized the block 0 hash on main net.
10:28 < sword_smith> It seems that I was able to connect to main net nodes. But I was not able to open channels with them.
10:28 < sword_smith> I guess I shouldn't be able to connect to main net nodes from test net.
10:41 < sword_smith> I think c-lightning is really buggy at the moment. Are we sure that it is possible to run a main net node and a test net node on the same machine and that the plugins also can handle this?
10:42 < sword_smith> Anyone has experience with this?
10:54 < jb55> sword_smith: yeah I was doing that at one point without any issues... haven't tried recently though
10:56 < sword_smith> jb55: Thanks. The node has just been super buggy for me tonight.
10:57 < sword_smith> And for some reason it made a transaction with a very low fee so have been waiting for that for ages. And some calls to connect/fundchannel (to the ACINQ node on both main net and test net) have been hanging.
11:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
11:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
11:26 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
11:32 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
11:36 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 250 seconds]
11:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:57 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
12:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 276 seconds]
12:05 -!- reallll is now known as belcher
12:15 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
12:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:05 < darosior> > "I think c-lightning is really buggy at the moment. Are we sure that it is possible to run a main net node and a test net node on the same machine and that the plugins also can handle this?" => You can just change the P2P port to have both. Why do you say that "C-lightning is buggy ATM" ?
13:08 < darosior> sword_smith: "It seems that I was able to connect to main net nodes. But I was not able to open channels with them." => Yeah the init message (to initiate a connection) is the same for any network for now, but should soon be changed.
13:09 < darosior> "I guess I shouldn't be able to connect to main net nodes from test net." => Yes you should, at least for now ;) https://github.com/lightningnetwork/lightning-rfc/pull/682
13:18 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
13:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
13:55 < sword_smith> darosior: For a different definition of "should", sure :)
14:00 < sword_smith> But I see your point, c-lightning must of course follow the Bolt specification. So my criticism should have been directed against Bolt and not c-lightning. My bad.
14:03 < sword_smith> "Why do you say that "C-lightning is buggy ATM" ?" => I just had a lot of commands that were hanging. Whenever I attempted to connect to the ACINQ nodes (testnet + main) the command was hanging. When I aborted it (with ctrl+c) all my txoutputs were gone from `listfunds` for some reason.
14:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
14:31 < sword_smith> I know I have a lot of questions and comments. I am sure it will get better soon once I get a bit more familiar with this whole setup :)
14:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
14:42 <@niftynei> sword_smith, was there any indication in the logs of what was happening right before it hung?
14:43 <@niftynei> interop between main + testnet is not rigorously tested (for what i hope are obvious reasons) so it doesn't surprise me that you ran into some problems
14:44 < sword_smith> niftynei: All I remember seeing was something about 'fundchannel cancelled by user' or some such.
15:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds]
15:09 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:22 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds]
15:24 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:43 < molz> sword_smith, separate those two networks to save your time, i run them on different users 
15:45 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
15:47 < sword_smith> molz: Thanks. But they are already separated like that.
16:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:08 < darosior> For now you can rescan outputs, but if you ever experience that again please `tail` your debug.log and fill an issue so that we can investigate further ;-)
17:15 < fiatjaf> htlc_accepted never gets a TLV payload
17:15 < fiatjaf> is that right?
17:15 < fiatjaf> when should I expect it to get one?
17:16 -!- Victor_sueca is now known as Victorsueca
17:31 < rusty> fiatjaf: I have a branch...
17:32 < fiatjaf> (:
17:32 < rusty> https://github.com/ElementsProject/lightning/pull/3167
17:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
17:50 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
18:33 < darosior> rusty: why do we derive the `remote_pubkey`, for the `to_remote` output, from our commitment point ? Would it make  sense to derive the `remote_pubkey` from the remote's `per_commitment_point` ? So that the remote node can recover its `to_remote` output from an unilateral close without having the remote point (e.g. for channels without
18:33 < darosior> option_static_remotekey after dataloss)
18:34 < rusty> darosior: because the remote per-commitment-point can change, depending on what other traffic is occuring?
18:35 < rusty> You wouldn't know which one I'd used, since it would depend on what msgs I'd received from you, I think.
18:43 < darosior> But don't we know the next_remote_percommit ?
18:45 < darosior> ": because the remote per-commitment-point can change, depending on what other traffic is occuring?" > ok, I thought we woulf fail if the remote per_commit_point changed, i'll re read the code tomorrow. Thanks !
19:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
19:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
19:50 < rusty> niftynei: you haven't done the post-release steps....
19:51 < rusty> niftynei: esp, CHANGELOG.md reset...
19:53 < rusty> niftynei: oh, and close out Milestone... MAKING-RELEASES.md def needs to add that!
21:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:23 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
22:24 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
22:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:25 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has quit [Ping timeout: 245 seconds]
23:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds]
23:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]
--- Log closed Wed Oct 30 00:00:49 2019