--- Log opened Sat Apr 30 00:00:09 2022
01:00 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev
01:04 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
01:08 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #lightning-dev
01:18 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
01:26 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Quit: Konversation terminated!]
01:27 -!- rusty [~rusty@210.185.125.71] has joined #lightning-dev
01:27 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
01:34 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
01:36 -!- rusty [~rusty@210.185.125.71] has quit [Ping timeout: 272 seconds]
01:39 < darosior> ariard: unfortunately i don't think that solves it as reducing the absolute is (very often) not miner-incentive-compatible (and by extension not node-runner-incentive-compatible)
01:40 < darosior> jeremyrubin: https://github.com/bitcoin/bitcoin/pull/23121 contains some discussions around it
01:45 -!- rusty [~rusty@123-243-217-29.tpgi.com.au] has joined #lightning-dev
01:50 -!- rusty [~rusty@123-243-217-29.tpgi.com.au] has quit [Ping timeout: 276 seconds]
01:58 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 246 seconds]
02:32 < remyers[m]> If the thing about off-chain txs like eltoo that prevents you from RBFing the commit tx with a different higher fee paying (confirmed) parent input is that these txs can't be re-signed (because you can't get your counter party to sign), then the pre-signed commit tx should include a fee paying apo-as input, along with the confirmed funding input, and only a single sh_all'd output to the settlement tx.  It can't be pinned with CPFP
02:32 < remyers[m]> because the output is CSV time locked and the tx doesn't need to be re-signed to spend a different apo-as signed input. I must be missing something though... 
03:15 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
03:22 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
04:06 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
05:05 -!- preemz [~preemz@73.58.92.183] has joined #lightning-dev
05:28 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
06:11 -!- preemz [~preemz@73.58.92.183] has quit [Ping timeout: 272 seconds]
06:23 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
06:27 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 256 seconds]
07:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
07:21 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
07:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
08:09 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 272 seconds]
08:31 < jeremyrubin> They don't commit to prevout, so you can pin any eltoo tx as a third party
08:31 < jeremyrubin> E.g I create a bottom of mempool long chain
08:31 < jeremyrubin> And then I attach the last output into the eltoo channel ratchet
08:33 < jeremyrubin> Or just a single witness input with a huge witness and low sats
08:38 < remyers[m]> why won't the tx be replaced by rbf if committed with an alternative confirmed input
08:44 < remyers[m]> any long unconfirmed parent chain in the mempool is unaffected by your RBF of the last child
08:46 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
08:59 < darosior> remyers[m]: Yeah it's not CPFP that make it pinnable. Bumping using inputs you are always the last tx in the chain. It's "just" that you can add so many dusty inputs that they would have to pay an insane absolute fee to RBF it. As mentioned previously that doesn't cost you anything if they do replace it, but note that you could as well let is sit
08:59 < darosior> at the bottom of the mempool for a while and then give a miner out of band (using their APIs or what) spending a single one of the dusty inputs with a larger feerate. This invalidates the large transaction so you don't pay the large absolute fee and you keep your prepared distribution of UTxOs so you can repeat the attack. (I don't think it's
08:59 < darosior> unreasonable to assume that regular users can't use an out-of-band connection to the miners but an attacker can.)
09:05 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Read error: Connection reset by peer]
09:29 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
09:53 < remyers[m]> If someone can add dusty inputs because of ANYONECANPAY, then what if inputs are committed to?
09:55 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
09:58 -!- preemz [~preemz@73.58.92.183] has joined #lightning-dev
09:59 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 250 seconds]
10:57 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
11:19 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 272 seconds]
11:37 -!- preemz [~preemz@73.58.92.183] has quit [Ping timeout: 256 seconds]
12:14 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
12:17 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Quit: Konversation terminated!]
12:17 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
12:19 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Client Quit]
12:19 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 272 seconds]
12:19 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
12:22 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Client Quit]
12:22 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
12:27 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Quit: Konversation terminated!]
12:27 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
12:30 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
12:33 < jeremyrubin> remyers[m]: that would probably fix it? but that sounds brittle
13:25 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
14:36 -!- cmdcode [~cmdcode@2a02:6ea0:d20c:3::b72e] has joined #lightning-dev
14:36 < cmdcode> o/
14:42 < cmdcode> I setup two lightning nodes on regtest, each using their own core client, connecting through tor. Peer connection and on-chain funding works fine, however when I try to fund a channel to the other node, the receiving node dies a horrible death with no error logs. Apparently receiving node is "still synching" (even though it's regtest) so that is a
14:42 < cmdcode> separate issue I'm investigating. My question is this: it is normal for the node to die suddenly in that event? And is there a better place to look for logs than 'getlog debug'?
14:55 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
14:59 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 246 seconds]
15:13 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
15:20 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 276 seconds]
15:28 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
15:35 -!- bucko_ [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
15:38 -!- bucko__ [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
15:38 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 256 seconds]
15:40 -!- bucko_ [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 246 seconds]
15:50 -!- darosior [~darosior@194.36.189.246] has quit [Read error: Connection reset by peer]
15:51 -!- darosior [~darosior@194.36.189.246] has joined #lightning-dev
16:32 < cmdcode> 2022-04-30T23:32:09.108Z UNUSUAL lightningd: You used `--addr=[REDACTED].onion` option with an .onion address, please use `--announce-addr` ! You are lucky in this node live some wizards and fairies, we have done this for you and announce, Be as hidden as wished
16:33 < cmdcode> what does this even mean O_O
16:35 < cmdcode> I was defining the address manually because my tor log keeps spitting out this: `Apr 30 23:34:19.000 [warn] Your application (using socks5 to port 9735) gave Tor a malformed hostname: [scrubbed]. Rejecting the connection.`
17:23 -!- bitromortac [~admin@gateway/tor-sasl/bitromortac] has joined #lightning-dev
17:26 -!- bitromortac_ [~admin@gateway/tor-sasl/bitromortac] has quit [Ping timeout: 240 seconds]
18:09 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 276 seconds]
18:36 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has joined #lightning-dev
18:37 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has quit [Remote host closed the connection]
18:37 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has joined #lightning-dev
19:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
19:48 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
19:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
19:51 -!- bucko__ [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 256 seconds]
20:24 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Remote host closed the connection]
20:42 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
20:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
20:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
20:56 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
20:57 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
20:57 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has quit [Remote host closed the connection]
20:58 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has joined #lightning-dev
21:05 -!- bucko_ [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
21:05 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 276 seconds]
21:10 -!- bucko_ [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 276 seconds]
21:11 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has quit [Remote host closed the connection]
21:12 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has joined #lightning-dev
21:18 -!- rusty [~rusty@118.211.70.216] has joined #lightning-dev
21:23 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
21:30 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Read error: Connection reset by peer]
21:44 -!- cmosher [~cmosher@1381149-v113.1365-static.oswgilaa.metronetinc.net] has joined #lightning-dev
21:44 -!- cmosher is now known as BitcoinLizard
21:45 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
21:47 -!- BitcoinLizard [~cmosher@1381149-v113.1365-static.oswgilaa.metronetinc.net] has left #lightning-dev []
21:54 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has quit [Remote host closed the connection]
21:54 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has joined #lightning-dev
22:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
22:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev
22:02 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 272 seconds]
22:25 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has joined #lightning-dev
22:31 -!- bucko [bucko@gateway/vpn/protonvpn/bucko] has quit [Ping timeout: 240 seconds]
22:34 -!- rusty [~rusty@118.211.70.216] has quit [Ping timeout: 276 seconds]
23:00 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #lightning-dev
23:11 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has quit [Ping timeout: 240 seconds]
23:17 < remyers[m]> <jeremyrubin> "remyers: that would probably fix..." <- Worth investing then, especially as apo-as gives a committed fee input flexibility. This could help with covenant use cases too if I understand earlier comments from darosiorearloer about doing vaults with APO.
23:18 < remyers[m]> * Worth investing then, especially as apo-as gives a committed fee input flexibility. This could help with covenant use cases too if I understand earlier comments from darosior about doing vaults with APO.
23:21 -!- Ghulie [~Ghulie@gateway/tor-sasl/ghulie] has joined #lightning-dev
23:58 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
--- Log closed Sun May 01 00:00:10 2022