2023-11-01 18:27:01.593 TRACE [lightning::ln::channel:2399] Upgrading HTLC dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2 to LocalRemoved with a Fulfill in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93!
2023-11-01 18:27:01.593 TRACE [lightning::ln::channel:5404] Updating HTLC state for a newly-sent commitment_signed...
2023-11-01 18:27:01.599 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10381 (really 274 xor<PHONE_NUMBER>89824) for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 for remote, generated by us with fee 4529...
2023-11-01 18:27:01.599 TRACE [lightning::ln::channel:1356]    ...not including inbound HTLC 2 (hash dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2) with value 99999000 due to state (LocalRemoved)
2023-11-01 18:27:01.599 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 36392
2023-11-01 18:27:01.599 TRACE [lightning::ln::channel:1458]    ...including to_local output with value 101744
2023-11-01 18:27:01.599 TRACE [lightning::ln::channelmanager:5510] Tracking monitor update completion action for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93: PaymentClaimed { payment_hash: PaymentHash([219, 190, 126, 43, 250, 214, 252, 179, 85, 103, 103, 237, 77, 0, 42, 32, 109, 142, 77, 104, 223, 154, 75, 19, 215, 140, 108, 11, 181, 189, 117, 178]) }
2023-11-01 18:27:01.599 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:01.599 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93, bringing update_id from 622 to 623 with 2 change(s).
2023-11-01 18:27:01.599 TRACE [lightning::chain::channelmonitor:2676] Updating ChannelMonitor with payment preimage
2023-11-01 18:27:01.600 TRACE [lightning::chain::channelmonitor:2672] Updating ChannelMonitor with latest counterparty commitment transaction info
2023-11-01 18:27:01.600 TRACE [lightning::chain::channelmonitor:2404] Tracking new counterparty commitment transaction with txid ec611bf4d5b1e4b7721f8e4211891a4533add5a93dfa8d001c9ce7473c402bb7 at commitment number<PHONE_NUMBER>10381 with 0 HTLC outputs
2023-11-01 18:27:01.601 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in progress
2023-11-01 18:27:01.601 DEBUG [lightning::ln::channelmanager:5515] ChannelMonitor update for 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in flight, holding messages until the update completes.
2023-11-01 18:27:01.601 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:27:01.605 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:27:02.177 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 924c2ee0b7da9a3b299bc94b0e5579a0e9febac5c01d6c512993b03e964bb863, index: 1 }, monitor_update_id: MonitorUpdateId { contents: OffChain(623) } }
2023-11-01 18:27:02.178 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 623. Current highest is 623. 0 pending in-flight updates.
2023-11-01 18:27:02.178 TRACE [lightning::ln::channel:5102] Creating an announcement_signatures message for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.178 TRACE [lightning::ln::channel:5106] Ignore : Channel is not available for public announcements
2023-11-01 18:27:02.178 TRACE [lightning::ln::channel:3965] Regenerated latest commitment update in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with 0 update_adds, 1 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
2023-11-01 18:27:02.184 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10381 (really 274 xor<PHONE_NUMBER>89824) for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 for remote, generated by us with fee 4529...
2023-11-01 18:27:02.184 TRACE [lightning::ln::channel:1356]    ...not including inbound HTLC 2 (hash dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2) with value 99999000 due to state (LocalRemoved)
2023-11-01 18:27:02.184 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 36392
2023-11-01 18:27:02.184 TRACE [lightning::ln::channel:1458]    ...including to_local output with value 101744
2023-11-01 18:27:02.186 TRACE [lightning::ln::channel:5518] Signed remote commitment tx<PHONE_NUMBER>63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c920100000000c67caf8002288e00000000000022002048513fb52eec0f0f78cf9ac54e7e13fb78400ac49d84898da658693f000ef5f2708d010000000000160014b200ea9d4d937e048174efbd8c7b544c26f3d44ff2384c20 (txid ec611bf4d5b1e4b7721f8e4211891a4533add5a93dfa8d001c9ce7473c402bb7) with redeemscript 47522102a9525c7a3b6eed792e6ad5fad2af3d777c384231ee718483c8cd708f035d1c712103b20a6a25c6628270169912144e900c7badc8f1759dd3526777cdf1c1dbb73d2952ae -> 51b6d4086fc02b3fd8ececf182cab5c020dc3f7b0d6f4f2dc492fbc8f15d4b876b5dc4aaac09aee7538b1d4e650a3cd2eaea7e8cd17b04019e6bd8e6aff25224 in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.187 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 resulting in a commitment update and no RAA, with RAA first
2023-11-01 18:27:02.187 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:27:02.187 DEBUG [mutiny_core::event:250] EVENT: PaymentClaimed claimed payment from payment hash dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2 of 99999000 millisatoshis (Some(99999000) intended)  from 1 htlcs
2023-11-01 18:27:02.187 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:02.192 DEBUG [lightning::ln::peer_handler:2024] Handling UpdateHTLCs event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 with 0 adds, 1 fulfills, 0 fails for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.192 TRACE [lightning::ln::peer_handler:1240] Enqueueing message UpdateFulfillHTLC { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), htlc_id: 2, payment_preimage: PaymentPreimage([176, 87, 92, 30, 205, 192, 183, 114, 62, 205, 74, 1, 239, 197, 77, 137, 215, 51, 48, 152, 19, 131, 249, 193, 187, 234, 9, 17, 207, 65, 110, 114]) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.193 TRACE [lightning::ln::peer_handler:1240] Enqueueing message CommitmentSigned { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), signature:<PHONE_NUMBER>b6d4086fc02b3fd8ececf182cab5c020dc3f7b0d6f4f2dc492fbc8f15d4b8702206b5dc4aaac09aee7538b1d4e650a3cd2eaea7e8cd17b04019e6bd8e6aff25224, htlc_signatures: [] } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.193 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:27:02.194 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:27:02.194 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:02.194 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:02.497 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:02.497 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.498 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:02.672 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:02.673 TRACE [lightning::ln::peer_handler:1586] Received message RevokeAndACK(RevokeAndACK { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), per_commitment_secret: [34, 192, 234, 195, 122, 114, 46, 223, 199, 246, 198, 16, 84, 194, 58, 102, 53, 216, 167, 46, 223, 135, 6, 15, 134, 32, 172, 234, 145, 30, 240, 172], next_per_commitment_point: PublicKey(03fd1d8dcb338af588ed1e8e7a33c9c085c0cacbb1c514fa434320f5eb99aad47257fcb02ed2ab5a25f048f2e0ba7228214ff15d04621bf36d3baba05cbf4784) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.674 TRACE [lightning::ln::channel:3408] Updating HTLCs on receipt of RAA in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93...
2023-11-01 18:27:02.674 TRACE [lightning::ln::channel:3425]  ...removing inbound LocalRemoved dbbe7e2bfad6fcb3556767ed4d002a206d8e4d68df9a4b13d78c6c0bb5bd75b2
2023-11-01 18:27:02.674 DEBUG [lightning::ln::channel:3587] Received a valid revoke_and_ack for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no reply necessary. Releasing monitor update.
2023-11-01 18:27:02.674 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.674 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93, bringing update_id from 623 to 624 with 1 change(s).
2023-11-01 18:27:02.674 TRACE [lightning::chain::channelmonitor:2680] Updating ChannelMonitor with commitment secret
2023-11-01 18:27:02.676 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in progress
2023-11-01 18:27:02.677 DEBUG [lightning::ln::channelmanager:6866] ChannelMonitor update for 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in flight, holding messages until the update completes.
2023-11-01 18:27:02.677 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.678 TRACE [lightning::ln::peer_handler:1586] Received message CommitmentSigned(CommitmentSigned { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), signature: 304402201e60cf01d2f6dcfb9e77acbe5a25df810db33ae5f9b4b6262b84a1216759029e022079d9b06d14316164e64bb7d80311ec84f3f248ece2f2a94119f1fa05f0a51127, htlc_signatures: [] }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.684 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10381 (really 274 xor<PHONE_NUMBER>89824) for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 for us, generated by remote with fee 4529...
2023-11-01 18:27:02.684 TRACE [lightning::ln::channel:1452]    ...including to_local output with value 101744
2023-11-01 18:27:02.684 TRACE [lightning::ln::channel:1458]    ...including to_remote output with value 36392
2023-11-01 18:27:02.684 TRACE [lightning::ln::channel:3000] Checking commitment tx signature 1e60cf01d2f6dcfb9e77acbe5a25df810db33ae5f9b4b6262b84a1216759029e79d9b06d14316164e64bb7d80311ec84f3f248ece2f2a94119f1fa05f0a51127 by key 02a9525c7a3b6eed792e6ad5fad2af3d777c384231ee718483c8cd708f035d1c71 against tx<PHONE_NUMBER>63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c920100000000c67caf8002288e000000000000160014b29a880bd4f773f22caa674dd572ab385e312cdb708d010000000000220020e8f75ef80193b93b23b5854cf9a42b78fd339b5f0af70c4ffe00129db24ab16ff2384c20 (sighash 089615c87862d3ab2287598bf6e3755d4cfffc30858f2aadb7e4608f72d3fee2) with redeemscript 47522102a9525c7a3b6eed792e6ad5fad2af3d777c384231ee718483c8cd708f035d1c712103b20a6a25c6628270169912144e900c7badc8f1759dd3526777cdf1c1dbb73d2952ae in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.687 DEBUG [lightning::ln::channel:3175] Received valid commitment_signed from peer in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93, updated HTLC state but awaiting a monitor update resolution to reply.
2023-11-01 18:27:02.687 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:02.687 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93, bringing update_id from 624 to 625 with 1 change(s).
2023-11-01 18:27:02.688 TRACE [lightning::chain::channelmonitor:2663] Updating ChannelMonitor with latest holder commitment transaction info
2023-11-01 18:27:02.689 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in progress
2023-11-01 18:27:02.689 DEBUG [lightning::ln::channelmanager:6692] ChannelMonitor update for 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in flight, holding messages until the update completes.
2023-11-01 18:27:02.689 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:02.689 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:27:02.691 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:27:02.696 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:02.696 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature:<PHONE_NUMBER>1a53d5d9b0e566f82337c849c9660c5cf31186b92f8977e5aca30acef091f002201e09a95aaf90d860c2cff9c913d3f5049bc1107b695598a78ca77a59a5897ca6, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:27:02.696 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:27:02.769 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:02.769 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature: 304402203fd09fd966cf884ed7e6df8e70bea53e9b94f3285b7cf6edda2e2964dc33efb90220574c9dca7d84c9d9af0f4fbcf724a1412e61413dfb99452f5c4aa039d7c6ecf8, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:27:02.769 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:27:03.126 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 924c2ee0b7da9a3b299bc94b0e5579a0e9febac5c01d6c512993b03e964bb863, index: 1 }, monitor_update_id: MonitorUpdateId { contents: OffChain(624) } }
2023-11-01 18:27:03.329 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 924c2ee0b7da9a3b299bc94b0e5579a0e9febac5c01d6c512993b03e964bb863, index: 1 }, monitor_update_id: MonitorUpdateId { contents: OffChain(625) } }
2023-11-01 18:27:03.329 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 625. Current highest is 625. 0 pending in-flight updates.
2023-11-01 18:27:03.329 TRACE [lightning::ln::channel:5102] Creating an announcement_signatures message for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:03.329 TRACE [lightning::ln::channel:5106] Ignore : Channel is not available for public announcements
2023-11-01 18:27:03.331 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 resulting in no commitment update and an RAA, with commitment first
2023-11-01 18:27:03.332 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with an RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:27:03.332 DEBUG [lightning::ln::peer_handler:2049] Handling SendRevokeAndACK event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:27:03.332 TRACE [lightning::ln::peer_handler:1240] Enqueueing message RevokeAndACK { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), per_commitment_secret: [252, 195, 33, 58, 184, 221, 120, 135, 132, 36, 60, 0, 70, 191, 195, 30, 32, 211, 32, 243, 233, 148, 245, 162, 117, 217, 235, 194, 51, 93, 84, 254], next_per_commitment_point: PublicKey(e5c8bee240bac3b77a96b1affe1fbbd70634f165934815d0d4193d9ec2201650bfb3d50e4611750231bb03051afb8e23b7ad517ab67d87c96887d29596595c42) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:03.332 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:27:03.334 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:27:03.334 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:12.670 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:12.670 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:12.671 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:13.073 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:13.073 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:22.519 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
2023-11-01 18:27:22.822 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:22.822 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:22.823 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:23.269 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:23.269 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:24.388 INFO  [mutiny_core::nodemanager:950] Updated fee estimates!
2023-11-01 18:27:24.389 INFO  [mutiny_core::esplora:221] Starting transaction sync.
2023-11-01 18:27:24.472 INFO  [mutiny_core::esplora:317] Finished transaction sync.
2023-11-01 18:27:24.828 INFO  [mutiny_core::nodemanager:1511] We are synced!
2023-11-01 18:27:32.947 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:32.947 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:32.947 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:33.407 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:33.407 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:43.105 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:43.106 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:43.106 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:43.498 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:43.498 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:52.512 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred
2023-11-01 18:27:52.513 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:27:52.513 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:27:52.552 TRACE [lightning_invoice::utils:537] Creating invoice with payment hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb
2023-11-01 18:27:52.552 TRACE [lightning_invoice::utils:627] Considering 1 channels for invoice route hints
2023-11-01 18:27:52.552 TRACE [lightning_invoice::utils:661] Channel with connected peer exists for invoice route hints
2023-11-01 18:27:52.552 TRACE [lightning_invoice::utils:733] Including channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in invoice route hints
2023-11-01 18:27:52.566 INFO  [mutiny_core::node:931] SUCCESS: generated invoice: lnbc900u1pj59x9gdqqnp4qwmp4snzc9su6380ya9au4wthstesaq2yye0ffhrul5dvget7q52xpp5h48zljvf57a6d07tq7ysvt3vh2wq6zprcescemw65zjuzgkwfzassp5z4vmegr4tceea8sjwfdvjaug2024xg9m063rktjmqdgys2lhssyq9qyysgqcqzptxqrrssrzjqwh05slmksqfkgdyz2wst9fewjmah2amldg3jg2pqzqgvr723mslp2l4eew5p354vsqqqqlgqqqqqzsqyg257mc89sdf62d5je64mx9srj85n7sjgveqshv9l8u8tpc58elcdj000kwg8lmehyjkr3g6np0qgnqmgmdmz4gxtfjgcv5gezpdufungpjtmy9q
2023-11-01 18:27:52.715 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
2023-11-01 18:27:52.794 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:53.242 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:27:53.243 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:53.243 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:27:53.539 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:53.642 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:53.642 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:27:54.537 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:55.541 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:56.542 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:57.543 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:57.592 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.592 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.593 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.593 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.594 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.594 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.599 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.599 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.599 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:57.666 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:27:58.543 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:27:59.540 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:28:00.630 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:28:02.638 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:28:55.214 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:28:55.215 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:28:55.215 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:28:55.218 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:28:55.264 ERROR [mutiny_core::networking::socket:88] got an error reading msg: Network connection closed.
2023-11-01 18:28:55.264 TRACE [lightning::ln::peer_handler:2260] Handling disconnection of peer 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:28:55.264 DEBUG [lightning::ln::channelmanager:8578] Marking channels with 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 disconnected and generating channel_updates.
2023-11-01 18:28:55.265 TRACE [lightning::ln::channel:3750] Peer disconnection resulted in 0 remote-announced HTLC drops on channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:28:55.265 TRACE [mutiny_core::networking::socket:103] WebSocket Closed
2023-11-01 18:28:55.265 DEBUG [mutiny_core::networking::proxy:107] closed websocket
2023-11-01 18:28:55.265 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred
2023-11-01 18:28:55.265 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:28:55.265 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:28:55.265 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
2023-11-01 18:28:56.223 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:00.256 TRACE [mutiny_core::node:1791] going to auto connect to peer: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:01.270 DEBUG [mutiny_core::networking::proxy:69] connected to ws: wss://p.mutinywallet.com
2023-11-01 18:29:01.271 DEBUG [mutiny_core::peermanager:380] connected to peer: PubkeyConnectionInfo { pubkey: PublicKey(f0e18eca0f86800041211951fbbbabdbb7743995059d12a4219b00b4fb43faaec9a0af987303533cdaa9a57b32494716c973a7a53696dd46367cb483a5fa46e6), connection_type: Tcp("<IP_ADDRESS>:9735"), original_connection_string: "03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0@<IP_ADDRESS>:9735" }
2023-11-01 18:29:01.271 TRACE [mutiny_core::peermanager:383] sent 50 to node: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:01.271 TRACE [mutiny_core::networking::socket:65] scheduling descriptor reader
2023-11-01 18:29:01.271 TRACE [mutiny_core::node:1812] auto connected peer: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:01.271 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:01.766 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:01.771 DEBUG [lightning::ln::peer_handler:1374] Finished noise handshake for connection with 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:01.772 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Init { features: [33, 81, 138, 8, 0, 160, 8], networks: Some([6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000]), remote_network_address: Some(TcpIpV4 { addr: [52, 88, 33, 119], port: 9735 }) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:01.772 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:01.772 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:02.623 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:02.623 INFO  [lightning::ln::peer_handler:1539] Received peer Init message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: supported, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsNonzeroFeeHtlcTx: not supported, AnchorsZeroFeeHtlcTx: not supported, ShutdownAnySegwit: supported, Taproot: not supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: supported
2023-11-01 18:29:02.624 DEBUG [lightning::ln::channelmanager:8721] Generating channel_reestablish events for 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:02.624 TRACE [lightning::ln::channel:5237] Enough info to generate a Data Loss Protect with per_commitment_secret 22c0eac37a722edfc7f6c61054c23a6635d8a72edf87060f8620acea911ef0ac for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:02.624 DEBUG [lightning::ln::peer_handler:2067] Handling SendChannelReestablish event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:02.624 TRACE [lightning::ln::peer_handler:1240] Enqueueing message ChannelReestablish { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), next_local_commitment_number: 275, next_remote_commitment_number: 274, your_last_per_commitment_secret: [34, 192, 234, 195, 122, 114, 46, 223, 199, 246, 198, 16, 84, 194, 58, 102, 53, 216, 167, 46, 223, 135, 6, 15, 134, 32, 172, 234, 145, 30, 240, 172], my_current_per_commitment_point: PublicKey(02020202020202020202020202020202020202020202020202020202020202ffcee50f772e0a9972250d4b61b3e5beb95de897c73b4ed1cc35ed013accf1c840), next_funding_txid: None } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:02.625 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:02.657 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:02.658 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature: 304402203fd09fd966cf884ed7e6df8e70bea53e9b94f3285b7cf6edda2e2964dc33efb90220574c9dca7d84c9d9af0f4fbcf724a1412e61413dfb99452f5c4aa039d7c6ecf8, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:29:02.658 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:29:02.658 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:29:02.666 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:02.675 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:02.728 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:02.729 TRACE [lightning::ln::peer_handler:1586] Received message ChannelReestablish(ChannelReestablish { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), next_local_commitment_number: 275, next_remote_commitment_number: 274, your_last_per_commitment_secret: [252, 195, 33, 58, 184, 221, 120, 135, 132, 36, 60, 0, 70, 191, 195, 30, 32, 211, 32, 243, 233, 148, 245, 162, 117, 217, 235, 194, 51, 93, 84, 254], my_current_per_commitment_point: PublicKey(e5c8bee240bac3b77a96b1affe1fbbd70634f165934815d0d4193d9ec2201650bfb3d50e4611750231bb03051afb8e23b7ad517ab67d87c96887d29596595c42), next_funding_txid: None }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:02.730 TRACE [lightning::ln::channel:5102] Creating an announcement_signatures message for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:02.730 TRACE [lightning::ln::channel:5106] Ignore : Channel is not available for public announcements
2023-11-01 18:29:02.730 DEBUG [lightning::ln::channel:4124] Reconnected channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no loss
2023-11-01 18:29:02.730 TRACE [lightning::ln::channelmanager:3356] Attempting to generate channel update for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:02.730 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:02.731 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:29:02.731 TRACE [lightning::ln::peer_handler:2111] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel<PHONE_NUMBER>65077249
2023-11-01 18:29:02.732 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:05.284 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:29:05.284 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:05.284 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:05.682 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:05.683 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:07.914 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:07.915 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature:<PHONE_NUMBER>ae0cfa6954fbeadfd9243f325721bb5f56ce631a92cc7009e9aec8ec7ac1e5022008affc5d71375339ecd459f45c36fb71def4e1456f7899fef0632a1dd96fb8ae, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:29:07.915 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:29:07.988 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:07.988 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature:<PHONE_NUMBER>cb118f74d92ea2d2c70612e7035786dc2dbbc32537886699b0f1b4d1148284022011a60f9cfbef39f1969651fa35b63f785d6263e49ebf3148523523468ad04d9e, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:29:07.988 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:29:13.272 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:13.273 TRACE [lightning::ln::peer_handler:1586] Received message OpenChannel(OpenChannel { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, temporary_channel_id: ChannelId([215, 109, 199, 6, 143, 35, 249, 114, 233, 162, 122, 236, 47, 30, 138, 52, 110, 205, 204, 214, 119, 211, 156, 139, 136, 199, 57, 159, 81, 2, 31, 117]), funding_satoshis: 191920, push_msat: 0, dust_limit_satoshis: 546, max_htlc_value_in_flight_msat:<PHONE_NUMBER>3709551615, channel_reserve_satoshis: 546, htlc_minimum_msat: 0, feerate_per_kw: 2204, to_self_delay: 144, max_accepted_htlcs: 30, funding_pubkey: PublicKey(abb3e4819a223b82a50bf8ad0df7411266d498237c67ab43b46f0262c96b2e2ea1b86069f1400ceef565d1bf654dfe4ad45453ebf4131a6b8fbbddf922290430), revocation_basepoint: PublicKey(6cd8f55d45bde51a014ee7b4892ed4fb84f728f4001dc0d7c1b9c4cdbda40c76461eedafd573eb9d0aa79e34b5c71f3cdb8bf0333255ccea9450083de0e4f213), payment_point: PublicKey(bed927d13a5a324fed3035518646fd278d1c55b27b39cd94d513a45e8b3ccb65d7a6a4cc0fbe797fb613ac0285d122d4246c1564495c2fbe870130840d76fde2), delayed_payment_basepoint: PublicKey(8c43715d599d3cd2b113e10e657dd71b6578ae717fe5ef3dd34e8472bdcfea78b9c87e3b126f536401e3b250dbc715570bb72ade1bd809cbb9d7c0ca4935833b), htlc_basepoint: PublicKey(f62ca3679f1faa950cfedcdfb9b52574582f432bfc66a7e6ce19b6c7a7a46532c41e20f5b7239d0bb046d6c52b2aee50f647f17227ba166dfbcd686bbfdf0d6c), first_per_commitment_point: PublicKey(10950b3dc1b666f5f48b90630bac0476e99d2f58014cdc902467f7f728d32a6d1ad110478ae9c62eb78fc3f5c7922c024ef0a54329ae270186f524e5073b97c0), channel_flags: 0, shutdown_scriptpubkey: Some(Script()), channel_type: Some([0, 16]) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.274 DEBUG [mutiny_core::event:360] EVENT: OpenChannelRequest incoming: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.278 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:29:13.278 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:29:13.281 DEBUG [mutiny_core::event:375] EVENT: OpenChannelRequest accepted
2023-11-01 18:29:13.281 DEBUG [lightning::ln::peer_handler:1919] Handling SendAcceptChannel event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel d76dc7068f23f972e9a27aec2f1e8a346ecdccd677d39c8b88c7399f51021f75
2023-11-01 18:29:13.281 TRACE [lightning::ln::peer_handler:1240] Enqueueing message AcceptChannel { temporary_channel_id: ChannelId([215, 109, 199, 6, 143, 35, 249, 114, 233, 162, 122, 236, 47, 30, 138, 52, 110, 205, 204, 214, 119, 211, 156, 139, 136, 199, 57, 159, 81, 2, 31, 117]), dust_limit_satoshis: 354, max_htlc_value_in_flight_msat: 191920000, channel_reserve_satoshis: 1919, htlc_minimum_msat: 1, minimum_depth: 0, to_self_delay: 144, max_accepted_htlcs: 50, funding_pubkey: PublicKey(d525a3c63145bd6b570c9d1532f0fccd433e72c01c3f9fb38122e488481bff75abe8389a2d9d224bf8a3df4141981af0e780dedb17d5a1dcf09a935c7e883859), revocation_basepoint: PublicKey(40c71e46483b4ae92ff37b48fb9be5667a39c639aa0ae59620b4f3c632730ea3ab7ad0844aab3079e46bba12094d7ed703c0e3c553259827a3e7fd4eb33ab8e4), payment_point: PublicKey(db587331f597d9ddde604ed6220bfd7e44cb20576fa4edcf5ed27327555ac6dd83b260f65ed79688584fd0ab7f51595722f18d43beae9f062a88706aab36f972), delayed_payment_basepoint: PublicKey(be623c5686c0a13968410908b79865505a252a8280d7ffc557f449420303ba8b975987559c6c406a4545a6d498d666225ba64159866b5d58bcba08ae2373c0a0), htlc_basepoint: PublicKey(481f93c765d8d1406397f21eebd55214f594c52ca7f52068e97b72425d79173a9794cf611ce8a584121d8508b8c832b33a189f56a3bb063718fe095a0c186036), first_per_commitment_point: PublicKey(e64ddd385c2fe1098f3252d367554192669feadecd15adbd2c05ee19cb2ebccbc56257df276f051ee81197cb22fda995ba4c1217f8895ad63fe6028eb9e17036), shutdown_scriptpubkey: Some(Script()), channel_type: Some([0, 16]) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.281 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:13.282 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:13.282 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:13.389 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:13.389 TRACE [lightning::ln::peer_handler:1586] Received message FundingCreated(FundingCreated { temporary_channel_id: ChannelId([215, 109, 199, 6, 143, 35, 249, 114, 233, 162, 122, 236, 47, 30, 138, 52, 110, 205, 204, 214, 119, 211, 156, 139, 136, 199, 57, 159, 81, 2, 31, 117]), funding_txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, funding_output_index: 0, signature:<PHONE_NUMBER>987b3a1ba71ac94e6ae90ee6a2144d537c41b73c9672bc6f173bca367c0afa02207bc2d0bd49c16ea8f5eb8b053c31dde5c32dfd09759a5b31652ddfda246a41c4 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.393 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10655 (really 0 xor<PHONE_NUMBER>8415) for channel d76dc7068f23f972e9a27aec2f1e8a346ecdccd677d39c8b88c7399f51021f75 for us, generated by remote with fee 2204...
2023-11-01 18:29:13.393 TRACE [lightning::ln::channel:1458]    ...including to_remote output with value 190325
2023-11-01 18:29:13.393 TRACE [lightning::ln::channel:6641] Checking funding_created tx signature 48987b3a1ba71ac94e6ae90ee6a2144d537c41b73c9672bc6f173bca367c0afa7bc2d0bd49c16ea8f5eb8b053c31dde5c32dfd09759a5b31652ddfda246a41c4 by key 032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab against tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e24800175e7020000000000160014bb794aa3727a47ab3d0d6370faeeaab30df6e06b1f904e20 (sighash f39d2ad2dba739ad232c353e016a2277427e73596d81f666af31a92ab506f3ec) with redeemscript 475221032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab210375ff1b4888e42281b39f3f1cc0723e43cdfcf032159d0c576bbd4531c6a325d552ae for channel d76dc7068f23f972e9a27aec2f1e8a346ecdccd677d39c8b88c7399f51021f75.
2023-11-01 18:29:13.397 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10655 (really 0 xor<PHONE_NUMBER>8415) for channel d76dc7068f23f972e9a27aec2f1e8a346ecdccd677d39c8b88c7399f51021f75 for remote, generated by remote with fee 2204...
2023-11-01 18:29:13.397 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 190325
2023-11-01 18:29:13.397 TRACE [lightning::ln::channel:6653] Initial counterparty tx for channel d76dc7068f23f972e9a27aec2f1e8a346ecdccd677d39c8b88c7399f51021f75 is: txid ec363d6aea5717711cf4aa22b661f251942c118fa6208dd38c3590ecf6667296 tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e24800175e702000000000022002046b89504edae9b7071edcc60515f4dbc8dc536f3aa290cf7764c9998c840774e1f904e20
2023-11-01 18:29:13.400 TRACE [lightning::chain::channelmonitor:2404] Tracking new counterparty commitment transaction with txid ec363d6aea5717711cf4aa22b661f251942c118fa6208dd38c3590ecf6667296 at commitment number<PHONE_NUMBER>10655 with 0 HTLC outputs
2023-11-01 18:29:13.400 INFO  [lightning::ln::channel:6748] Generated funding_signed for peer for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:13.401 TRACE [lightning::chain::chainmonitor:722] Got new ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:13.401 INFO  [lightning::chain::chainmonitor:728] Persistence of new ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:13.402 DEBUG [lightning::ln::channelmanager:6284] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:13.402 DEBUG [lightning::ln::peer_handler:1952] Handling SendFundingSigned event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:13.402 TRACE [lightning::ln::peer_handler:1240] Enqueueing message FundingSigned { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), signature:<PHONE_NUMBER>92da34294cd0764a38da2cbadd44256e579fecebe80c194b948f0c485aea62022027027026fe2c3f957a13ac89b8fe20f651bf4ae21e25cb4ef1b5071b40edb642 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.402 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:13.403 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:13.403 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:13.787 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(0) } }
2023-11-01 18:29:13.788 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 0. Current highest is 0. 0 pending in-flight updates.
2023-11-01 18:29:13.789 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe resulting in no commitment update and no RAA, with commitment first
2023-11-01 18:29:13.790 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, sending channel ready, without announcement
2023-11-01 18:29:13.790 DEBUG [mutiny_core::event:555] EVENT: ChannelPending channel_id: 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, user_channel_id:<PHONE_NUMBER>6886893329409494215509852197, counterparty_node_id: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.790 DEBUG [lightning::ln::peer_handler:1958] Handling SendChannelReady event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:13.790 TRACE [lightning::ln::peer_handler:1240] Enqueueing message ChannelReady { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), next_per_commitment_point: PublicKey(30d6222d184423ea3bc8d9ae84d67699250d8c0c89f33f99a26da6526cc70f57ed325e808903a17860d0d1d10095c213ec42bcd5a5bc62f261e8eff27cd7d10e), short_channel_id_alias: Some(785113974438035463) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:13.791 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:13.794 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:13.795 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:14.173 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:14.174 TRACE [lightning::ln::peer_handler:1586] Received message ChannelReady(ChannelReady { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), next_per_commitment_point: PublicKey(985c738d4edec95be8145890db8bcc30b872ff22dd215705977f7ab1bbab65bc29e7800c44049099b270511bb81ecf3cbff5a21d701467d7aaaa7a63c548f3dd), short_channel_id_alias: Some(17420295268003749114) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:14.174 INFO  [lightning::ln::channel:2736] Received channel_ready from peer for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:14.174 TRACE [lightning::ln::channelmanager:6363] Sending private initial channel_update for our counterparty on channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:14.174 TRACE [lightning::ln::channelmanager:3356] Attempting to generate channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:14.174 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:14.175 TRACE [lightning::ln::peer_handler:2111] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel<PHONE_NUMBER>8003749114
2023-11-01 18:29:14.176 DEBUG [mutiny_core::event:518] EVENT: ChannelReady channel_id: 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, user_channel_id:<PHONE_NUMBER>6886893329409494215509852197, counterparty_node_id: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0, channel_type: StaticRemoteKey: required, AnchorsNonzeroFeeHtlcTx: not supported, AnchorsZeroFeeHtlcTx: not supported, Taproot: not supported, SCIDPrivacy: not supported, ZeroConf: not supported, unknown flags: none
2023-11-01 18:29:14.176 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:14.180 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:14.180 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:15.399 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:29:15.399 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:15.399 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:16.010 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:16.011 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:17.300 INFO  [mutiny_core::nodemanager:950] Updated fee estimates!
2023-11-01 18:29:17.300 INFO  [mutiny_core::esplora:221] Starting transaction sync.
2023-11-01 18:29:17.721 TRACE [lightning::ln::channelmanager:8074] New best block:<PHONE_NUMBER>000000000005e2e6d7e37dc1369bb8bba950fbc9c100ba350f9c1a at height 814869
2023-11-01 18:29:17.722 TRACE [lightning::ln::channel:5102] Creating an announcement_signatures message for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:17.722 TRACE [lightning::ln::channel:5106] Ignore : Channel is not available for public announcements
2023-11-01 18:29:17.722 DEBUG [lightning::chain::chainmonitor:682] New best block<PHONE_NUMBER>000000000005e2e6d7e37dc1369bb8bba950fbc9c100ba350f9c1a at height 814869 provided via best_block_updated
2023-11-01 18:29:17.722 TRACE [lightning::chain::channelmonitor:3567] Processing 0 matched transactions for block at height 814869.
2023-11-01 18:29:17.722 DEBUG [lightning::chain::onchaintx:699] Updating claims view at height 814869 with 0 claim requests
2023-11-01 18:29:17.722 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 814869 with 0 matched transactions in block 814869
2023-11-01 18:29:17.723 TRACE [lightning::chain::onchaintx:951] Bumping 0 candidates
2023-11-01 18:29:17.723 TRACE [lightning::chain::chainmonitor:378] Syncing Channel Monitor for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:29:17.725 DEBUG [lightning::chain::chainmonitor:383] Channel Monitor sync for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in progress, holding events until completion!
2023-11-01 18:29:17.725 TRACE [lightning::chain::channelmonitor:3567] Processing 0 matched transactions for block at height 814869.
2023-11-01 18:29:17.725 DEBUG [lightning::chain::onchaintx:699] Updating claims view at height 814869 with 0 claim requests
2023-11-01 18:29:17.725 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 814869 with 0 matched transactions in block 814869
2023-11-01 18:29:17.725 TRACE [lightning::chain::onchaintx:951] Bumping 0 candidates
2023-11-01 18:29:17.725 TRACE [lightning::chain::chainmonitor:378] Syncing Channel Monitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:17.726 DEBUG [lightning::chain::chainmonitor:383] Channel Monitor sync for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress, holding events until completion!
2023-11-01 18:29:17.727 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:17.729 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:17.729 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.729 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.730 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.730 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.831 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.831 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.831 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.831 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.932 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.932 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.932 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:17.932 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.033 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.034 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.034 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.034 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.122 INFO  [mutiny_core::esplora:317] Finished transaction sync.
2023-11-01 18:29:18.125 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(4294967299) } }
2023-11-01 18:29:18.125 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.125 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.226 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.226 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
2023-11-01 18:29:18.242 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 924c2ee0b7da9a3b299bc94b0e5579a0e9febac5c01d6c512993b03e964bb863, index: 1 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(4294967298) } }
2023-11-01 18:29:18.549 INFO  [mutiny_core::nodemanager:1511] We are synced!
2023-11-01 18:29:19.177 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:19.177 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:29:19.801 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:19.802 TRACE [lightning::ln::peer_handler:1586] Received message UpdateAddHTLC(UpdateAddHTLC { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), htlc_id: 0, amount_msat: 90000000, payment_hash: PaymentHash([189, 78, 47, 201, 137, 167, 187, 166, 191, 203, 7, 137, 6, 46, 44, 186, 156, 13, 8, 35, 198, 97, 140, 237, 218, 160, 165, 193, 34, 206, 72, 187]), cltv_expiry: 814913, skimmed_fee_msat: None, onion_routing_packet: OnionPacket version 0 with hmac [124, 102, 210, 41, 71, 72, 4, 241, 3, 168, 147, 9, 51, 13, 74, 138, 2, 90, 18, 99, 96, 179, 148, 221, 201, 249, 49, 200, 36, 58, 144, 217] }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:20.212 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:20.212 TRACE [lightning::ln::peer_handler:1586] Received message UpdateFee(UpdateFee { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), feerate_per_kw: 4529 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:20.212 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:29:20.212 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:29:20.212 TRACE [lightning::ln::peer_handler:1586] Received message CommitmentSigned(CommitmentSigned { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), signature:<PHONE_NUMBER>7d56ac36fb646db3bec711ba57688d4a40804c8e110c0d079032096f364fae0220348e9d3dba59f4b79e0e54a01798332922d186963703c83c97a32031c6507469, htlc_signatures: [304402202fdc4b6d9ee4fd4d3e8157ec760ed6ff7a729f4f8443b6b639d3e6c77de505fa0220380b997d968314ba2c707e0c005db5db240b605028eee0b5fecbf02cdb39d1c2] }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:20.219 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10654 (really 1 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for us, generated by remote with fee 4529...
2023-11-01 18:29:20.219 TRACE [lightning::ln::channel:1353]    ...including inbound RemoteAnnounced HTLC 0 (hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb) with value 90000000
2023-11-01 18:29:20.219 TRACE [lightning::ln::channel:1458]    ...including to_remote output with value 97863
2023-11-01 18:29:20.219 TRACE [lightning::ln::channel:3000] Checking commitment tx signature 747d56ac36fb646db3bec711ba57688d4a40804c8e110c0d079032096f364fae348e9d3dba59f4b79e0e54a01798332922d186963703c83c97a32031c6507469 by key 032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab against tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e248002905f010000000000220020ceda1ac0f4a204cb90cecb9a4a0b9ec1a3f1a3fa2c98b4f02a1cf122c68efa0f477e010000000000160014bb794aa3727a47ab3d0d6370faeeaab30df6e06b1e904e20 (sighash 7103c215d2c15ce59cbcc44684c3de97b9d3b069be06c034946e2da7254bc3e0) with redeemscript 475221032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab210375ff1b4888e42281b39f3f1cc0723e43cdfcf032159d0c576bbd4531c6a325d552ae in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.222 TRACE [lightning::ln::channel:3071] Checking HTLC tx signature 2fdc4b6d9ee4fd4d3e8157ec760ed6ff7a729f4f8443b6b639d3e6c77de505fa380b997d968314ba2c707e0c005db5db240b605028eee0b5fecbf02cdb39d1c2 by key 036d15bd5d6b7b1e332657f4e4730bfadc5ece9003a1823ab328fa38ded1955f1c against tx<PHONE_NUMBER>34e5cd64063347859f439834d0df52ea5861b683ada2119697dab0351a5bf7cd00000000000000000001215301000000000022002096cb6b3d667e64b6fea8769575aca22d44f55ed94c1ad0aaa0c3f2f76a45a8e600000000 (sighash 009f8df0acfb961e43b1a846cf6c92533d715b354c5852649da7f1441920d871) with redeemscript 8b76a9144c56bac99cffab9c2f2f19b5051994e9172120628763ac6721036d15bd5d6b7b1e332657f4e4730bfadc5ece9003a1823ab328fa38ded1955f1c7c8201208763a914586c3660c5bd224a67541135515fcc138372209a88527c2102a4f4764229718e922ed7111793c3fc4cfa844db27fff2f75c8dcedef01bd0a1252ae677503416f0cb175ac6868 in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe.
2023-11-01 18:29:20.223 TRACE [lightning::ln::channel:3116] Updating HTLC bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb to AwaitingRemoteRevokeToAnnounce due to commitment_signed in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe.
2023-11-01 18:29:20.223 TRACE [lightning::ln::channel:5404] Updating HTLC state for a newly-sent commitment_signed...
2023-11-01 18:29:20.223 TRACE [lightning::ln::channel:5413]  ...promoting inbound AwaitingRemoteRevokeToAnnounce bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb to AwaitingAnnouncedRemoteRevoke
2023-11-01 18:29:20.223 TRACE [lightning::ln::channel:5429]  ...promoting inbound AwaitingRemoteRevokeToAnnounce fee update 4529 to Committed
2023-11-01 18:29:20.227 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10654 (really 1 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for remote, generated by us with fee 4529...
2023-11-01 18:29:20.227 TRACE [lightning::ln::channel:1353]    ...including inbound AwaitingAnnouncedRemoteRevoke HTLC 0 (hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb) with value 90000000
2023-11-01 18:29:20.227 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 97863
2023-11-01 18:29:20.228 DEBUG [lightning::ln::channel:3192] Received valid commitment_signed from peer in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, updating HTLC state and responding with our own commitment_signed and a revoke_and_ack.
2023-11-01 18:29:20.228 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.228 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, bringing update_id from 0 to 1 with 2 change(s).
2023-11-01 18:29:20.228 TRACE [lightning::chain::channelmonitor:2663] Updating ChannelMonitor with latest holder commitment transaction info
2023-11-01 18:29:20.228 TRACE [lightning::chain::channelmonitor:2672] Updating ChannelMonitor with latest counterparty commitment transaction info
2023-11-01 18:29:20.228 TRACE [lightning::chain::channelmonitor:2404] Tracking new counterparty commitment transaction with txid 27e8e0ecb8556dedf2371b19dcd84fb2db403fd65eac94d4afdaf3522d13becc at commitment number<PHONE_NUMBER>10654 with 1 HTLC outputs
2023-11-01 18:29:20.229 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:20.229 DEBUG [lightning::ln::channelmanager:6692] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:20.229 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:20.233 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:20.580 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(1) } }
2023-11-01 18:29:20.580 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 1. Current highest is 1. 0 pending in-flight updates.
2023-11-01 18:29:20.581 TRACE [lightning::ln::channel:3965] Regenerated latest commitment update in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with 0 update_adds, 0 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
2023-11-01 18:29:20.586 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10654 (really 1 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for remote, generated by us with fee 4529...
2023-11-01 18:29:20.586 TRACE [lightning::ln::channel:1353]    ...including inbound AwaitingAnnouncedRemoteRevoke HTLC 0 (hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb) with value 90000000
2023-11-01 18:29:20.586 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 97863
2023-11-01 18:29:20.590 TRACE [lightning::ln::channel:5518] Signed remote commitment tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e248002905f010000000000220020ca9523ecceceb8e41f4e3d6ca27c6da7911d2154ead287cc0b39080569f530d4477e010000000000220020a56507dc755b754fe393d7ffb74ee5f814d2f02ec615211a2574073c1895872f1e904e20 (txid 27e8e0ecb8556dedf2371b19dcd84fb2db403fd65eac94d4afdaf3522d13becc) with redeemscript 475221032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab210375ff1b4888e42281b39f3f1cc0723e43cdfcf032159d0c576bbd4531c6a325d552ae -> 6fbc7a33e346c3ab74ff0ae634b987773d1ee2897a6305446164cc75eff413092349aa0e1fcd1d1e46858e24c4870e21d139fba63e52cb8ea0583d4fd811093e in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.590 TRACE [lightning::ln::channel:5524] Signed remote HTLC tx<PHONE_NUMBER>ccbe132d52f3daafd494ac5ed63f40dbb24fd8dc191b37f2ed6d55b8ece0e82700000000000000000001d653010000000000220020a56507dc755b754fe393d7ffb74ee5f814d2f02ec615211a2574073c1895872f416f0c00 with redeemscript 8576a9142d4e8c9eabe1223386f4bd16a325b0e471f05aaf8763ac6721038ace5e72414fcceb1df91de4d5f44f4d18410fc350dcfc06631fc7bcd4204fd77c820120876475527c2103edd64c36edb47f4d93f4ed6300450d1d35b0bef00c30ab28fef39d421b1cd1e352ae67a914586c3660c5bd224a67541135515fcc138372209a88ac6868 with pubkey 03edd64c36edb47f4d93f4ed6300450d1d35b0bef00c30ab28fef39d421b1cd1e3 -> 387e3a01e4e4f856ef939b77915059e4737a6ff33e738416804a64954f0c9f142e24a3f110e6a56a2ef6aa5a773be43a632959296dab86f583596626df10c298 in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.590 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe resulting in a commitment update and an RAA, with RAA first
2023-11-01 18:29:20.590 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with an RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:29:20.590 DEBUG [lightning::ln::peer_handler:2049] Handling SendRevokeAndACK event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.590 TRACE [lightning::ln::peer_handler:1240] Enqueueing message RevokeAndACK { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), per_commitment_secret: [72, 156, 207, 127, 128, 129, 144, 4, 94, 208, 47, 197, 66, 147, 193, 64, 159, 79, 77, 229, 130, 174, 69, 11, 137, 208, 86, 216, 200, 80, 197, 105], next_per_commitment_point: PublicKey(28117c828213d4e708a26e9602bb5f35da7987d3f595e288de68dc854a201baa3da018b3f47aa04742882390f6a2f2d30121139c239efa3397d68f0f9118130d) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:20.590 DEBUG [lightning::ln::peer_handler:2024] Handling UpdateHTLCs event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 with 0 adds, 0 fulfills, 0 fails for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:20.591 TRACE [lightning::ln::peer_handler:1240] Enqueueing message CommitmentSigned { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), signature: 304402206fbc7a33e346c3ab74ff0ae634b987773d1ee2897a6305446164cc75eff4130902202349aa0e1fcd1d1e46858e24c4870e21d139fba63e52cb8ea0583d4fd811093e, htlc_signatures: [30440220387e3a01e4e4f856ef939b77915059e4737a6ff33e738416804a64954f0c9f1402202e24a3f110e6a56a2ef6aa5a773be43a632959296dab86f583596626df10c298] } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:20.591 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:20.593 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:20.593 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:20.593 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:21.104 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:21.105 TRACE [lightning::ln::peer_handler:1586] Received message RevokeAndACK(RevokeAndACK { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), per_commitment_secret: [30, 172, 194, 176, 153, 17, 65, 109, 191, 68, 219, 132, 156, 167, 12, 33, 66, 92, 14, 240, 241, 51, 88, 225, 243, 41, 11, 124, 215, 59, 210, 77], next_per_commitment_point: PublicKey(61a1f8e262470ec9f70f9e706b88acf9d2dab17835d4440b095f34cc97972dab979991cad2c2df7b825f168cf7e2fc0164706ae5bdf753526cbfa21815296c3d) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:21.106 TRACE [lightning::ln::channel:3408] Updating HTLCs on receipt of RAA in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe...
2023-11-01 18:29:21.106 TRACE [lightning::ln::channel:3476]  ...promoting inbound AwaitingAnnouncedRemoteRevoke bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb to Committed
2023-11-01 18:29:21.106 DEBUG [lightning::ln::channel:3587] Received a valid revoke_and_ack for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no reply necessary. Releasing monitor update.
2023-11-01 18:29:21.106 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:21.106 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, bringing update_id from 1 to 2 with 1 change(s).
2023-11-01 18:29:21.107 TRACE [lightning::chain::channelmonitor:2680] Updating ChannelMonitor with commitment secret
2023-11-01 18:29:21.108 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:21.108 DEBUG [lightning::ln::channelmanager:6866] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:21.108 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:21.110 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:21.113 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:21.243 TRACE [lightning_invoice::utils:537] Creating invoice with payment hash ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593
2023-11-01 18:29:21.243 TRACE [lightning_invoice::utils:627] Considering 2 channels for invoice route hints
2023-11-01 18:29:21.243 TRACE [lightning_invoice::utils:630] Ignoring channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for invoice route hints
2023-11-01 18:29:21.243 TRACE [lightning_invoice::utils:661] Channel with connected peer exists for invoice route hints
2023-11-01 18:29:21.244 TRACE [lightning_invoice::utils:733] Including channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in invoice route hints
2023-11-01 18:29:21.261 INFO  [mutiny_core::node:931] SUCCESS: generated invoice: lnbc900u1pj59xgpdqqnp4qwmp4snzc9su6380ya9au4wthstesaq2yye0ffhrul5dvget7q52xpp54vtymyyslp0hr3k6mwygxkllh36vszmm0mjq2s7wu3w2l32c6kfssp56jxzqcqt3c90q7em5hp6n83lwn9e3ew4ldqgl4e67n9g9z59a8qs9qyysgqcqzptxqrrssrzjqwh05slmksqfkgdyz2wst9fewjmah2amldg3jg2pqzqgvr723mslp2l4eew5p354vsqqqqlgqqqqqzsqygl2f4cmp65k4zf2gpc77sgv55u56z8s5eswq9a7lu4kdph07cuvmjzusgxacdqmha48vu454g94nwlts96xajt7amm30665p5y8a9uksqyxzflt
2023-11-01 18:29:21.478 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:21.543 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(2) } }
2023-11-01 18:29:21.543 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 2. Current highest is 2. 0 pending in-flight updates.
2023-11-01 18:29:21.543 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe resulting in no commitment update and no RAA, with RAA first
2023-11-01 18:29:21.543 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no RAA, no commitment update, 1 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:29:21.543 DEBUG [mutiny_core::event:453] EVENT: PendingHTLCsForwardable: 100ms, processing...
2023-11-01 18:29:21.546 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:21.644 DEBUG [mutiny_core::event:229] EVENT: PaymentReceived received payment from payment hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb of 90000000 millisatoshis to Some(PublicKey(a328f02b23d6e8e7e3a6f432210a749817bccb55de4b27ef44cd61c162c21ab6abdb0a94466a5a9bbf052f843c6786d139047481fb930294aa31b078bb1486ee))
2023-11-01 18:29:21.644 DEBUG [lightning::ln::channel:2311] Claiming inbound HTLC id 0 with payment hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb with preimage 1b0b790455270a5a0a19b6a343ee21772b9f132e7d5ad28ac5676b9575d9f9a1
2023-11-01 18:29:21.644 TRACE [lightning::ln::channel:2399] Upgrading HTLC bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb to LocalRemoved with a Fulfill in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe!
2023-11-01 18:29:21.644 TRACE [lightning::ln::channel:5404] Updating HTLC state for a newly-sent commitment_signed...
2023-11-01 18:29:21.645 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10653 (really 2 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for remote, generated by us with fee 4529...
2023-11-01 18:29:21.645 TRACE [lightning::ln::channel:1356]    ...not including inbound HTLC 0 (hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb) with value 90000000 due to state (LocalRemoved)
2023-11-01 18:29:21.645 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 98642
2023-11-01 18:29:21.645 TRACE [lightning::ln::channel:1458]    ...including to_local output with value 90000
2023-11-01 18:29:21.645 TRACE [lightning::ln::channelmanager:5510] Tracking monitor update completion action for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe: PaymentClaimed { payment_hash: PaymentHash([189, 78, 47, 201, 137, 167, 187, 166, 191, 203, 7, 137, 6, 46, 44, 186, 156, 13, 8, 35, 198, 97, 140, 237, 218, 160, 165, 193, 34, 206, 72, 187]) }
2023-11-01 18:29:21.645 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:21.645 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, bringing update_id from 2 to 3 with 2 change(s).
2023-11-01 18:29:21.645 TRACE [lightning::chain::channelmonitor:2676] Updating ChannelMonitor with payment preimage
2023-11-01 18:29:21.645 TRACE [lightning::chain::channelmonitor:2672] Updating ChannelMonitor with latest counterparty commitment transaction info
2023-11-01 18:29:21.645 TRACE [lightning::chain::channelmonitor:2404] Tracking new counterparty commitment transaction with txid 059c0caa8f5dbfc4cd4c1360ca5165f95778ec892fe1b945e26dae5b7d4921a3 at commitment number<PHONE_NUMBER>10653 with 0 HTLC outputs
2023-11-01 18:29:21.646 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:21.646 DEBUG [lightning::ln::channelmanager:5515] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:21.646 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:21.646 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:22.075 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(3) } }
2023-11-01 18:29:22.075 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 3. Current highest is 3. 0 pending in-flight updates.
2023-11-01 18:29:22.076 TRACE [lightning::ln::channel:3965] Regenerated latest commitment update in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with 0 update_adds, 1 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
2023-11-01 18:29:22.082 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10653 (really 2 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for remote, generated by us with fee 4529...
2023-11-01 18:29:22.082 TRACE [lightning::ln::channel:1356]    ...not including inbound HTLC 0 (hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb) with value 90000000 due to state (LocalRemoved)
2023-11-01 18:29:22.082 TRACE [lightning::ln::channel:1452]    ...including to_remote output with value 98642
2023-11-01 18:29:22.082 TRACE [lightning::ln::channel:1458]    ...including to_local output with value 90000
2023-11-01 18:29:22.084 TRACE [lightning::ln::channel:5518] Signed remote commitment tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e248002905f0100000000001600145bf8152cef72275441e797af706afbe091488f2e5281010000000000220020091182abe52b5316c9b47e9aaea7d9aa91e2e473e861ccf3fd89802f2d4f8fa91d904e20 (txid 059c0caa8f5dbfc4cd4c1360ca5165f95778ec892fe1b945e26dae5b7d4921a3) with redeemscript 475221032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab210375ff1b4888e42281b39f3f1cc0723e43cdfcf032159d0c576bbd4531c6a325d552ae -> 311c94dc3f2f69ccd14895fc89a80f05ea2d14e8a8f4060626b37fad44f18628196ba9dffcd3d0687ea22b82656d1ba255a8176e5bd01f1e749cc862daac2e5f in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.084 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe resulting in a commitment update and no RAA, with RAA first
2023-11-01 18:29:22.084 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:29:22.085 DEBUG [mutiny_core::event:250] EVENT: PaymentClaimed claimed payment from payment hash bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb of 90000000 millisatoshis (Some(90000000) intended)  from 1 htlcs
2023-11-01 18:29:22.085 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:22.091 DEBUG [lightning::ln::peer_handler:2024] Handling UpdateHTLCs event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 with 0 adds, 1 fulfills, 0 fails for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.091 TRACE [lightning::ln::peer_handler:1240] Enqueueing message UpdateFulfillHTLC { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), htlc_id: 0, payment_preimage: PaymentPreimage([27, 11, 121, 4, 85, 39, 10, 90, 10, 25, 182, 163, 67, 238, 33, 119, 43, 159, 19, 46, 125, 90, 210, 138, 197, 103, 107, 149, 117, 217, 249, 161]) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:22.091 TRACE [lightning::ln::peer_handler:1240] Enqueueing message CommitmentSigned { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), signature:<PHONE_NUMBER>1c94dc3f2f69ccd14895fc89a80f05ea2d14e8a8f4060626b37fad44f186280220196ba9dffcd3d0687ea22b82656d1ba255a8176e5bd01f1e749cc862daac2e5f, htlc_signatures: [] } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:22.091 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:22.093 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:22.094 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:22.094 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:22.554 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:22.579 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:22.579 TRACE [lightning::ln::peer_handler:1586] Received message RevokeAndACK(RevokeAndACK { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), per_commitment_secret: [7, 135, 64, 113, 5, 233, 191, 84, 2, 210, 75, 197, 178, 232, 124, 73, 14, 22, 180, 120, 75, 168, 144, 3, 51, 0, 103, 42, 83, 197, 113, 249], next_per_commitment_point: PublicKey(8cf12d1df8a100088e1c8adb6ecc0b6ac69ee569ac34884271b3c506a21e27356f9f6ef1d9111cef584333e11e128efe72e9027736735551cdf217dc130b1146) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:22.579 TRACE [lightning::ln::channel:3408] Updating HTLCs on receipt of RAA in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe...
2023-11-01 18:29:22.579 TRACE [lightning::ln::channel:3425]  ...removing inbound LocalRemoved bd4e2fc989a7bba6bfcb0789062e2cba9c0d0823c6618ceddaa0a5c122ce48bb
2023-11-01 18:29:22.579 DEBUG [lightning::ln::channel:3587] Received a valid revoke_and_ack for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no reply necessary. Releasing monitor update.
2023-11-01 18:29:22.579 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.579 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, bringing update_id from 3 to 4 with 1 change(s).
2023-11-01 18:29:22.580 TRACE [lightning::chain::channelmonitor:2680] Updating ChannelMonitor with commitment secret
2023-11-01 18:29:22.580 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:22.580 DEBUG [lightning::ln::channelmanager:6866] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:22.580 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.581 TRACE [lightning::ln::peer_handler:1586] Received message CommitmentSigned(CommitmentSigned { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), signature: 304402200fd4d35b37508f0040ca005ecb260efb5cf118af28f6c800243e039761f1b7ad02203ef39304f29a7f06a55d094ee3c37f719ab83ae0fc0da2720b13f9f96e509043, htlc_signatures: [] }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:22.583 TRACE [lightning::ln::channel:1291] Building commitment transaction number<PHONE_NUMBER>10653 (really 2 xor<PHONE_NUMBER>8415) for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for us, generated by remote with fee 4529...
2023-11-01 18:29:22.583 TRACE [lightning::ln::channel:1452]    ...including to_local output with value 90000
2023-11-01 18:29:22.583 TRACE [lightning::ln::channel:1458]    ...including to_remote output with value 98642
2023-11-01 18:29:22.583 TRACE [lightning::ln::channel:3000] Checking commitment tx signature 0fd4d35b37508f0040ca005ecb260efb5cf118af28f6c800243e039761f1b7ad3ef39304f29a7f06a55d094ee3c37f719ab83ae0fc0da2720b13f9f96e509043 by key 032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab against tx<PHONE_NUMBER>85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe0000000000016e248002905f010000000000220020f63ee47a0248f9e282f5551d4dc495644e64d0e47e086980daf79f06f5ed19025281010000000000160014bb794aa3727a47ab3d0d6370faeeaab30df6e06b1d904e20 (sighash 17740f5584c23a7f7549d3bba0fc8de5cb95a038b7fe43b5dbfe26d48e199339) with redeemscript 475221032e2e6bc962026fb443ab677c2398d4661241f70dadf80ba5823b229a81e4b3ab210375ff1b4888e42281b39f3f1cc0723e43cdfcf032159d0c576bbd4531c6a325d552ae in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.584 DEBUG [lightning::ln::channel:3175] Received valid commitment_signed from peer in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, updated HTLC state but awaiting a monitor update resolution to reply.
2023-11-01 18:29:22.584 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:22.584 INFO  [lightning::chain::channelmonitor:2631] Applying update to monitor 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe, bringing update_id from 4 to 5 with 1 change(s).
2023-11-01 18:29:22.584 TRACE [lightning::chain::channelmonitor:2663] Updating ChannelMonitor with latest holder commitment transaction info
2023-11-01 18:29:22.585 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in progress
2023-11-01 18:29:22.585 DEBUG [lightning::ln::channelmanager:6692] ChannelMonitor update for 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe in flight, holding messages until the update completes.
2023-11-01 18:29:22.585 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:22.586 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:22.914 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(4) } }
2023-11-01 18:29:23.017 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: beea32649eac00987580b7f1a04393adfb02fccb6d0a497499056c127389b585, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(5) } }
2023-11-01 18:29:23.018 TRACE [lightning::ln::channelmanager:5910] ChannelMonitor updated to 5. Current highest is 5. 0 pending in-flight updates.
2023-11-01 18:29:23.019 DEBUG [lightning::ln::channel:3853] Restored monitor updating in channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe resulting in no commitment update and an RAA, with commitment first
2023-11-01 18:29:23.019 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with an RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:29:23.019 DEBUG [lightning::ln::peer_handler:2049] Handling SendRevokeAndACK event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:29:23.019 TRACE [lightning::ln::peer_handler:1240] Enqueueing message RevokeAndACK { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), per_commitment_secret: [168, 13, 186, 163, 126, 242, 29, 215, 218, 12, 165, 250, 247, 120, 248, 169, 186, 223, 31, 16, 197, 220, 13, 36, 243, 245, 68, 191, 160, 252, 98, 183], next_per_commitment_point: PublicKey(56bd61946b72917ee26f6443820adec86ff645839500e22289697922822b6c1275defbd257012843b2f475d88b29c6d05e1569d945337ff057a3beca8b7a7964) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:23.020 TRACE [mutiny_core::background:557] Persisting ChannelManager...
2023-11-01 18:29:23.023 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
2023-11-01 18:29:23.023 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:23.554 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:24.556 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:25.399 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
2023-11-01 18:29:25.555 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:25.601 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:29:25.601 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:25.601 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:29:26.001 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:29:26.002 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:29:26.556 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:27.556 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:28.555 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:29.647 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:29:31.637 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:04.941 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:04.999 ERROR [mutiny_core::networking::socket:88] got an error reading msg: Network connection closed.
2023-11-01 18:30:04.999 TRACE [lightning::ln::peer_handler:2260] Handling disconnection of peer 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:04.999 DEBUG [lightning::ln::channelmanager:8578] Marking channels with 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 disconnected and generating channel_updates.
2023-11-01 18:30:04.999 TRACE [lightning::ln::channel:3750] Peer disconnection resulted in 0 remote-announced HTLC drops on channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:04.999 TRACE [lightning::ln::channel:3750] Peer disconnection resulted in 0 remote-announced HTLC drops on channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:05.000 TRACE [mutiny_core::networking::socket:103] WebSocket Closed
2023-11-01 18:30:05.000 DEBUG [mutiny_core::networking::proxy:107] closed websocket
2023-11-01 18:30:05.000 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred
2023-11-01 18:30:05.000 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:30:05.000 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
2023-11-01 18:30:05.000 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:30:05.000 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
2023-11-01 18:30:05.945 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/ab164d9090f85f71c6dadb88835bffbc74c80b7b7ee40543cee45cafc558d593_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:09.982 TRACE [mutiny_core::node:1791] going to auto connect to peer: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:10.984 DEBUG [mutiny_core::networking::proxy:69] connected to ws: wss://p.mutinywallet.com
2023-11-01 18:30:10.988 DEBUG [mutiny_core::peermanager:380] connected to peer: PubkeyConnectionInfo { pubkey: PublicKey(f0e18eca0f86800041211951fbbbabdbb7743995059d12a4219b00b4fb43faaec9a0af987303533cdaa9a57b32494716c973a7a53696dd46367cb483a5fa46e6), connection_type: Tcp("<IP_ADDRESS>:9735"), original_connection_string: "03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0@<IP_ADDRESS>:9735" }
2023-11-01 18:30:10.988 TRACE [mutiny_core::peermanager:383] sent 50 to node: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:10.988 TRACE [mutiny_core::networking::socket:65] scheduling descriptor reader
2023-11-01 18:30:10.988 TRACE [mutiny_core::node:1812] auto connected peer: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:10.989 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.092 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.097 DEBUG [lightning::ln::peer_handler:1374] Finished noise handshake for connection with 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.098 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Init { features: [33, 81, 138, 8, 0, 160, 8], networks: Some([6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000]), remote_network_address: Some(TcpIpV4 { addr: [52, 88, 33, 119], port: 9735 }) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.098 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.098 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.311 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.311 INFO  [lightning::ln::peer_handler:1539] Received peer Init message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: supported, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsNonzeroFeeHtlcTx: not supported, AnchorsZeroFeeHtlcTx: not supported, ShutdownAnySegwit: supported, Taproot: not supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: supported
2023-11-01 18:30:11.312 DEBUG [lightning::ln::channelmanager:8721] Generating channel_reestablish events for 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.312 TRACE [lightning::ln::channel:5237] Enough info to generate a Data Loss Protect with per_commitment_secret<PHONE_NUMBER>e9bf5402d24bc5b2e87c490e16b4784ba890033300672a53c571f9 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.312 TRACE [lightning::ln::channel:5237] Enough info to generate a Data Loss Protect with per_commitment_secret 22c0eac37a722edfc7f6c61054c23a6635d8a72edf87060f8620acea911ef0ac for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:11.313 DEBUG [lightning::ln::peer_handler:2067] Handling SendChannelReestablish event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.313 TRACE [lightning::ln::peer_handler:1240] Enqueueing message ChannelReestablish { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), next_local_commitment_number: 3, next_remote_commitment_number: 2, your_last_per_commitment_secret: [7, 135, 64, 113, 5, 233, 191, 84, 2, 210, 75, 197, 178, 232, 124, 73, 14, 22, 180, 120, 75, 168, 144, 3, 51, 0, 103, 42, 83, 197, 113, 249], my_current_per_commitment_point: PublicKey(02020202020202020202020202020202020202020202020202020202020202ffcee50f772e0a9972250d4b61b3e5beb95de897c73b4ed1cc35ed013accf1c840), next_funding_txid: None } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.313 DEBUG [lightning::ln::peer_handler:2067] Handling SendChannelReestablish event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:11.313 TRACE [lightning::ln::peer_handler:1240] Enqueueing message ChannelReestablish { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), next_local_commitment_number: 275, next_remote_commitment_number: 274, your_last_per_commitment_secret: [34, 192, 234, 195, 122, 114, 46, 223, 199, 246, 198, 16, 84, 194, 58, 102, 53, 216, 167, 46, 223, 135, 6, 15, 134, 32, 172, 234, 145, 30, 240, 172], my_current_per_commitment_point: PublicKey(02020202020202020202020202020202020202020202020202020202020202ffcee50f772e0a9972250d4b61b3e5beb95de897c73b4ed1cc35ed013accf1c840), next_funding_txid: None } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.313 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.313 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.314 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.314 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature:<PHONE_NUMBER>cb118f74d92ea2d2c70612e7035786dc2dbbc32537886699b0f1b4d1148284022011a60f9cfbef39f1969651fa35b63f785d6263e49ebf3148523523468ad04d9e, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:30:11.314 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:11.314 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.314 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:11.314 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:11.321 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.329 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.350 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.350 TRACE [lightning::ln::peer_handler:1586] Received message ChannelReestablish(ChannelReestablish { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), next_local_commitment_number: 3, next_remote_commitment_number: 2, your_last_per_commitment_secret: [168, 13, 186, 163, 126, 242, 29, 215, 218, 12, 165, 250, 247, 120, 248, 169, 186, 223, 31, 16, 197, 220, 13, 36, 243, 245, 68, 191, 160, 252, 98, 183], my_current_per_commitment_point: PublicKey(56bd61946b72917ee26f6443820adec86ff645839500e22289697922822b6c1275defbd257012843b2f475d88b29c6d05e1569d945337ff057a3beca8b7a7964), next_funding_txid: None }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.351 DEBUG [lightning::ln::channel:4124] Reconnected channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no loss
2023-11-01 18:30:11.351 TRACE [lightning::ln::channelmanager:3356] Attempting to generate channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.351 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.352 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:30:11.352 TRACE [lightning::ln::peer_handler:1586] Received message ChannelReestablish(ChannelReestablish { channel_id: ChannelId([99, 184, 75, 150, 62, 176, 147, 41, 81, 108, 29, 192, 197, 186, 254, 233, 160, 121, 85, 14, 75, 201, 155, 41, 59, 154, 218, 183, 224, 46, 76, 147]), next_local_commitment_number: 275, next_remote_commitment_number: 274, your_last_per_commitment_secret: [252, 195, 33, 58, 184, 221, 120, 135, 132, 36, 60, 0, 70, 191, 195, 30, 32, 211, 32, 243, 233, 148, 245, 162, 117, 217, 235, 194, 51, 93, 84, 254], my_current_per_commitment_point: PublicKey(e5c8bee240bac3b77a96b1affe1fbbd70634f165934815d0d4193d9ec2201650bfb3d50e4611750231bb03051afb8e23b7ad517ab67d87c96887d29596595c42), next_funding_txid: None }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.353 TRACE [lightning::ln::channel:5102] Creating an announcement_signatures message for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:11.353 TRACE [lightning::ln::channel:5106] Ignore : Channel is not available for public announcements
2023-11-01 18:30:11.353 DEBUG [lightning::ln::channel:4124] Reconnected channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no loss
2023-11-01 18:30:11.353 TRACE [lightning::ln::channelmanager:3356] Attempting to generate channel update for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:11.353 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93
2023-11-01 18:30:11.353 TRACE [lightning::ln::channelmanager:5806] Handling channel resumption for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-11-01 18:30:11.353 TRACE [lightning::ln::peer_handler:2111] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel<PHONE_NUMBER>8003749114
2023-11-01 18:30:11.353 TRACE [lightning::ln::peer_handler:2111] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel<PHONE_NUMBER>65077249
2023-11-01 18:30:11.353 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.353 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:11.467 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:11.467 TRACE [lightning::ln::peer_handler:1586] Received message ChannelReady(ChannelReady { channel_id: ChannelId([133, 181, 137, 115, 18, 108, 5, 153, 116, 73, 10, 109, 203, 252, 2, 251, 173, 147, 67, 160, 241, 183, 128, 117, 152, 0, 172, 158, 100, 50, 234, 190]), next_per_commitment_point: PublicKey(985c738d4edec95be8145890db8bcc30b872ff22dd215705977f7ab1bbab65bc29e7800c44049099b270511bb81ecf3cbff5a21d701467d7aaaa7a63c548f3dd), short_channel_id_alias: Some(17420295268003749114) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:11.468 TRACE [lightning::ln::channelmanager:6363] Sending private initial channel_update for our counterparty on channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.468 TRACE [lightning::ln::channelmanager:3356] Attempting to generate channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.468 TRACE [lightning::ln::channelmanager:3366] Generating channel update for channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe
2023-11-01 18:30:11.469 TRACE [lightning::ln::peer_handler:2111] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel<PHONE_NUMBER>8003749114
2023-11-01 18:30:11.469 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:15.113 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
2023-11-01 18:30:15.113 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:15.113 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
2023-11-01 18:30:15.610 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:15.610 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
2023-11-01 18:30:16.531 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:16.531 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:16.532 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:16.532 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature: 304402201af577adfc37fb23df398ec7989b1717f761d76d01edaf5d5d40df2393111f7b02202c9ef0b677b3251fb6720033b2cfc5b0884b08324be7041899c069402f3b5963, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:30:16.532 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:16.605 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
2023-11-01 18:30:16.606 DEBUG [lightning::ln::channelmanager:6973] Received channel_update ChannelUpdate { signature:<PHONE_NUMBER>39c73470f975361f2868b35185626dd4d1f3c402c6ffbb732f5f679bf54ac602200cc0fad1be7e279a922c8b290ffdf9114a911083ef55d3dde5f8d8a07101e120, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id:<PHONE_NUMBER>65077249, timestamp:<PHONE_NUMBER>, flags: 0, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 140001000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93.
2023-11-01 18:30:16.606 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
2023-11-01 18:30:19.930 TRACE [lightning_invoice::utils:537] Creating invoice with payment hash 88240607c734579e61eee8313534c42924b663567f8ad1abd6734720459d596e
2023-11-01 18:30:19.930 TRACE [lightning_invoice::utils:627] Considering 2 channels for invoice route hints
2023-11-01 18:30:19.930 TRACE [lightning_invoice::utils:630] Ignoring channel 85b58973126c059974490a6dcbfc02fbad9343a0f1b780759800ac9e6432eabe for invoice route hints
2023-11-01 18:30:19.930 TRACE [lightning_invoice::utils:661] Channel with connected peer exists for invoice route hints
2023-11-01 18:30:19.931 TRACE [lightning_invoice::utils:733] Including channel 63b84b963eb09329516c1dc0c5bafee9a079550e4bc99b293b9adab7e02e4c93 in invoice route hints
2023-11-01 18:30:19.951 INFO  [mutiny_core::node:931] SUCCESS: generated invoice: lnbc899990n1pj59xfmdqqnp4qwmp4snzc9su6380ya9au4wthstesaq2yye0ffhrul5dvget7q52xpp53qjqvp78x3teuc0waqcn2dxy9yjtvc6k079dr27kwdrjq3vat9hqsp5g5jjcat0hxgmz6rr6ztl06wrs64ww280v2k625pgyzh0kkrzymes9qyysgqcqzptxqrrssrzjqwh05slmksqfkgdyz2wst9fewjmah2amldg3jg2pqzqgvr723mslp2l4eew5p354vsqqqqlgqqqqqzsqygmhh63sv7u2psvghf0c5zckgfsas2d2gvw05f9lj54ed6sv058hrh7fu9eydgghhe34asxqv0dflz239d2gpdsa3ppp3xwvjrpulvn8qqrpc9wh
2023-11-01 18:30:20.142 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/88240607c734579e61eee8313534c42924b663567f8ad1abd6734720459d596e_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:20.964 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/88240607c734579e61eee8313534c42924b663567f8ad1abd6734720459d596e_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:21.965 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/88240607c734579e61eee8313534c42924b663567f8ad1abd6734720459d596e_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:22.966 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/88240607c734579e61eee8313534c42924b663567f8ad1abd6734720459d596e_f210abf8-af61-4034-a4fc-e6647a8d0abb
2023-11-01 18:30:23.968 TRACE [mutiny_core::ldkstorage:378] Trace: checking payment key: payment_inbound/

mutiny-logs 4.txt

Post a file? SMH…

deleted the giant comments, will just use the file haha

Opened a new channel but two prior transfers not showing. The balance that is showing doesn’t allow transfers. Idk

That just means you need to wait for the force close to be swept, can take a few days sometimes.

They swept somewhere

mutiny-logs 5.txt

Are my sats just gone for good?

No, we'll work on it.

I see a couple revoked transactions, which means all of the funds went to the LSP due to bugs. Do you have the node id? It's in settings > admin, at the top. We'll get in touch with the LSP to see their point of view.

03b61ac262c161cd44ef274bde55cbbc1798740a2132f4a6e3e7e8d6232bf028a3

Is that all you needed?

No, I do not believe so. I purposefully used safari to set the PWA since I do not use that browser.
The problem didn’t appear until the 25k sat transfer from Cashapp. That one hung up until the channel closed and was eventually sent back to the cashapp sender.
The 69k sat transferred from strike said it went through on their end but went into the either.

Did you have a password set for your wallet?

No

Node Id: 03b61ac262c161cd44ef274bde55cbbc1798740a2132f4a6e3e7e8d6232bf028a3
channel force close txs:
https://mempool.space/tx/b620dcebbe932f42df854da443eed569b1134200297c21c991d9df547a23603d
https://mempool.space/tx/f7166a10701839312e876ff577699239c426c3aa9b9ba44d84fb83b0811695c5

Where did it go?

The funds were swept by the LSP, sometime next week they will send it back

Provide an address.

lnbc1pj4qxmjdqdgdshx6pqg9c8qpp537keyadje75pf67shftsxktp9d2rf4dafwh4nft222k33chu7pussp5y0y5d0k8u6z6pyccu5s9tk40nudx67gsevu8kqsm5ch2kyj57zws9qrsgqcqpcxqy8ayqrzjqv06k0m23t593pngl0jt7n9wznp64fqngvctz7vts8nq4tukvtljqzx7uuqqrdqqqcqqqqqqqqqqqqqq9grzjqtsjy9p55gdceevp36fvdmrkxqvzfhy8ak2tgc5zgtjtra9xlaz97zetkyqq25gqqqqqqqqqqqqqqqqq9gh22danjddy7dsgj97qsm9vhk0cjq6qrd0vf7qjqxzcsl64hjhwfz6f392yahxe05u0845ke78yv256e9q2fpx5tzypdrvkhxmyl4weqq7zfhl6

Need an onchain address, the invoice will expire

On chain:
bc1qstc5ajmp2w5uegxy97z3dak7g9kmvj5sn87hr0