--- Log opened Sun Apr 04 00:00:15 2021
00:19 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
00:19 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
00:58 < warren> It just occurred to me that it would be relatively easy to get signet to mirror the fee behavior of mainnet. That would make it easier to test the corner cases I ran into recently.
01:17 < darosior> warren: we test them using regtest and mocking bitcoind's API
02:37 <@cdecker> The c-lightning testing framework has a mock API on top of a reverse proxy that nodes go through, so you can set arbitrary fees. However we don't have a good way to simulate blocksize contention
02:41 -!- nibbier [~quassel@mx01.geekbox.info] has joined #c-lightning
02:44 < nibbier> hi! I have a channel, which is stuck in "CHANNELD_AWAITING_LOCKIN:Will attempt reconnect in 9 seconds". Also the "9 seconds" don't change. other node is gone for 23 days now. how can i abandon this tx/channel?
03:21 -!- arksun [~arksun@92.40.192.0.threembb.co.uk] has quit [Ping timeout: 240 seconds]
05:45 -!- vincenzopalazzo [~vincenzop@host-79-13-113-25.retail.telecomitalia.it] has joined #c-lightning
08:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
08:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
09:15 <@niftynei> no
09:15 <@niftynei> well
09:15 <@niftynei> depends
09:15 <@niftynei> you can force close it
09:16 <@niftynei> nibbier, ^^^
09:21 -!- cltrbreak_MAD2 is now known as ctrlbreak
09:57 < ctrlbreak> Heyo!  How's everyone?
12:55 -!- belcher_ is now known as belcher
14:46 < warren> cdecker: i'm talking specifically about the case where I told c-lightnig to use "slow" and it picked a fee rate so far below "slow" that it was immediately rejected by its bitcoind as below the minimum fee rate for the mempool at that time. Then it's stuck for a while because all the UTXO's it would have spent are reserved.
15:19 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
15:49 -!- vincenzopalazzo [~vincenzop@host-79-13-113-25.retail.telecomitalia.it] has quit [Quit: Leaving]
16:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
16:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
16:55 < nibbier> niftynei: even before it's open? the opening tx is not on the blockchain yet, and as it seems not in any mempool I tried
18:33 < nibbier> trying to close it, but as the funding tx never made it to the chain, I doubt this will do anything.
18:50 -!- fjahr [sid374480@gateway/web/irccloud.com/x-catdfbsuppskvnfw] has quit [Ping timeout: 250 seconds]
18:56 -!- fjahr [sid374480@gateway/web/irccloud.com/x-ilpsykelulslvhrl] has joined #c-lightning
20:21 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
20:23 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
20:24 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
20:29 < az0re> Why do anchor outputs require adding `1 OP_CHECKSEQUENCEVERIFY OP_DROP` to every HTLC script? (see https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md#received-htlc-outputs )
20:30 < az0re> No matter what, on-chain settlement of the HTLC is delayed by 1 block (right? am I interpreting that correctly?). But only when using anchor outputs. Why?
21:02 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
21:14 < nibbier> cdecker: just updated my backup config, thnks for backup-compact :) 
21:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has quit [Remote host closed the connection]
21:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-appjcgjzwowenres] has joined #c-lightning
22:05 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
22:47 -!- opsec_x12 [~opsec_x12@44-25-143-42.ip.hamwan.net] has quit [Remote host closed the connection]
22:48 -!- opsec_x12 [~opsec_x12@44-25-143-42.ip.hamwan.net] has joined #c-lightning
23:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
23:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
23:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
23:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
--- Log closed Mon Apr 05 00:00:16 2021