search

MutinyWallet / mutiny-web

The frontend for Mutiny Wallet
https://app.mutinywallet.com
MIT License
176 stars 57 forks source link

failed to load mutiny #613

Closed tulla2020 closed 10 months ago

tulla2020 commented 10 months ago

unable to restore wallet. put in 12 words. imported json. keeps telling me wallet is open on another device...but its not. mutiny

TonyGiorgio commented 10 months ago

So you're restoring from another device? What device are you coming from and how are you sure it is not running elsewhere? Do you have other tabs with the wallet loaded?

tulla2020 commented 10 months ago

i used mutiny with iphone and macbook. all tabs, windows, browsers closed. here is recent logs:

2023-10-22 21:06:51.527 DEBUG [mutiny_core::gossip:154] Previous gossip sync timestamp: 0 2023-10-22 21:06:52.757 DEBUG [mutiny_core::gossip:175] retrieved remote scorer 2023-10-22 21:06:53.397 INFO [mutiny_core::node:189] initializing a new node: 4d2d8b2e-0e4c-4648-82e6-b6e951d6d82b 2023-10-22 21:06:53.407 DEBUG [mutiny_core::ldkstorage:218] Reading channel manager from storage 2023-10-22 21:06:53.411 INFO [lightning::ln::channelmanager:9310] Successfully loaded channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 at update_id 117 against monitor at update id 116 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9585] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9586] The ChannelMonitor for channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 is at update_id 116 with update_id through 116 in-flight 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9588] but the ChannelManager is at update_id 117. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9589] The chain::Watch API requires that monitors are persisted durably before returning, 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9590] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9591] Without the latest ChannelMonitor we cannot continue without risking funds. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9592] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning

TonyGiorgio commented 10 months ago

When was the last time it was used successfully? Are these logs from the original device?

tulla2020 commented 10 months ago

a week ago? yes, orginal device.

benthecarman commented 10 months ago

can you post the whole log file?

tulla2020 commented 10 months ago

this is what i JUST DOWNLOADED:

2023-10-22 21:06:51.527 DEBUG [mutiny_core::gossip:154] Previous gossip sync timestamp: 0 2023-10-22 21:06:52.757 DEBUG [mutiny_core::gossip:175] retrieved remote scorer 2023-10-22 21:06:53.397 INFO [mutiny_core::node:189] initializing a new node: 4d2d8b2e-0e4c-4648-82e6-b6e951d6d82b 2023-10-22 21:06:53.407 DEBUG [mutiny_core::ldkstorage:218] Reading channel manager from storage 2023-10-22 21:06:53.411 INFO [lightning::ln::channelmanager:9310] Successfully loaded channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 at update_id 117 against monitor at update id 116 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9585] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9586] The ChannelMonitor for channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 is at update_id 116 with update_id through 116 in-flight 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9588] but the ChannelManager is at update_id 117. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9589] The chain::Watch API requires that monitors are persisted durably before returning, 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9590] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9591] Without the latest ChannelMonitor we cannot continue without risking funds. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9592] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning 2023-10-22 22:50:37.732 DEBUG [mutiny_core::gossip:154] Previous gossip sync timestamp: 0 2023-10-22 22:50:38.967 DEBUG [mutiny_core::gossip:175] retrieved remote scorer 2023-10-22 22:50:39.540 INFO [mutiny_core::node:189] initializing a new node: 4d2d8b2e-0e4c-4648-82e6-b6e951d6d82b 2023-10-22 22:50:39.548 DEBUG [mutiny_core::ldkstorage:218] Reading channel manager from storage 2023-10-22 22:50:39.551 INFO [lightning::ln::channelmanager:9310] Successfully loaded channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 at update_id 117 against monitor at update id 116 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9585] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9586] The ChannelMonitor for channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 is at update_id 116 with update_id through 116 in-flight 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9588] but the ChannelManager is at update_id 117. 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9589] The chain::Watch API requires that monitors are persisted durably before returning, 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9590] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9591] Without the latest ChannelMonitor we cannot continue without risking funds. 2023-10-22 22:50:39.551 ERROR [lightning::ln::channelmanager:9592] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning 2023-10-22 23:50:26.764 DEBUG [mutiny_core::gossip:154] Previous gossip sync timestamp: 0 2023-10-22 23:50:28.078 DEBUG [mutiny_core::gossip:175] retrieved remote scorer 2023-10-22 23:50:28.736 INFO [mutiny_core::node:189] initializing a new node: 4d2d8b2e-0e4c-4648-82e6-b6e951d6d82b 2023-10-22 23:50:28.744 DEBUG [mutiny_core::ldkstorage:218] Reading channel manager from storage 2023-10-22 23:50:28.746 INFO [lightning::ln::channelmanager:9310] Successfully loaded channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 at update_id 117 against monitor at update id 116 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9585] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9586] The ChannelMonitor for channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 is at update_id 116 with update_id through 116 in-flight 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9588] but the ChannelManager is at update_id 117. 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9589] The chain::Watch API requires that monitors are persisted durably before returning, 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9590] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9591] Without the latest ChannelMonitor we cannot continue without risking funds. 2023-10-22 23:50:28.746 ERROR [lightning::ln::channelmanager:9592] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning

