-
Notifications
You must be signed in to change notification settings - Fork 31
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
Beet Auto close app #32
Comments
Well, this is a user's local device. That being said, keys/wallets are saved encrypted upon creation. So a backup is never "needed" ..Just advised. The functionality will be added soon, compatible with the current reference wallet's bin files. In the event of theft while open, probably auto-locking the wallet after a (configurable?) time limit would work best. @sschiessl-bcp thoughts? |
To avoid misunderstandings. Beet holds NO state whatsoever. just the keys in encrypted format. All other information is read from the chain. |
This |
Yes Sir, understood. |
Is your feature request related to a problem? Please describe.
I was thinking a checkbox to "auto close the app after xx time" might be a good option. But, how could that be done in the event that a transaction occurs, a back up is mandated, but the user is either unavailable, device is lost, stolen, away from backup device, etc?
With that said, I am curious as to how Beet would currently handle an instance where a user accesses the app, makes transactions, and experiences a power failure, reboot, loss of connection, or back up needed?
The text was updated successfully, but these errors were encountered: