Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Handle situation when remote node has no backup capabilities #2220

Open
korhaliv opened this issue May 16, 2019 · 0 comments
Open

Handle situation when remote node has no backup capabilities #2220

korhaliv opened this issue May 16, 2019 · 0 comments
Labels
backups SCB backup and restore related features status: needs design issue needs designs

Comments

@korhaliv
Copy link
Member

Detailed Description

Handle UX edge case when a user uses <0.6 LND remote node without SCB support. Currently, the user will be prompted to setup backup provider but actual backing up won't happen. This is potentially a dangerous situation since the user doesn't know that backups are not working actually.

@korhaliv korhaliv added the backups SCB backup and restore related features label May 16, 2019
@korhaliv korhaliv added this to the v0.5.0-beta milestone May 16, 2019
@mrfelton mrfelton added the status: needs design issue needs designs label May 16, 2019
@mrfelton mrfelton modified the milestones: v0.5.0-beta, v0.6.0-beta Jun 6, 2019
@mrfelton mrfelton modified the milestones: v0.6.0-beta, v0.7.0-beta Oct 19, 2019
@mrfelton mrfelton removed this from the v0.7.0-beta milestone Mar 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backups SCB backup and restore related features status: needs design issue needs designs
Projects
None yet
Development

No branches or pull requests

2 participants