tulla2020 commented 10 months ago

on the bottom of the page i am given the option "delete everything"....

TonyGiorgio commented 10 months ago

It's just strange that those logs are it. Have you already deleted it before? Is this after you had already deleted it and restored? And if so, do you know why why you might have deleted it?

The main problem here is there's a state update missing. If we had the original logs we could investigate more deeply. But if you did delete everything off of the original device and this is the state you're in, we're going to have to build a tool to recover from this problem specifically. Has been pretty rare.

tulla2020 commented 10 months ago

these are logs further back i downloaded. does help?

2023-10-22 21:06:51.527 DEBUG [mutiny_core::gossip:154] Previous gossip sync timestamp: 0 2023-10-22 21:06:52.757 DEBUG [mutiny_core::gossip:175] retrieved remote scorer 2023-10-22 21:06:53.397 INFO [mutiny_core::node:189] initializing a new node: 4d2d8b2e-0e4c-4648-82e6-b6e951d6d82b 2023-10-22 21:06:53.407 DEBUG [mutiny_core::ldkstorage:218] Reading channel manager from storage 2023-10-22 21:06:53.411 INFO [lightning::ln::channelmanager:9310] Successfully loaded channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 at update_id 117 against monitor at update id 116 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9585] A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9586] The ChannelMonitor for channel 8cef53a189cea5ed73d95b3cfd7af042daf088ad616c9b041ecd38ac9ccaca50 is at update_id 116 with update_id through 116 in-flight 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9588] but the ChannelManager is at update_id 117. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9589] The chain::Watch API requires that monitors are persisted durably before returning, 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9590] client applications must ensure that ChannelMonitor data is always available and the latest to avoid funds loss! 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9591] Without the latest ChannelMonitor we cannot continue without risking funds. 2023-10-22 21:06:53.411 ERROR [lightning::ln::channelmanager:9592] Please ensure the chain::Watch API requirements are met and file a bug report at https://github.com/lightningdevkit/rust-lightning

tulla2020 commented 10 months ago

can you give me some next steps? or more help. ?

TonyGiorgio commented 10 months ago

If you do not have the original state on the original device, we're going to have to do a bit of work to recover things. It was previously a rare thing to even be possible but has happened a couple times. We've planned this work out and will provide you an update when it is available.

benthecarman commented 10 months ago

Hey, we made a simple CLI tool that should help try to recover your funds. You should be able to download it and run mutiny-data-recovery --seed "your seed here" and make it so you can open mutiny again and hopefully get your funds back

https://github.com/MutinyWallet/mutiny-data-recovery/releases/tag/v0.1.0

tulla2020 commented 10 months ago

i appreciate your quick help Ben....however i may need a bit more instruction....i download the file for my Mac....then i copy all that into terminal? then i copy the above command and include my 12 words?

benthecarman commented 10 months ago

Yeah you just need to run it with your seed words

tulla2020 commented 10 months ago

not sure i'm having luck. i ran the code and it says 'process completed" but i'm not sure what to do next...

tulla2020 commented 10 months ago

Image 10-26-23 at 5 56 PM

benthecarman commented 10 months ago

I think you're running something else, there should only be one log from it

tulla2020 commented 10 months ago

i'm sorry for the confusion....i am not sure what to do next. i ran the download. . . but i did not copy in the 'mutiny data recovery' piece.....and i'm not sure how to format it anyways. with " ____" ?

TonyGiorgio commented 10 months ago

Open a terminal in the folder you downloaded in and type

./mutiny-data-recovery --seed "seed here"

tulla2020 commented 10 months ago

i wish i understood what you meant

tulla2020 commented 10 months ago

still needing some help. download the zip file...opened terminal in the folder....copied and pasted with my seeds words. do i need quotation marks? i've tried it a few ways.

tulla2020 commented 10 months ago

EAFBEFF5-3740-4CEA-9FF7-A2A6AA85686B

tulla2020 commented 10 months ago

sorry to be a bother...but i'm hoping you guys can give me some more help here...

tulla2020 commented 10 months ago

maybe there is a better platform? telegram?

benthecarman commented 10 months ago

@tulla2020 you can message me on telegram, I am on benthecarman on there as well

TonyGiorgio commented 10 months ago

The file is called mutiny-data-recovery_darwin, try that.

benthecarman commented 10 months ago

Funds were recovered on telegram!