Android broken State after moving all fund from fedimint to lightning wallet #1064
Comments
|
can you post the actual log files instead of text here, it makes it much easier to read |
there you go mate |
seems you ran into this storage issue, same as #919. Will get back to you on what to do here |
great mate, I'll be waiting |
|
Huh, so finally found some time to look at this and...we're missing a lot of logs. Both |
|
Was there any other device which you may have opened this wallet on that might have logs? |
|
Hi! I only did it on my pixel 6A and my pop os laptop. This are direct exports from the client. I didn't change the logs. The only thing I actually did is change the name of the logs and that's it |
I just had the wallet in my android phone, when I got the error from the wallet is when I tried the brave browser wallet for restoring |
|
Hmm, okay, thanks, that's helpful, thanks. That seems to imply the issue is just on the Android side and some state got lost somehow. |
some extra context and lets see if it's useful. I was emptying out my fedimint (freedom one) to test another fedimint. The empty out succeed. I don't remember which of this two things I did: either I closed the app and when I logged back it the app stoped working or I subscribed to another fedimint closed the app and then the same result. Hope this helps |
|
How did you empty it out? Did you swap it all to your lightning channel? Did you have a lightning channel already or have one made during the swap? |
|
I used the swap-out functinality from the wallet. I did swap out the entire content of the channel. I did have a channel with enough capacity before doing the swap. I'm 99% sure that it's a channel made with the help of the voltage ISP |
|
I forgot to tell you, I tried paying a robosats hodl invoice from the fedimint. The app was giving me feed back as if the transaction didn't even happen. hope this helps |
|
has there been any progress on this? |
I tried restoring from state on a browser as recommended without success. also I think I fucked up and tried to restore from seedwords in my android wallet by deleting everything
logs from android
805f 2024-04-09 17:00:15.902 TRACE [lightning::ln::peer_handler:1632] Received message ChannelReestablish(ChannelReestablish { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), next_local_commitment_number: 569, next_remote_commitment_number: 567, your_last_per_commitment_secret: [81, 13, 98, 107, 209, 155, 136, 158, 19, 210, 92, 234, 110, 71, 1, 246, 139, 201, 25, 151, 174, 1, 246, 213, 230, 198, 37, 173, 210, 179, 205, 181], my_current_per_commitment_point: PublicKey(38623380f120e1cd3dba482181615f52f4d42581c36cfd45de9461d7488d1c5661303ae53859ad9573959d2d55e2eb11a29cc392c7feede3196424a5dfb2f80a), next_funding_txid: None }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:15.905 TRACE [lightning::ln::channel:5592] Creating an announcement_signatures message for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:15.905 TRACE [lightning::ln::channel:5596] Ignore : Channel is not available for public announcements 805f 2024-04-09 17:00:15.906 DEBUG [lightning::ln::channel:4560] Reconnected channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with no loss 805f 2024-04-09 17:00:15.906 TRACE [lightning::ln::channelmanager:3296] Attempting to generate channel update for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:15.906 TRACE [lightning::ln::channelmanager:3307] Generating channel update for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:15.909 TRACE [lightning::ln::channelmanager:5851] Handling channel resumption for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement 805f 2024-04-09 17:00:15.910 TRACE [lightning::ln::peer_handler:2204] Handling SendChannelUpdate event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 892622022366658560 805f 2024-04-09 17:00:15.911 TRACE [mutiny_core::networking::proxy:92] sent data down websocket 805f 2024-04-09 17:00:15.965 TRACE [lightning::ln::channelmanager:8298] 1 transactions included in block 00000000000000000001702594f4462475227177459ae91bec4cde91c5b0a980 at height 811835 provided 805f 2024-04-09 17:00:15.965 TRACE [lightning::ln::channel:5592] Creating an announcement_signatures message for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:15.965 TRACE [lightning::ln::channel:5596] Ignore : Channel is not available for public announcements 805f 2024-04-09 17:00:15.966 DEBUG [lightning::chain::chainmonitor:668] 1 provided transactions confirmed at height 811835 in block 00000000000000000001702594f4462475227177459ae91bec4cde91c5b0a980 805f 2024-04-09 17:00:15.983 TRACE [lightning::chain::channelmonitor:3742] Processing 0 matched transactions for block at height 811835. 805f 2024-04-09 17:00:15.983 DEBUG [lightning::chain::onchaintx:714] Updating claims view at height 838478 with 0 claim requests 805f 2024-04-09 17:00:15.983 DEBUG [lightning::chain::onchaintx:834] Updating claims view at height 838478 with 0 matched transactions in block 811835 805f 2024-04-09 17:00:15.983 TRACE [lightning::chain::onchaintx:965] Bumping 0 candidates 805f 2024-04-09 17:00:15.983 TRACE [lightning::chain::chainmonitor:379] Syncing Channel Monitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:15.987 DEBUG [lightning::chain::chainmonitor:384] Channel Monitor sync for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d in progress, holding events until completion! 805f 2024-04-09 17:00:15.987 DEBUG [lightning_transaction_sync::esplora:234] Finished transaction sync at tip 000000000000000000026a14f4970a0e8200af25e0bb88464d911a2c1d237ec6: 1 confirmed, 0 unconfirmed. 805f 2024-04-09 17:00:16.009 TRACE [lightning_background_processor:693] Persisting ChannelManager... 805f 2024-04-09 17:00:16.010 TRACE [lightning_background_processor:693] Done persisting ChannelManager. 805f 2024-04-09 17:00:16.011 DEBUG [mutiny_core::node:819] Retrying to persist monitor for outpoint: OutPoint { txid: 0x7dbbd5b8a94c9242ab310e9bceacd41a5b7d41325f2ce1e19130937ec2ab2b7b, index: 0 } 805f 2024-04-09 17:00:16.340 DEBUG [mutiny_core::ldkstorage:117] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 0x7dbbd5b8a94c9242ab310e9bceacd41a5b7d41325f2ce1e19130937ec2ab2b7b, index: 0 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(0) } } 805f 2024-04-09 17:00:16.541 INFO [mutiny_core::nodemanager:1250] We are synced! 805f 2024-04-09 17:00:16.588 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 378 805f 2024-04-09 17:00:16.589 DEBUG [lightning::ln::channelmanager:7113] Received channel_update ChannelUpdate { signature: 304402206d1b63d3e08b9f90ea8291567cd56f7a5a95721288cef9dfcaafaf5c192e8a7c02201e2d9e6cbdd86aab66de6ed6a933716224eda9e74f0c77a050c17b15f0375f3d, contents: UnsignedChannelUpdate { chain_hash: 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000, short_channel_id: 753307302165413892, timestamp: 1712682015, flags: 1, cltv_expiry_delta: 34, htlc_minimum_msat: 1, htlc_maximum_msat: 1827448000, fee_base_msat: 1000, fee_proportional_millionths: 10, excess_data: [] } } for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d. 805f 2024-04-09 17:00:16.589 DEBUG [lightning::ln::peer_handler:1517] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update 805f 2024-04-09 17:00:16.589 TRACE [lightning::ln::peer_handler:1632] Received message UpdateFee(UpdateFee { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), feerate_per_kw: 8214 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:16.589 TRACE [mutiny_core::fees:177] Got fee rate from saved cache! 805f 2024-04-09 17:00:16.590 TRACE [lightning::ln::peer_handler:1632] Received message CommitmentSigned(CommitmentSigned { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), signature: 304402201f4fe601c0b5a16ed162cdaec5149e1c68d5621f4057158c2123393ba286470c02205e9b286da1480ba76195bac4c9a48e7f17cfe157b8138459e3a1ab3d0c51272b, htlc_signatures: [] }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:16.605 TRACE [lightning::ln::channel:1612] Building commitment transaction number 281474976710087 (really 568 xor 184029055702567) for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d for us, generated by remote with fee 8214... 805f 2024-04-09 17:00:16.605 TRACE [lightning::ln::channel:1777] ...including to_local output with value 47072 805f 2024-04-09 17:00:16.605 TRACE [lightning::ln::channel:1783] ...including to_remote output with value 1792888 805f 2024-04-09 17:00:16.619 TRACE [lightning::ln::channel:3365] Checking commitment tx signature 1f4fe601c0b5a16ed162cdaec5149e1c68d5621f4057158c2123393ba286470c5e9b286da1480ba76195bac4c9a48e7f17cfe157b8138459e3a1ab3d0c51272b by key 03a4e3bcd4e7be3b126bf1630dcc0eba155f15da3eb4bb35905f7ea9b83fe2d4ab against tx 02000000017b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d00000000009a5fa78002e0b7000000000000220020f46e83bf5c016165d28843db8edc607da31fe83fe62715bf5c7b4b89636f8757785b1b00000000001600140f1a0d312573f214a95e29651ef221fca209b5bd1f547e20 (sighash 3404a3df3a49e9c56ef6dcf43d4270289ac4c7492eb9486166434df31250bbc4) with redeemscript 47522102f353e5a6663f78f01558a98e13e4a5ce5ee5277f2affada0acf87e686b53c95c2103a4e3bcd4e7be3b126bf1630dcc0eba155f15da3eb4bb35905f7ea9b83fe2d4ab52ae in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:16.623 TRACE [lightning::ln::channel:5907] Updating HTLC state for a newly-sent commitment_signed... 805f 2024-04-09 17:00:16.623 TRACE [lightning::ln::channel:5932] ...promoting inbound AwaitingRemoteRevokeToAnnounce fee update 8214 to Committed 805f 2024-04-09 17:00:16.630 TRACE [lightning::ln::channel:1612] Building commitment transaction number 281474976710086 (really 569 xor 184029055702567) for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d for remote, generated by us with fee 8214... 805f 2024-04-09 17:00:16.630 TRACE [lightning::ln::channel:1777] ...including to_remote output with value 1792888 805f 2024-04-09 17:00:16.630 TRACE [lightning::ln::channel:1783] ...including to_local output with value 47072 805f 2024-04-09 17:00:16.631 DEBUG [lightning::ln::channel:3559] Received valid commitment_signed from peer in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d, updating HTLC state and responding with our own commitment_signed and a revoke_and_ack. 805f 2024-04-09 17:00:16.637 TRACE [lightning::chain::chainmonitor:774] Updating ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:16.637 INFO [lightning::chain::channelmonitor:2752] Applying update to monitor 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d, bringing update_id from 1209 to 1210 with 2 change(s). 805f 2024-04-09 17:00:16.637 TRACE [lightning::chain::channelmonitor:2793] Updating ChannelMonitor with latest holder commitment transaction info 805f 2024-04-09 17:00:16.638 TRACE [lightning::chain::channelmonitor:2802] Updating ChannelMonitor with latest counterparty commitment transaction info 805f 2024-04-09 17:00:16.638 TRACE [lightning::chain::channelmonitor:2482] Tracking new counterparty commitment transaction with txid 213344c567dcf2065913776c442dc380a293e317cdfd28502e4a3add4cf958cd at commitment number 281474976710086 with 0 HTLC outputs 805f 2024-04-09 17:00:16.640 DEBUG [lightning::chain::chainmonitor:793] Persistence of ChannelMonitorUpdate for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d in progress 805f 2024-04-09 17:00:16.640 DEBUG [lightning::ln::channelmanager:6827] ChannelMonitor update for 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d in flight, holding messages until the update completes. 805f 2024-04-09 17:00:16.641 TRACE [lightning_background_processor:693] Persisting ChannelManager... 805f 2024-04-09 17:00:16.647 TRACE [lightning_background_processor:693] Done persisting ChannelManager. 805f 2024-04-09 17:00:17.439 DEBUG [mutiny_core::ldkstorage:117] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 0x7dbbd5b8a94c9242ab310e9bceacd41a5b7d41325f2ce1e19130937ec2ab2b7b, index: 0 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(4294967297) } } 805f 2024-04-09 17:00:17.756 DEBUG [mutiny_core::ldkstorage:117] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 0x7dbbd5b8a94c9242ab310e9bceacd41a5b7d41325f2ce1e19130937ec2ab2b7b, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(1210) } } 805f 2024-04-09 17:00:17.760 TRACE [lightning::ln::channelmanager:5956] ChannelMonitor updated to 1210. Current highest is 1210. 0 pending in-flight updates. 805f 2024-04-09 17:00:17.766 TRACE [lightning::ln::channel:5592] Creating an announcement_signatures message for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:17.766 TRACE [lightning::ln::channel:5596] Ignore : Channel is not available for public announcements 805f 2024-04-09 17:00:17.771 TRACE [lightning::ln::channel:4380] Regenerating latest commitment update in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with 0 update_adds, 0 update_fulfills, 0 update_fails, and 0 update_fail_malformeds 805f 2024-04-09 17:00:17.790 TRACE [lightning::ln::channel:1612] Building commitment transaction number 281474976710086 (really 569 xor 184029055702567) for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d for remote, generated by us with fee 8214... 805f 2024-04-09 17:00:17.791 TRACE [lightning::ln::channel:1777] ...including to_remote output with value 1792888 805f 2024-04-09 17:00:17.791 TRACE [lightning::ln::channel:1783] ...including to_local output with value 47072 805f 2024-04-09 17:00:17.799 TRACE [lightning::ln::channel:6026] Signed remote commitment tx 02000000017b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d00000000009a5fa78002e0b7000000000000160014197819ccf49a338356d37eaf6d566fdb72ad5122785b1b000000000022002071d57017bd9bf97a08ef5b1a07fc44b2f9ac60c2600806f3f1d9874f87e8ecd81e547e20 (txid 213344c567dcf2065913776c442dc380a293e317cdfd28502e4a3add4cf958cd) with redeemscript 47522102f353e5a6663f78f01558a98e13e4a5ce5ee5277f2affada0acf87e686b53c95c2103a4e3bcd4e7be3b126bf1630dcc0eba155f15da3eb4bb35905f7ea9b83fe2d4ab52ae -> 25bdcbd04a28b800bf8b1d89cf98a98fb66037c80aadc122b9381888646e7b503367d0789b9bf775662bc3593093e4f817e2e0559468b4bd4ec4a7b6c61ada13 in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:17.799 DEBUG [lightning::ln::channel:4243] Restored monitor updating in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d resulting in a commitment update and an RAA, with RAA first 805f 2024-04-09 17:00:17.800 TRACE [lightning::ln::channelmanager:5851] Handling channel resumption for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with an RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement 805f 2024-04-09 17:00:17.802 DEBUG [lightning::ln::peer_handler:2142] Handling SendRevokeAndACK event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:17.803 TRACE [lightning::ln::peer_handler:1279] Enqueueing message RevokeAndACK { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), per_commitment_secret: [160, 224, 113, 22, 87, 111, 219, 162, 154, 254, 243, 125, 66, 189, 2, 204, 182, 237, 149, 15, 226, 70, 68, 44, 155, 0, 203, 180, 78, 213, 251, 196], next_per_commitment_point: PublicKey(943d63fc507f0a7c337f5bda2b69aa1e549b4c204ffce71354d7a41ea03c20b06b6b0f05a926bd31f73563c6d2de7f2a1ea3d1eac5568805cf15c310ac182334) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:17.804 DEBUG [lightning::ln::peer_handler:2117] Handling UpdateHTLCs event in peer_handler for node 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 with 0 adds, 0 fulfills, 0 fails for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:17.804 TRACE [lightning::ln::peer_handler:1279] Enqueueing message CommitmentSigned { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), signature: 3044022025bdcbd04a28b800bf8b1d89cf98a98fb66037c80aadc122b9381888646e7b5002203367d0789b9bf775662bc3593093e4f817e2e0559468b4bd4ec4a7b6c61ada13, htlc_signatures: [] } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:17.805 TRACE [lightning_background_processor:693] Persisting ChannelManager... 805f 2024-04-09 17:00:17.808 TRACE [lightning_background_processor:693] Done persisting ChannelManager. 805f 2024-04-09 17:00:17.809 TRACE [mutiny_core::networking::proxy:92] sent data down websocket 805f 2024-04-09 17:00:17.810 TRACE [mutiny_core::networking::proxy:92] sent data down websocket 805f 2024-04-09 17:00:23.783 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred 805f 2024-04-09 17:00:23.784 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred 805f 2024-04-09 17:00:23.786 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:23.790 TRACE [mutiny_core::networking::proxy:92] sent data down websocket 805f 2024-04-09 17:00:28.794 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 171 805f 2024-04-09 17:00:28.795 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:28.797 TRACE [lightning::ln::peer_handler:1632] Received message RevokeAndACK(RevokeAndACK { channel_id: ChannelId([123, 43, 171, 194, 126, 147, 48, 145, 225, 225, 44, 95, 50, 65, 125, 91, 26, 212, 172, 206, 155, 14, 49, 171, 66, 146, 76, 169, 184, 213, 187, 125]), per_commitment_secret: [42, 206, 32, 78, 174, 79, 252, 8, 134, 23, 217, 25, 118, 139, 83, 239, 246, 253, 155, 221, 48, 99, 204, 162, 191, 122, 121, 189, 238, 5, 248, 204], next_per_commitment_point: PublicKey(003930b09211644d2b85eae4493d519ba23b007a31350240eb04f2dcfb83f1a1b0150c944915053d9ea9ece9b69b90c4ed9520bd867c9995b9fea9de51e7c0cc) }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0 805f 2024-04-09 17:00:28.802 TRACE [lightning::ln::channel:3788] Updating HTLCs on receipt of RAA in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d... 805f 2024-04-09 17:00:28.802 DEBUG [lightning::ln::channel:3972] Received a valid revoke_and_ack for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with no reply necessary. Releasing monitor update. 805f 2024-04-09 17:00:28.802 TRACE [lightning::chain::chainmonitor:774] Updating ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:28.802 INFO [lightning::chain::channelmonitor:2752] Applying update to monitor 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d, bringing update_id from 1210 to 1211 with 1 change(s). 805f 2024-04-09 17:00:28.803 TRACE [lightning::chain::channelmonitor:2810] Updating ChannelMonitor with commitment secret 805f 2024-04-09 17:00:28.810 DEBUG [lightning::chain::chainmonitor:793] Persistence of ChannelMonitorUpdate for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d in progress 805f 2024-04-09 17:00:28.810 DEBUG [lightning::ln::channelmanager:7004] ChannelMonitor update for 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d in flight, holding messages until the update completes. 805f 2024-04-09 17:00:28.811 TRACE [lightning::ln::channelmanager:3307] Generating channel update for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:28.814 TRACE [lightning_background_processor:693] Persisting ChannelManager... 805f 2024-04-09 17:00:28.816 TRACE [lightning_background_processor:693] Done persisting ChannelManager. 805f 2024-04-09 17:00:31.122 DEBUG [mutiny_core::ldkstorage:117] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: 0x7dbbd5b8a94c9242ab310e9bceacd41a5b7d41325f2ce1e19130937ec2ab2b7b, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(1211) } } 805f 2024-04-09 17:00:31.124 TRACE [lightning::ln::channelmanager:5956] ChannelMonitor updated to 1211. Current highest is 1211. 0 pending in-flight updates. 805f 2024-04-09 17:00:31.124 TRACE [lightning::ln::channel:5592] Creating an announcement_signatures message for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d 805f 2024-04-09 17:00:31.124 TRACE [lightning::ln::channel:5596] Ignore : Channel is not available for public announcements 805f 2024-04-09 17:00:31.124 DEBUG [lightning::ln::channel:4243] Restored monitor updating in channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d resulting in no commitment update and no RAA, with RAA first 805f 2024-04-09 17:00:31.124 TRACE [lightning::ln::channelmanager:5851] Handling channel resumption for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement 805f 2024-04-09 17:00:31.125 TRACE [lightning_background_processor:693] Persisting ChannelManager... 805f 2024-04-09 17:00:31.127 TRACE [lightning_background_processor:693] Done persisting ChannelManager. 341f 2024-04-16 11:29:05.947 TRACE [mutiny_core::nodemanager:337] Checking device lock 341f 2024-04-16 11:29:05.947 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713266938, device: "1a8403fe-811f-4924-b0a5-0bf6aaefc25c" } 341f 2024-04-16 11:29:06.618 TRACE [mutiny_core::nodemanager:342] Device lock set: took 670ms 341f 2024-04-16 11:29:06.618 INFO [mutiny_core::nodemanager:365] Building node manager components 341f 2024-04-16 11:29:06.708 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 341f 2024-04-16 11:29:06.729 DEBUG [mutiny_core::gossip:204] retrieved local scorer 341f 2024-04-16 11:29:06.730 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 21ms 341f 2024-04-16 11:29:06.730 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 112ms 341f 2024-04-16 11:29:06.730 DEBUG [mutiny_core::nodemanager:427] Building nodes 341f 2024-04-16 11:29:06.730 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") 341f 2024-04-16 11:29:06.772 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching 341f 2024-04-16 11:29:06.778 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching 341f 2024-04-16 11:29:06.788 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching 341f 2024-04-16 11:29:06.792 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching 341f 2024-04-16 11:29:06.792 INFO [mutiny_core::node:417] creating lsp client 341f 2024-04-16 11:29:06.792 INFO [mutiny_core::node:425] lsp config matches saved lsp config 341f 2024-04-16 11:29:06.792 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage 341f 2024-04-16 11:29:06.794 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. 341f 2024-04-16 11:29:06.794 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning 5c3a 2024-04-16 11:30:38.824 TRACE [mutiny_core::nodemanager:337] Checking device lock 5c3a 2024-04-16 11:30:38.824 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713267007, device: "1a8403fe-811f-4924-b0a5-0bf6aaefc25c" } 5c3a 2024-04-16 11:30:39.625 TRACE [mutiny_core::nodemanager:342] Device lock set: took 800ms 5c3a 2024-04-16 11:30:39.625 INFO [mutiny_core::nodemanager:365] Building node manager components 5c3a 2024-04-16 11:30:39.718 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 5c3a 2024-04-16 11:30:39.739 DEBUG [mutiny_core::gossip:204] retrieved local scorer 5c3a 2024-04-16 11:30:39.739 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 20ms 5c3a 2024-04-16 11:30:39.739 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 114ms 5c3a 2024-04-16 11:30:39.739 DEBUG [mutiny_core::nodemanager:427] Building nodes 5c3a 2024-04-16 11:30:39.740 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") 5c3a 2024-04-16 11:30:39.780 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching 5c3a 2024-04-16 11:30:39.786 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching 5c3a 2024-04-16 11:30:39.797 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching 5c3a 2024-04-16 11:30:39.801 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching 5c3a 2024-04-16 11:30:39.801 INFO [mutiny_core::node:417] creating lsp client 5c3a 2024-04-16 11:30:39.801 INFO [mutiny_core::node:425] lsp config matches saved lsp config 5c3a 2024-04-16 11:30:39.801 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage 5c3a 2024-04-16 11:30:39.803 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. 5c3a 2024-04-16 11:30:39.803 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning 5c3a 2024-04-16 11:46:36.995 ERROR [mutiny_core::nodemanager:359] Error setting device lock: Network connection closed. 5231 2024-04-16 12:14:18.519 TRACE [mutiny_core::nodemanager:337] Checking device lock 5231 2024-04-16 12:14:18.520 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713269632, device: "376822bc-41f2-4b7f-9663-014e73ee921b" } b224 2024-04-16 12:15:27.308 TRACE [mutiny_core::nodemanager:337] Checking device lock b224 2024-04-16 12:15:27.308 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713269663, device: "376822bc-41f2-4b7f-9663-014e73ee921b" } b224 2024-04-16 12:15:28.069 TRACE [mutiny_core::nodemanager:342] Device lock set: took 760ms b224 2024-04-16 12:15:28.069 INFO [mutiny_core::nodemanager:365] Building node manager components b224 2024-04-16 12:15:28.253 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 b224 2024-04-16 12:15:28.276 DEBUG [mutiny_core::gossip:204] retrieved local scorer b224 2024-04-16 12:15:28.277 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 23ms b224 2024-04-16 12:15:28.277 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 208ms b224 2024-04-16 12:15:28.277 DEBUG [mutiny_core::nodemanager:427] Building nodes b224 2024-04-16 12:15:28.279 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") b224 2024-04-16 12:15:28.348 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching b224 2024-04-16 12:15:28.357 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching b224 2024-04-16 12:15:28.374 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching b224 2024-04-16 12:15:28.380 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching b224 2024-04-16 12:15:28.380 INFO [mutiny_core::node:417] creating lsp client b224 2024-04-16 12:15:28.380 INFO [mutiny_core::node:425] lsp config matches saved lsp config b224 2024-04-16 12:15:28.380 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage b224 2024-04-16 12:15:28.474 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 b224 2024-04-16 12:15:28.475 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! b224 2024-04-16 12:15:28.475 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight b224 2024-04-16 12:15:28.475 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. b224 2024-04-16 12:15:28.476 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, b224 2024-04-16 12:15:28.476 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! b224 2024-04-16 12:15:28.476 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. b224 2024-04-16 12:15:28.476 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightninglogs from brave browser in linux
0c6c 2024-04-16 12:11:50.148 TRACE [mutiny_core::nodemanager:337] Checking device lock 0c6c 2024-04-16 12:11:50.148 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713269477, device: "1a8403fe-811f-4924-b0a5-0bf6aaefc25c" } eebf 2024-04-16 12:12:20.097 TRACE [mutiny_core::nodemanager:337] Checking device lock eebf 2024-04-16 12:12:20.097 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713269477, device: "1a8403fe-811f-4924-b0a5-0bf6aaefc25c" } eebf 2024-04-16 12:12:20.786 TRACE [mutiny_core::nodemanager:342] Device lock set: took 688ms eebf 2024-04-16 12:12:20.786 INFO [mutiny_core::nodemanager:365] Building node manager components eebf 2024-04-16 12:12:20.832 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 eebf 2024-04-16 12:12:20.832 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 0ms eebf 2024-04-16 12:12:20.832 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 47ms eebf 2024-04-16 12:12:20.832 DEBUG [mutiny_core::nodemanager:427] Building nodes eebf 2024-04-16 12:12:20.833 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") eebf 2024-04-16 12:12:20.878 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching eebf 2024-04-16 12:12:20.882 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching eebf 2024-04-16 12:12:20.896 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching eebf 2024-04-16 12:12:20.901 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching eebf 2024-04-16 12:12:20.901 INFO [mutiny_core::node:417] creating lsp client eebf 2024-04-16 12:12:20.901 INFO [mutiny_core::node:425] lsp config matches saved lsp config eebf 2024-04-16 12:12:20.901 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage eebf 2024-04-16 12:12:20.974 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 eebf 2024-04-16 12:12:20.974 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. eebf 2024-04-16 12:12:20.975 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning 708d 2024-04-16 12:29:18.574 TRACE [mutiny_core::nodemanager:337] Checking device lock 708d 2024-04-16 12:29:18.575 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713270264, device: "3a49ab87-5ab8-4002-b541-d42bcdbd302f" } 708d 2024-04-16 12:29:19.265 TRACE [mutiny_core::nodemanager:342] Device lock set: took 690ms 708d 2024-04-16 12:29:19.265 INFO [mutiny_core::nodemanager:365] Building node manager components 708d 2024-04-16 12:29:19.328 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 708d 2024-04-16 12:29:19.329 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 0ms 708d 2024-04-16 12:29:19.329 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 64ms 708d 2024-04-16 12:29:19.329 DEBUG [mutiny_core::nodemanager:427] Building nodes 708d 2024-04-16 12:29:19.330 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") 708d 2024-04-16 12:29:19.407 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching 708d 2024-04-16 12:29:19.411 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching 708d 2024-04-16 12:29:19.431 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching 708d 2024-04-16 12:29:19.439 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching 708d 2024-04-16 12:29:19.439 INFO [mutiny_core::node:417] creating lsp client 708d 2024-04-16 12:29:19.439 INFO [mutiny_core::node:425] lsp config matches saved lsp config 708d 2024-04-16 12:29:19.440 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage 708d 2024-04-16 12:29:19.516 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. 708d 2024-04-16 12:29:19.517 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightninglogs from android after deleting info and restoring with seedwords
9c0d 2024-04-16 12:20:09.700 TRACE [mutiny_core::nodemanager:337] Checking device lock 9c0d 2024-04-16 12:20:09.700 INFO [mutiny_core::nodemanager:339] Current device lock: DeviceLock { time: 1713269924, device: "1a8403fe-811f-4924-b0a5-0bf6aaefc25c" } 9c0d 2024-04-16 12:20:10.604 TRACE [mutiny_core::nodemanager:342] Device lock set: took 904ms 9c0d 2024-04-16 12:20:10.604 INFO [mutiny_core::nodemanager:365] Building node manager components 9c0d 2024-04-16 12:20:10.663 DEBUG [mutiny_core::gossip:181] Previous gossip sync timestamp: 0 9c0d 2024-04-16 12:20:10.664 TRACE [mutiny_core::gossip:221] Gossip sync/Scorer initialized in 0ms 9c0d 2024-04-16 12:20:10.666 TRACE [mutiny_core::nodemanager:408] Node manager Components built: took 61ms 9c0d 2024-04-16 12:20:10.666 DEBUG [mutiny_core::nodemanager:427] Building nodes 9c0d 2024-04-16 12:20:10.668 INFO [mutiny_core::node:357] initializing a new node: Some("3246d2a8-631c-406e-a04e-a8a63c0ae5bc") 9c0d 2024-04-16 12:20:10.729 DEBUG [mutiny_core::ldkstorage:180] Channel monitor b549b691a60a5e68c077d213a3d2ae558d868e37823ec72629a4bcee00b9051c:1 has no claimable balances, not watching 9c0d 2024-04-16 12:20:10.735 DEBUG [mutiny_core::ldkstorage:180] Channel monitor c608f5fffa9928150ffad6e058167ab16e59d81dce6751d1d06bd29bfe3f68ab:0 has no claimable balances, not watching 9c0d 2024-04-16 12:20:10.747 DEBUG [mutiny_core::ldkstorage:180] Channel monitor 3c5714de3859f584d7fd25b577ad483aab99fd6d87032f7c220b35c040923a7f:0 has no claimable balances, not watching 9c0d 2024-04-16 12:20:10.750 DEBUG [mutiny_core::ldkstorage:180] Channel monitor f92d0f1789f3f8cce7b199f6ea78ff527469bdddc775d98e22b459d7350bdeae:0 has no claimable balances, not watching 9c0d 2024-04-16 12:20:10.750 INFO [mutiny_core::node:417] creating lsp client 9c0d 2024-04-16 12:20:10.751 INFO [mutiny_core::node:425] lsp config matches saved lsp config 9c0d 2024-04-16 12:20:10.751 DEBUG [mutiny_core::ldkstorage:212] Reading channel manager from storage 9c0d 2024-04-16 12:20:10.841 INFO [lightning::ln::channelmanager:10363] Successfully loaded channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d at update_id 1310 against monitor at update id 1309 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10643] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10644] The ChannelMonitor for channel 7b2babc27e933091e1e12c5f32417d5b1ad4acce9b0e31ab42924ca9b8d5bb7d is at update_id 1309 with update_id through 1309 in-flight 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10646] but the ChannelManager is at update_id 1310. 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10647] The chain::Watch API *requires* that monitors are persisted durably before returning, 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10648] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10649] Without the latest ChannelMonitor we cannot continue without risking funds. 9c0d 2024-04-16 12:20:10.843 ERROR [lightning::ln::channelmanager:10650] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightningThe text was updated successfully, but these errors were encountered: