Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace home with migration screen in legacy app #658

Merged
merged 3 commits into from
Dec 2, 2024
Merged

Conversation

dpad85
Copy link
Member

@dpad85 dpad85 commented Nov 29, 2024

For context, pre-splice channels (used by the legacy Android app a.k.a v1) needed to be migrated to v2 since September 2023. A free migration flow was available until October 2024.

See this post for details about the splicing v2 update: https://acinq.co/blog/phoenix-splicing-update

In October 2024, all remaining legacy channel have been closed (i.e. funds are moved back on-chain to the "final wallet"). In some cases, for some specific channels type, the closing also needs interaction from the wallet to complete. To perform this interaction the legacy code must be used, so the legacy app still needs to be available.

To help with this migration and let users understand where their funds are, the legacy main screen now only contains the migration prompt with the final wallet balance, as well as access to the settings in case the user needs to complete the channels closing.

Migration prompt (in v1)

Spending from final wallet (in v2)

Legacy channels have now all been closed and the legacy app
can only be used to import closed legacy channels for users
who uninstalled the app.

The settings menu has also been cleaned.
@dpad85 dpad85 marked this pull request as ready for review December 2, 2024 16:43
Also made switch-to-legacy button more visible.
@dpad85 dpad85 merged commit e3905b7 into master Dec 2, 2024
@dpad85 dpad85 deleted the legacy-migration branch December 2, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant