search

MutinyWallet / mutiny-node

SDK behind Mutiny Wallet
https://mutinywallet.com
MIT License
189 stars 35 forks source link

Invoice expired but it wasn't #552

Closed TonyGiorgio closed 1 year ago

TonyGiorgio commented 1 year ago 
2023-06-01 22:07:33.171 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:34.179 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:34.598 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:34.599 DEBUG [lightning::ln::peer_handler:1293] Error handling message from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a; ignoring: Couldn't find channel for update
2023-06-01 22:07:34.599 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:34.602 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:34.603 TRACE [lightning::ln::peer_handler:1381] Received message UpdateAddHTLC(UpdateAddHTLC { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], htlc_id: 0, amount_msat: 7500000, payment_hash: PaymentHash([51, 1, 70, 27, 119, 151, 139, 122, 138, 255, 78, 97, 43, 193, 209, 221, 125, 240, 4, 250, 197, 145, 62, 197, 129, 32, 224, 16, 50, 224, 152, 168]), cltv_expiry: 120580, onion_routing_packet: OnionPacket version 0 with hmac [130, 215, 191, 95, 36, 59, 237, 244, 166, 16, 67, 250, 133, 30, 187, 219, 182, 12, 208, 206, 119, 96, 42, 177, 229, 73, 146, 151, 50, 37, 233, 221] }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:34.612 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:34.613 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:07:34.615 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:07:34.764 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:07:34.764 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:34.764 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:07:34.764 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:34.871 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:34.872 TRACE [lightning::ln::peer_handler:1381] Received message CommitmentSigned(CommitmentSigned { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], signature: 304402204f28b19e4c862dda45895913b70247c846cb98c10611a4d7d4c1ffe2ec98670102200683fd7d06c841c4d09193bd642af7acc69e80f5566e16d11859293c2a265f5e, htlc_signatures: [304402203e0193a073486b85c1843505a6f0594289818fc18bdbdb1d6ecfb656de0ac275022000b92f338913a16ef9b07351b36fe99c5d552868d2f32e28296e15142f68acb6] }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:34.883 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710654 (really 1 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for us, generated by remote with fee 253...
2023-06-01 22:07:34.883 TRACE [lightning::ln::channel:1580]    ...including inbound RemoteAnnounced HTLC 0 (hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8) with value 7500000
2023-06-01 22:07:34.883 TRACE [lightning::ln::channel:1685]    ...including to_remote output with value 100860
2023-06-01 22:07:34.884 TRACE [lightning::ln::channel:3094] Checking commitment tx signature 4f28b19e4c862dda45895913b70247c846cb98c10611a4d7d4c1ffe2ec9867010683fd7d06c841c4d09193bd642af7acc69e80f5566e16d11859293c2a265f5e by key 031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e against tx 0200000001e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdfff010000000081abf680024c1d00000000000022002045fa29e69b2f6e38916ff896725801608677e0ec5b22a624ec29f2cf3a863117fc890100000000001600149c86a02691b8b145242ee0bcca5fd3322ea31ae9d7abcb20 (sighash 0079059904c6d3e9007fc7e115a27319aad0b079d2df92798535aa6582ba8272) with redeemscript 4752210276a7d29903deb55d13c9cf1772acb538cb388b4721accc403549b74ecb367e6921031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e52ae in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.887 TRACE [lightning::ln::channel:3165] Checking HTLC tx signature 3e0193a073486b85c1843505a6f0594289818fc18bdbdb1d6ecfb656de0ac27500b92f338913a16ef9b07351b36fe99c5d552868d2f32e28296e15142f68acb6 by key 031a4454a2f27a2869fbd1152286c3342b6c91a189c2cd0e7e576198f5db454fa8 against tx 02000000014ba4ebab38198b043d37c7e9552cc7bf3d301b53b0e3742194ec2b2351b39c7a000000000000000000019b1c00000000000022002032129687cdd88052d6799aa487bf1e64b4529ac5f7bb748d22b7283a5cc6f60e00000000 (sighash d7c248aaeee4385008b876f83f102b8cf5de1cf8d235859537ecaacf88550495) with redeemscript 8b76a9143f4199cda2d7ad754acd63e4563a54d9e85848218763ac6721031a4454a2f27a2869fbd1152286c3342b6c91a189c2cd0e7e576198f5db454fa87c8201208763a91479419dd6d16dde7901cdc42b57fb8f576d37564a88527c210363e6b030e5e919de380b3261302f30ddfc87a6d24995f37fcdb5b4d5d5c19e7052ae67750304d701b175ac6868 in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:07:34.889 TRACE [lightning::ln::channel:3210] Updating HTLC 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8 to AwaitingRemoteRevokeToAnnounce due to commitment_signed in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:07:34.889 TRACE [lightning::ln::channel:5865] Updating HTLC state for a newly-sent commitment_signed...
2023-06-01 22:07:34.889 TRACE [lightning::ln::channel:5874]  ...promoting inbound AwaitingRemoteRevokeToAnnounce 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8 to AwaitingAnnouncedRemoteRevoke
2023-06-01 22:07:34.892 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710654 (really 1 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for remote, generated by us with fee 253...
2023-06-01 22:07:34.892 TRACE [lightning::ln::channel:1580]    ...including inbound AwaitingAnnouncedRemoteRevoke HTLC 0 (hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8) with value 7500000
2023-06-01 22:07:34.892 TRACE [lightning::ln::channel:1679]    ...including to_remote output with value 100860
2023-06-01 22:07:34.892 DEBUG [lightning::ln::channel:3287] Received valid commitment_signed from peer in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, updating HTLC state and responding with our own commitment_signed and a revoke_and_ack.
2023-06-01 22:07:34.894 TRACE [lightning::chain::chainmonitor:706] Updating ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.894 INFO  [lightning::chain::channelmonitor:2328] Applying update to monitor e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, bringing update_id from 0 to 1 with 2 changes.
2023-06-01 22:07:34.894 TRACE [lightning::chain::channelmonitor:2359] Updating ChannelMonitor with latest holder commitment transaction info
2023-06-01 22:07:34.894 TRACE [lightning::chain::channelmonitor:2368] Updating ChannelMonitor with latest counterparty commitment transaction info
2023-06-01 22:07:34.895 TRACE [lightning::chain::channelmonitor:2142] Tracking new counterparty commitment transaction with txid f283f43504b0b12fc2315be5fddaf0de6015ce8cac0bf5c721b392105725dbd0 at commitment number 281474976710654 with 1 HTLC outputs
2023-06-01 22:07:34.896 DEBUG [lightning::chain::chainmonitor:726] Persistence of ChannelMonitorUpdate for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:07:34.897 TRACE [lightning::ln::channel:4009] Regenerated latest commitment update in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with 0 update_adds, 0 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
2023-06-01 22:07:34.900 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710654 (really 1 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for remote, generated by us with fee 253...
2023-06-01 22:07:34.900 TRACE [lightning::ln::channel:1580]    ...including inbound AwaitingAnnouncedRemoteRevoke HTLC 0 (hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8) with value 7500000
2023-06-01 22:07:34.900 TRACE [lightning::ln::channel:1679]    ...including to_remote output with value 100860
2023-06-01 22:07:34.905 TRACE [lightning::ln::channel:5968] Signed remote commitment tx 0200000001e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdfff010000000081abf680024c1d0000000000002200203207f964d721edc44ae40e9e4d606aa2921fc22c86abe2d719df550005f27d53fc89010000000000220020730ad9743bfdb3037bb10a5c8898154e19486a92caeffc4fc2c34e1c2f69f0e7d7abcb20 (txid f283f43504b0b12fc2315be5fddaf0de6015ce8cac0bf5c721b392105725dbd0) with redeemscript 4752210276a7d29903deb55d13c9cf1772acb538cb388b4721accc403549b74ecb367e6921031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e52ae -> 0c8b8092e783ef1695d086972ed50762bc2d0a8871a4b0825bdadaf7cd419e7f4bb4105aaa58bbba499f125385ebb912aadebf9b7a938101b7f23de6980e3f33 in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.905 TRACE [lightning::ln::channel:5974] Signed remote HTLC tx 0200000001d0db25571092b321c7f50bac8cce1560def0dafde55b31c22fb1b00435f483f200000000000000000001a51c000000000000220020730ad9743bfdb3037bb10a5c8898154e19486a92caeffc4fc2c34e1c2f69f0e704d70100 with redeemscript 8576a91463126aab8cbf47b4e58b21578a8f4e93bc49a5d88763ac6721032ec536b4c13ea298f5c61a1e2823ae8ff44653a9be5163ee6627d41c8a04e8877c820120876475527c2103e0b7243cec276a5d78af74dedd776ddba99dd354bcc4b33c78c82c3c250ce36d52ae67a91479419dd6d16dde7901cdc42b57fb8f576d37564a88ac6868 with pubkey 03e0b7243cec276a5d78af74dedd776ddba99dd354bcc4b33c78c82c3c250ce36d -> 7d292a1841377ddfd6b3c080cbc4325932f17500d02853d76f1d7cba05368bb016fc7c91a73d572bdcbb0e9b7a3ba7915deb3ed970e3125a43594760774b276e in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.905 DEBUG [lightning::ln::channel:3899] Restored monitor updating in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulting in a commitment update and an RAA, with RAA first
2023-06-01 22:07:34.905 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with an RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:07:34.905 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:34.905 DEBUG [lightning::ln::peer_handler:1783] Handling SendRevokeAndACK event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.905 TRACE [lightning::ln::peer_handler:1071] Enqueueing message RevokeAndACK { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], per_commitment_secret: [243, 36, 134, 69, 187, 108, 169, 96, 136, 60, 141, 84, 116, 105, 195, 123, 244, 122, 172, 59, 35, 247, 194, 31, 176, 132, 155, 19, 92, 218, 101, 36], next_per_commitment_point: PublicKey(e7fb00dd683dca90b5face242b40b50af59c59ec1d07775eb5477d487b38239db90c37782a6bd14e1280245438d62ea3360f5df315948b48f2203a66844b9685) } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:34.905 DEBUG [lightning::ln::peer_handler:1758] Handling UpdateHTLCs event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a with 0 adds, 0 fulfills, 0 fails for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:34.905 TRACE [lightning::ln::peer_handler:1071] Enqueueing message CommitmentSigned { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], signature: 304402200c8b8092e783ef1695d086972ed50762bc2d0a8871a4b0825bdadaf7cd419e7f02204bb4105aaa58bbba499f125385ebb912aadebf9b7a938101b7f23de6980e3f33, htlc_signatures: [304402207d292a1841377ddfd6b3c080cbc4325932f17500d02853d76f1d7cba05368bb0022016fc7c91a73d572bdcbb0e9b7a3ba7915deb3ed970e3125a43594760774b276e] } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:34.905 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:34.905 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:34.907 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:07:34.908 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:07:34.908 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:34.908 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:35.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:35.304 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:35.305 TRACE [lightning::ln::peer_handler:1381] Received message RevokeAndACK(RevokeAndACK { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], per_commitment_secret: [171, 187, 230, 115, 180, 187, 105, 229, 84, 231, 50, 94, 166, 219, 85, 61, 66, 41, 19, 191, 88, 5, 30, 22, 163, 170, 249, 81, 116, 206, 193, 59], next_per_commitment_point: PublicKey(e4a4b7229dfce155ff3c20e551d656cdd798e54089b48e7c1d3eafe5fa01c65ef1c51b1156833fb5956b39acac90b67e5886af3c4837625f405c234d2ccf3bac) }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:35.305 TRACE [lightning::ln::channel:3485] Updating HTLCs on receipt of RAA in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe...
2023-06-01 22:07:35.305 TRACE [lightning::ln::channel:3553]  ...promoting inbound AwaitingAnnouncedRemoteRevoke 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8 to Committed
2023-06-01 22:07:35.305 DEBUG [lightning::ln::channel:3646] Received a valid revoke_and_ack for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no reply necessary.
2023-06-01 22:07:35.306 TRACE [lightning::chain::chainmonitor:706] Updating ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:35.306 INFO  [lightning::chain::channelmonitor:2328] Applying update to monitor e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, bringing update_id from 1 to 2 with 1 changes.
2023-06-01 22:07:35.307 TRACE [lightning::chain::channelmonitor:2376] Updating ChannelMonitor with commitment secret
2023-06-01 22:07:35.308 DEBUG [lightning::chain::chainmonitor:726] Persistence of ChannelMonitorUpdate for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:07:35.308 DEBUG [lightning::ln::channel:3899] Restored monitor updating in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulting in no commitment update and no RAA, with RAA first
2023-06-01 22:07:35.308 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no RAA, no commitment update, 1 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:07:35.309 TRACE [lightning::ln::channelmanager:2627] Generating channel update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:07:35.310 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:35.311 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:07:35.312 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:07:35.312 DEBUG [mutiny_core::event:427] EVENT: PendingHTLCsForwardable: 100ms, processing...
2023-06-01 22:07:35.420 TRACE [lightning::ln::inbound_payment:380] Failing HTLC with payment_hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8: expired payment
2023-06-01 22:07:35.420 TRACE [lightning::ln::channelmanager:3604] Failing new HTLC with payment_hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8 as payment verification failed
2023-06-01 22:07:35.423 TRACE [lightning::ln::channelmanager:4103] Failing HTLC with payment_hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8 backwards from us with HTLC error code 16399
2023-06-01 22:07:35.424 DEBUG [mutiny_core::event:424] EVENT: HTLCHandlingFailed, ignored
2023-06-01 22:07:35.425 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:07:35.427 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:07:35.844 TRACE [mutiny_core::background:656] Calling PeerManager's timer_tick_occurred
2023-06-01 22:07:35.844 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:35.844 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:35.844 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:36.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:36.197 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:36.197 TRACE [lightning::ln::peer_handler:1381] Received message Pong(Pong { byteslen: 0 }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:36.197 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:37.183 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:38.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:39.182 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:39.789 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:07:39.789 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:39.790 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:07:39.790 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:40.179 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:41.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:42.177 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:43.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:44.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:44.811 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:07:44.812 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:44.812 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:07:44.812 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:44.948 TRACE [mutiny_core::background:656] Persisting scorer
2023-06-01 22:07:44.948 TRACE [mutiny_core::background:656] Rebroadcasting monitor's pending claims
2023-06-01 22:07:45.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:45.988 TRACE [mutiny_core::background:656] Calling PeerManager's timer_tick_occurred
2023-06-01 22:07:45.988 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:45.988 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:07:45.988 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:07:46.178 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:46.308 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:07:46.308 TRACE [lightning::ln::peer_handler:1381] Received message Pong(Pong { byteslen: 0 }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:07:46.308 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:07:47.179 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: payment_inbound/3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8_6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:07:48.182 TRACE [mutiny_core::ldkstorage:244] Trace: checking payment key: 
...
...
2023-06-01 22:11:29.964 TRACE [mutiny_core::background:656] Calling PeerManager's timer_tick_occurred
2023-06-01 22:11:29.964 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:29.964 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:29.965 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:30.324 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:30.324 TRACE [lightning::ln::peer_handler:1381] Received message Pong(Pong { byteslen: 0 }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:30.324 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:30.556 INFO  [mutiny_core::esplora:220] Starting transaction sync.
2023-06-01 22:11:30.953 TRACE [lightning::ln::channelmanager:6076] New best block: 000002b42bfb6b02d8ebb091bfc455e539ccefac6633c3e21bcc1e8719a398f5 at height 120544
2023-06-01 22:11:30.953 TRACE [lightning::ln::channel:5534] Creating an announcement_signatures message for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:30.953 TRACE [lightning::ln::channel:5538] Ignore : Channel is not available for public announcements
2023-06-01 22:11:30.954 DEBUG [lightning::chain::chainmonitor:612] New best block 000002b42bfb6b02d8ebb091bfc455e539ccefac6633c3e21bcc1e8719a398f5 at height 120544 provided via best_block_updated
2023-06-01 22:11:30.954 TRACE [lightning::chain::channelmonitor:3157] Processing 0 matched transactions for block at height 120544.
2023-06-01 22:11:30.954 DEBUG [lightning::chain::onchaintx:707] Updating claims view at height 120544 with 0 claim requests
2023-06-01 22:11:30.954 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 120544 with 0 matched transactions in block 120544
2023-06-01 22:11:30.954 TRACE [lightning::chain::onchaintx:955] Bumping 0 candidates
2023-06-01 22:11:30.954 TRACE [lightning::chain::chainmonitor:306] Syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:30.955 TRACE [lightning::chain::chainmonitor:309] Finished syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:30.955 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:30.956 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:31.110 INFO  [mutiny_core::esplora:316] Finished transaction sync.
2023-06-01 22:11:31.220 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:11:31.220 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:31.220 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:11:31.220 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:33.473 INFO  [mutiny_core::nodemanager:1072] We are synced!
2023-06-01 22:11:36.252 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:11:36.252 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:36.252 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:11:36.253 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:40.132 TRACE [mutiny_core::background:656] Calling PeerManager's timer_tick_occurred
2023-06-01 22:11:40.132 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:40.132 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:40.132 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:40.464 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:40.464 TRACE [lightning::ln::peer_handler:1381] Received message Pong(Pong { byteslen: 0 }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:40.464 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:41.277 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:11:41.277 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:41.277 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:11:41.277 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:41.684 DEBUG [mutiny_core::nodemanager:1729] fetching new bitcoin price
2023-06-01 22:11:48.975 DEBUG [mutiny_core::gossip:63] Got network graph, getting scorer...
2023-06-01 22:11:48.975 DEBUG [mutiny_core::gossip:133] Previous gossip sync timestamp: 1685125800
2023-06-01 22:11:48.976 INFO  [mutiny_core::gossip:152] RGS URL: https://rgs.mutinynet.com/snapshot/1685125800
2023-06-01 22:11:49.203 TRACE [lightning_rapid_gossip_sync::processing:62] Processing RGS data...
2023-06-01 22:11:49.209 DEBUG [lightning_rapid_gossip_sync::processing:138] Processing RGS update from 1685125800 with 6 nodes, 20 channel announcements and 40 channel updates.
2023-06-01 22:11:49.211 TRACE [lightning_rapid_gossip_sync::processing:247] Done processing RGS data from 1685125800
2023-06-01 22:11:49.211 INFO  [mutiny_core::gossip:202] RGS sync result: 1685125800
2023-06-01 22:11:49.524 INFO  [mutiny_core::node:190] initializing a new node: 6f7a09cf-f837-4201-846c-538e0227fc3f
2023-06-01 22:11:49.634 INFO  [lightning::ln::channelmanager:7548] Successfully loaded channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:49.637 INFO  [mutiny_core::node:291] creating lsp client
2023-06-01 22:11:49.639 TRACE [lightning::chain::chainmonitor:658] Got new ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:49.642 INFO  [lightning::chain::chainmonitor:672] Persistence of new ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:11:49.643 INFO  [mutiny_core::socket:141] setting up multi websocket descriptor
2023-06-01 22:11:49.643 INFO  [mutiny_core::nodemanager:526] inserting updated nodes
2023-06-01 22:11:49.643 INFO  [mutiny_core::nodemanager:532] inserted updated nodes
2023-06-01 22:11:49.710 TRACE [mutiny_core::background:656] Calling ChannelManager's timer_tick_occurred on startup
2023-06-01 22:11:49.711 TRACE [mutiny_core::fees:130] Got fee rate from saved cache!
2023-06-01 22:11:49.711 TRACE [mutiny_core::background:656] Rebroadcasting monitor's pending claims on startup
2023-06-01 22:11:49.719 DEBUG [mutiny_core::event:427] EVENT: PendingHTLCsForwardable: 2s, processing...
2023-06-01 22:11:49.720 TRACE [mutiny_core::node:1256] setting up multi proxy socket
2023-06-01 22:11:49.749 DEBUG [mutiny_core::nodemanager:1729] fetching new bitcoin price
2023-06-01 22:11:49.800 INFO  [mutiny_core::nodemanager:703] Updated fee estimates!
2023-06-01 22:11:49.801 INFO  [mutiny_core::esplora:220] Starting transaction sync.
2023-06-01 22:11:50.203 TRACE [lightning::ln::channelmanager:6076] New best block: 00000174e22115ff7e6658162060f9b4e0514838265abb306663d108eeed588d at height 120545
2023-06-01 22:11:50.203 TRACE [lightning::ln::channel:5526] Cannot create an announcement_signatures as our peer is disconnected
2023-06-01 22:11:50.204 DEBUG [lightning::chain::chainmonitor:612] New best block 00000174e22115ff7e6658162060f9b4e0514838265abb306663d108eeed588d at height 120545 provided via best_block_updated
2023-06-01 22:11:50.208 TRACE [lightning::chain::channelmonitor:3157] Processing 0 matched transactions for block at height 120545.
2023-06-01 22:11:50.208 DEBUG [lightning::chain::onchaintx:707] Updating claims view at height 120545 with 0 claim requests
2023-06-01 22:11:50.209 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 120545 with 0 matched transactions in block 120545
2023-06-01 22:11:50.209 TRACE [lightning::chain::onchaintx:955] Bumping 0 candidates
2023-06-01 22:11:50.209 TRACE [lightning::chain::chainmonitor:306] Syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:50.211 TRACE [lightning::chain::chainmonitor:309] Finished syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:50.625 TRACE [lightning::ln::channelmanager:6057] 1 transactions included in block 00000001c84b3cb5e5069015f4a242ac57ebe6720e89659887b8e0831f7b4f29 at height 120538 provided
2023-06-01 22:11:50.625 TRACE [lightning::ln::channel:5526] Cannot create an announcement_signatures as our peer is disconnected
2023-06-01 22:11:50.636 DEBUG [lightning::chain::chainmonitor:596] 1 provided transactions confirmed at height 120538 in block 00000001c84b3cb5e5069015f4a242ac57ebe6720e89659887b8e0831f7b4f29
2023-06-01 22:11:50.637 TRACE [lightning::chain::channelmonitor:3157] Processing 0 matched transactions for block at height 120538.
2023-06-01 22:11:50.637 DEBUG [lightning::chain::onchaintx:707] Updating claims view at height 120545 with 0 claim requests
2023-06-01 22:11:50.637 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 120545 with 0 matched transactions in block 120538
2023-06-01 22:11:50.637 TRACE [lightning::chain::onchaintx:955] Bumping 0 candidates
2023-06-01 22:11:50.637 TRACE [lightning::chain::chainmonitor:306] Syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:50.638 TRACE [lightning::chain::chainmonitor:309] Finished syncing Channel Monitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:50.638 INFO  [mutiny_core::esplora:316] Finished transaction sync.
2023-06-01 22:11:50.725 DEBUG [mutiny_core::proxy:73] connected to ws: wss://p.mutinywallet.com
2023-06-01 22:11:50.726 TRACE [mutiny_core::socket:178] connecting new multi websocket descriptor
2023-06-01 22:11:50.726 TRACE [mutiny_core::socket:240] spawning multi socket connection reader
2023-06-01 22:11:50.726 TRACE [mutiny_core::socket:285] spawning multi socket channel reader
2023-06-01 22:11:50.728 DEBUG [mutiny_core::node:1530] making connection to peer: PubkeyConnectionInfo { pubkey: PublicKey(8a939324d63d7f395756850f25c58cf5bdca310d52c4d2a8311ea64debc8ab66fb0eb323565f205fbc8d4df4ea103e333b7f63adeda9d9744b0d357e26b2c7bb), connection_type: Tcp("45.33.17.66:39735"), original_connection_string: "0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a@45.33.17.66:39735" }
2023-06-01 22:11:51.722 TRACE [lightning::ln::channelmanager:3402] Failing HTLC back to channel with short id 24065011014369283 (backward HTLC ID 0) after delay
2023-06-01 22:11:51.722 TRACE [lightning::ln::channel:2094] Placing failure for HTLC ID 0 in holding cell in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:11:51.732 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:51.736 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:51.739 DEBUG [mutiny_core::proxy:73] connected to ws: wss://p.mutinywallet.com
2023-06-01 22:11:51.742 DEBUG [mutiny_core::node:1565] connected to peer: PubkeyConnectionInfo { pubkey: PublicKey(8a939324d63d7f395756850f25c58cf5bdca310d52c4d2a8311ea64debc8ab66fb0eb323565f205fbc8d4df4ea103e333b7f63adeda9d9744b0d357e26b2c7bb), connection_type: Tcp("45.33.17.66:39735"), original_connection_string: "0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a@45.33.17.66:39735" }
2023-06-01 22:11:51.742 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.742 TRACE [mutiny_core::node:1568] sent 50 to node: 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.742 TRACE [mutiny_core::socket:470] scheduling descriptor reader
2023-06-01 22:11:51.742 TRACE [mutiny_core::node:1291] auto connected lsp: 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.743 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:51.816 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:51.847 DEBUG [lightning::ln::peer_handler:1192] Finished noise handshake for connection with 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.847 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Init { features: [34, 81, 10, 8, 0, 160, 8], remote_network_address: Some(IPv4 { addr: [45, 33, 17, 66], port: 39735 }) } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.847 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:51.848 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.848 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.848 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:51.848 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:51.922 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:51.923 INFO  [lightning::ln::peer_handler:1334] Received peer Init message from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: supported, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsZeroFeeHtlcTx: not supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: supported
2023-06-01 22:11:51.923 DEBUG [lightning::ln::channelmanager:6563] Generating channel_reestablish events for 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.923 TRACE [lightning::ln::channel:5656] Enough info to generate a Data Loss Protect with per_commitment_secret abbbe673b4bb69e554e7325ea6db553d422913bf58051e16a3aaf95174cec13b for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.923 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:51.923 DEBUG [lightning::ln::peer_handler:1801] Handling SendChannelReestablish event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.924 TRACE [lightning::ln::peer_handler:1071] Enqueueing message ChannelReestablish { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], next_local_commitment_number: 2, next_remote_commitment_number: 1, data_loss_protect: Present(DataLossProtect { your_last_per_commitment_secret: [171, 187, 230, 115, 180, 187, 105, 229, 84, 231, 50, 94, 166, 219, 85, 61, 66, 41, 19, 191, 88, 5, 30, 22, 163, 170, 249, 81, 116, 206, 193, 59], my_current_per_commitment_point: PublicKey(02020202020202020202020202020202020202020202020202020202020202ffcee50f772e0a9972250d4b61b3e5beb95de897c73b4ed1cc35ed013accf1c840) }) } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.924 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.924 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:51.925 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:51.925 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:51.981 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:51.981 TRACE [lightning::ln::peer_handler:1381] Received message ChannelReestablish(ChannelReestablish { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], next_local_commitment_number: 2, next_remote_commitment_number: 1, data_loss_protect: Present(DataLossProtect { your_last_per_commitment_secret: [243, 36, 134, 69, 187, 108, 169, 96, 136, 60, 141, 84, 116, 105, 195, 123, 244, 122, 172, 59, 35, 247, 194, 31, 176, 132, 155, 19, 92, 218, 101, 36], my_current_per_commitment_point: PublicKey(e7fb00dd683dca90b5face242b40b50af59c59ec1d07775eb5477d487b38239db90c37782a6bd14e1280245438d62ea3360f5df315948b48f2203a66844b9685) }) }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.982 TRACE [lightning::ln::channel:5534] Creating an announcement_signatures message for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.982 TRACE [lightning::ln::channel:5538] Ignore : Channel is not available for public announcements
2023-06-01 22:11:51.982 DEBUG [lightning::ln::channel:4163] Reconnected channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no loss
2023-06-01 22:11:51.982 TRACE [lightning::ln::channelmanager:2618] Attempting to generate channel update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.982 TRACE [lightning::ln::channelmanager:2627] Generating channel update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.983 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:11:51.983 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:51.984 TRACE [lightning::ln::channel:3309] Freeing holding cell with 1 HTLC updates in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.984 TRACE [lightning::ln::channel:2102] Failing HTLC ID 0 back with a update_fail_htlc message in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:11:51.984 TRACE [lightning::ln::channel:5865] Updating HTLC state for a newly-sent commitment_signed...
2023-06-01 22:11:51.987 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710653 (really 2 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for remote, generated by us with fee 253...
2023-06-01 22:11:51.987 TRACE [lightning::ln::channel:1583]    ...not including inbound HTLC 0 (hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8) with value 7500000 due to state (LocalRemoved)
2023-06-01 22:11:51.987 TRACE [lightning::ln::channel:1679]    ...including to_remote output with value 108403
2023-06-01 22:11:51.988 DEBUG [lightning::ln::channel:3401] Freeing holding cell in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulted in 0 HTLCs added, 0 HTLCs fulfilled, and 1 HTLCs failed.
2023-06-01 22:11:51.990 TRACE [lightning::chain::chainmonitor:706] Updating ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.990 INFO  [lightning::chain::channelmonitor:2328] Applying update to monitor e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, bringing update_id from 2 to 3 with 1 changes.
2023-06-01 22:11:51.990 TRACE [lightning::chain::channelmonitor:2368] Updating ChannelMonitor with latest counterparty commitment transaction info
2023-06-01 22:11:51.990 TRACE [lightning::chain::channelmonitor:2142] Tracking new counterparty commitment transaction with txid 6a38061ded8e0e4582f3f99022b77acd186a5fdb35ef6661dab7f0caf412466c at commitment number 281474976710653 with 0 HTLC outputs
2023-06-01 22:11:51.991 DEBUG [lightning::chain::chainmonitor:726] Persistence of ChannelMonitorUpdate for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:11:51.992 TRACE [lightning::ln::channel:5534] Creating an announcement_signatures message for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.992 TRACE [lightning::ln::channel:5538] Ignore : Channel is not available for public announcements
2023-06-01 22:11:51.992 TRACE [lightning::ln::channel:4009] Regenerated latest commitment update in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with 0 update_adds, 0 update_fulfills, 1 update_fails, and 0 update_fail_malformeds
2023-06-01 22:11:51.996 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710653 (really 2 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for remote, generated by us with fee 253...
2023-06-01 22:11:51.996 TRACE [lightning::ln::channel:1583]    ...not including inbound HTLC 0 (hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8) with value 7500000 due to state (LocalRemoved)
2023-06-01 22:11:51.996 TRACE [lightning::ln::channel:1679]    ...including to_remote output with value 108403
2023-06-01 22:11:51.998 TRACE [lightning::ln::channel:5968] Signed remote commitment tx 0200000001e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdfff010000000081abf6800173a70100000000002200203b0e41c763696387770401bb1987bf5425394f39726c62511aa13952f34351bad4abcb20 (txid 6a38061ded8e0e4582f3f99022b77acd186a5fdb35ef6661dab7f0caf412466c) with redeemscript 4752210276a7d29903deb55d13c9cf1772acb538cb388b4721accc403549b74ecb367e6921031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e52ae -> 3d686a3d3fab904d2b42c511545163a744f4fd2e5b777fcad74ac84b69bb4d397bebda6148252a7b06db33ba76927ee7df3c2ddaf4fe5635634f7efa66c04321 in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.998 DEBUG [lightning::ln::channel:3899] Restored monitor updating in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulting in a commitment update and no RAA, with RAA first
2023-06-01 22:11:51.998 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:11:51.999 TRACE [lightning::ln::peer_handler:1845] Handling SendChannelUpdate event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a for channel 132532932588929025
2023-06-01 22:11:51.999 DEBUG [lightning::ln::peer_handler:1758] Handling UpdateHTLCs event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a with 0 adds, 0 fulfills, 1 fails for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:51.999 TRACE [lightning::ln::peer_handler:1071] Enqueueing message UpdateFailHTLC { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], htlc_id: 0, reason: OnionErrorPacket { data: [11, 220, 120, 87, 254, 215, 10, 42, 40, 185, 48, 249, 132, 91, 210, 223, 41, 100, 56, 11, 107, 93, 191, 143, 201, 239, 145, 37, 43, 206, 102, 118, 196, 90, 60, 133, 113, 151, 161, 80, 8, 123, 20, 244, 53, 241, 61, 178, 243, 49, 46, 66, 187, 70, 148, 175, 187, 237, 151, 92, 207, 250, 183, 76, 205, 193, 10, 187, 86, 80, 159, 230, 176, 118, 231, 220, 241, 97, 22, 187, 227, 7, 70, 130, 123, 17, 94, 200, 117, 83, 121, 164, 112, 197, 57, 180, 197, 75, 28, 99, 150, 245, 155, 145, 53, 158, 78, 219, 135, 180, 79, 111, 225, 254, 190, 112, 137, 224, 11, 184, 232, 211, 219, 131, 155, 162, 153, 228, 171, 148, 3, 86, 81, 34, 138, 42, 151, 250, 13, 70, 218, 65, 6, 253, 35, 222, 135, 112, 160, 34, 141, 19, 104, 147, 238, 89, 154, 54, 229, 225, 213, 164, 84, 168, 114, 90, 82, 241, 41, 69, 199, 91, 199, 221, 212, 24, 115, 59, 39, 253, 113, 28, 217, 185, 234, 181, 29, 136, 132, 168, 88, 208, 56, 203, 141, 141, 207, 158, 247, 79, 123, 239, 195, 80, 173, 162, 99, 161, 125, 10, 105, 202, 255, 20, 185, 139, 52, 56, 166, 108, 71, 175, 201, 174, 123, 87, 223, 198, 241, 13, 66, 169, 103, 19, 22, 7, 37, 110, 111, 47, 16, 98, 120, 130, 59, 4, 75, 240, 253, 196, 110, 224, 216, 35, 51, 113, 18, 83, 64, 190, 39, 221, 146, 229, 103, 169, 100, 126, 160, 35, 208, 15, 173, 132, 135, 71, 20, 238, 192, 151, 225, 109, 158, 231, 82, 94, 250, 31, 22, 153, 96, 57] } } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.999 TRACE [lightning::ln::peer_handler:1071] Enqueueing message CommitmentSigned { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], signature: 304402203d686a3d3fab904d2b42c511545163a744f4fd2e5b777fcad74ac84b69bb4d3902207bebda6148252a7b06db33ba76927ee7df3c2ddaf4fe5635634f7efa66c04321, htlc_signatures: [] } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:51.999 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.999 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.999 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:51.999 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:52.000 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:52.002 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:52.002 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:52.002 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:52.346 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:52.347 TRACE [lightning::ln::peer_handler:1381] Received message RevokeAndACK(RevokeAndACK { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], per_commitment_secret: [59, 38, 100, 53, 73, 87, 103, 200, 184, 197, 38, 89, 110, 141, 57, 36, 218, 25, 61, 115, 252, 202, 71, 104, 149, 117, 170, 141, 24, 231, 62, 79], next_per_commitment_point: PublicKey(a0713d4d2c51718da84fca32f7d7b4f8770840785b5abb0f12f0998bcad6da63f103a09aeee47d0b33cb632192a1860e3c4d7867af7e0f416a3be64080f1e208) }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:52.348 TRACE [lightning::ln::channel:3485] Updating HTLCs on receipt of RAA in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe...
2023-06-01 22:11:52.348 TRACE [lightning::ln::channel:3502]  ...removing inbound LocalRemoved 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8
2023-06-01 22:11:52.348 DEBUG [lightning::ln::channel:3646] Received a valid revoke_and_ack for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no reply necessary.
2023-06-01 22:11:52.348 TRACE [lightning::chain::chainmonitor:706] Updating ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.348 INFO  [lightning::chain::channelmonitor:2328] Applying update to monitor e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, bringing update_id from 3 to 4 with 1 changes.
2023-06-01 22:11:52.349 TRACE [lightning::chain::channelmonitor:2376] Updating ChannelMonitor with commitment secret
2023-06-01 22:11:52.350 DEBUG [lightning::chain::chainmonitor:726] Persistence of ChannelMonitorUpdate for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:11:52.351 TRACE [lightning::ln::channel:5534] Creating an announcement_signatures message for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.351 TRACE [lightning::ln::channel:5538] Ignore : Channel is not available for public announcements
2023-06-01 22:11:52.351 DEBUG [lightning::ln::channel:3899] Restored monitor updating in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulting in no commitment update and no RAA, with RAA first
2023-06-01 22:11:52.351 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:11:52.351 TRACE [lightning::ln::channelmanager:2627] Generating channel update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.352 TRACE [lightning::ln::peer_handler:1381] Received message CommitmentSigned(CommitmentSigned { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], signature: 304402203de021ec1a37d6551f40c0509b5344928a95f0055bad2860cd8268b2068bac8302203e53bcabf7b17473eb2acf197726683f59f7f604b7018cc18f64337b12b97bf1, htlc_signatures: [] }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:52.356 TRACE [lightning::ln::channel:1519] Building commitment transaction number 281474976710653 (really 2 xor 271216477449174) for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe for us, generated by remote with fee 253...
2023-06-01 22:11:52.356 TRACE [lightning::ln::channel:1685]    ...including to_remote output with value 108403
2023-06-01 22:11:52.356 TRACE [lightning::ln::channel:3094] Checking commitment tx signature 3de021ec1a37d6551f40c0509b5344928a95f0055bad2860cd8268b2068bac833e53bcabf7b17473eb2acf197726683f59f7f604b7018cc18f64337b12b97bf1 by key 031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e against tx 0200000001e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdfff010000000081abf6800173a70100000000001600149c86a02691b8b145242ee0bcca5fd3322ea31ae9d4abcb20 (sighash 4968692aba3ef624b83f4727df67fa24ecd84649f2aaabc6cb6b32cd9fe8ceb1) with redeemscript 4752210276a7d29903deb55d13c9cf1772acb538cb388b4721accc403549b74ecb367e6921031f40ed890286c82e463269d2247c81ce24eda1c70d5582260bc4c2be890acf0e52ae in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.358 DEBUG [lightning::ln::channel:3287] Received valid commitment_signed from peer in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, updating HTLC state and responding with a revoke_and_ack.
2023-06-01 22:11:52.358 TRACE [lightning::chain::chainmonitor:706] Updating ChannelMonitor for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.358 INFO  [lightning::chain::channelmonitor:2328] Applying update to monitor e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe, bringing update_id from 4 to 5 with 1 changes.
2023-06-01 22:11:52.358 TRACE [lightning::chain::channelmonitor:2359] Updating ChannelMonitor with latest holder commitment transaction info
2023-06-01 22:11:52.360 DEBUG [lightning::chain::chainmonitor:726] Persistence of ChannelMonitorUpdate for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe completed
2023-06-01 22:11:52.360 TRACE [lightning::ln::channel:5534] Creating an announcement_signatures message for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.360 TRACE [lightning::ln::channel:5538] Ignore : Channel is not available for public announcements
2023-06-01 22:11:52.361 DEBUG [lightning::ln::channel:3899] Restored monitor updating in channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe resulting in no commitment update and an RAA, with commitment first
2023-06-01 22:11:52.361 TRACE [lightning::ln::channelmanager:4408] Handling channel resumption for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe with an RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
2023-06-01 22:11:52.361 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:52.361 DEBUG [lightning::ln::peer_handler:1783] Handling SendRevokeAndACK event in peer_handler for node 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe
2023-06-01 22:11:52.361 TRACE [lightning::ln::peer_handler:1071] Enqueueing message RevokeAndACK { channel_id: [231, 245, 225, 216, 193, 144, 137, 181, 194, 33, 53, 173, 38, 111, 48, 28, 27, 113, 192, 144, 102, 76, 0, 157, 60, 120, 246, 192, 86, 175, 223, 254], per_commitment_secret: [247, 120, 78, 55, 113, 182, 178, 192, 34, 47, 227, 170, 135, 214, 21, 136, 213, 48, 234, 7, 133, 6, 21, 91, 134, 206, 182, 35, 87, 162, 48, 18], next_per_commitment_point: PublicKey(8f000c09d7d59d3143f71f510c9d63138b8d030156a19a4e017a2a4e763141faf0ebe15475eb91a598a76fd34abab8c3bfbb66d43cb4c547526db730a1de5ad3) } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:11:52.362 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:52.363 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:52.364 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:52.365 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:53.179 INFO  [mutiny_core::nodemanager:1072] We are synced!
2023-06-01 22:11:54.764 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:11:54.764 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:54.764 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:11:54.765 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:11:57.053 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:57.053 DEBUG [lightning::ln::channelmanager:5347] Received channel_update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:11:57.054 DEBUG [lightning::ln::peer_handler:1293] Error handling message from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a; ignoring: Couldn't find channel for update
2023-06-01 22:11:57.055 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:57.055 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:57.057 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:57.059 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:11:57.059 DEBUG [lightning::ln::channelmanager:5347] Received channel_update for channel e7f5e1d8c19089b5c22135ad266f301c1b71c090664c009d3c78f6c056afdffe.
2023-06-01 22:11:57.060 DEBUG [lightning::ln::peer_handler:1293] Error handling message from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a; ignoring: Couldn't find channel for update
2023-06-01 22:11:57.060 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:11:57.060 TRACE [mutiny_core::background:656] Persisting ChannelManager...
2023-06-01 22:11:57.060 TRACE [mutiny_core::background:656] Done persisting ChannelManager.
2023-06-01 22:11:59.804 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:11:59.804 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:11:59.804 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
2023-06-01 22:11:59.804 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:12:01.844 TRACE [mutiny_core::background:656] Calling PeerManager's timer_tick_occurred
2023-06-01 22:12:01.845 TRACE [lightning::ln::peer_handler:1071] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:12:01.845 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:12:01.845 TRACE [mutiny_core::proxy:98] sent data down websocket
2023-06-01 22:12:02.172 TRACE [mutiny_core::socket:487] received binary data from websocket
2023-06-01 22:12:02.173 TRACE [lightning::ln::peer_handler:1381] Received message Pong(Pong { byteslen: 0 }) from 0366abc8eb4da61e31a8d2c4520d31cabdf58cc5250f855657397f3dd62493938a
2023-06-01 22:12:02.173 TRACE [mutiny_core::socket:492] read event from the node
2023-06-01 22:12:04.828 TRACE [mutiny_core::socket:167] sending keep alive message to proxy
2023-06-01 22:12:04.828 TRACE [mutiny_core::proxy:87] initiating sending down websocket
2023-06-01 22:12:04.828 TRACE [mutiny_core::socket:172] initiated keep alive message to proxy
benthecarman commented 1 year ago

2023-06-01 22:07:35.420 TRACE [lightning::ln::inbound_payment:380] Failing HTLC with payment_hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8: expired payment

was this for an inbound payment?

TonyGiorgio commented 1 year ago

2023-06-01 22:07:35.420 TRACE [lightning::ln::inbound_payment:380] Failing HTLC with payment_hash 3301461b77978b7a8aff4e612bc1d1dd7df004fac5913ec58120e01032e098a8: expired payment

was this for an inbound payment?

yes

TonyGiorgio commented 1 year ago

I've gotten this quite a few times, typically when opening up one of the cloudflare PR instances and trying to receive: 

2023-06-08 17:17:30.997 TRACE [lightning::ln::channelmanager:3604] Failing new HTLC with payment_hash 5707e3dcf3270cf1bd8f324db15d9b1ec470f55cb89937d95e79ca893d460029 as payment verification failed
2023-06-08 17:17:30.998 TRACE [lightning::ln::channelmanager:4103] Failing HTLC with payment_hash 5707e3dcf3270cf1bd8f324db15d9b1ec470f55cb89937d95e79ca893d460029 backwards from us with HTLC error code 16399
2023-06-08 17:17:30.998 DEBUG [mutiny_core::event:424] EVENT: HTLCHandlingFailed, ignored

Making another invoice doesn't work either. I have to refresh first, and then the 2nd invoice I made ends up going through.

TonyGiorgio commented 1 year ago

Nothing obvious stands out to me for the testing I've done on our end so I've opened up the issue here: https://github.com/lightningdevkit/rust-lightning/issues/2345

TonyGiorgio commented 1 year ago

While a greater solution is needed in LDK, I think we're just going to have to throw something in here that pauses creating the first invoice until it has sync'd for the first time. Otherwise it's far too risky doing a first time demo being nervous about them speeding through the receive screen.