cake_wallet/cw_bitcoin_cash
Omar Hatem fb33a6f23d
Cw 688 avoid wallet file corruption (#1582)
* CW-688 Store Seed and keys in .keys file

* CW-688 Open wallet from keys in .keys file and migrate wallets using the old file

* CW-688 Open wallet from keys in .keys file and migrate wallets using the old file

* CW-688 Restore .keys file from .keys.backup

* CW-688 Restore .keys file from .keys.backup

* CW-688 Move saving .keys files into the save function instead of the service

* CW-688 Handle corrupt wallets

* CW-688 Handle corrupt wallets

* CW-688 Remove code duplication

* CW-688 Reduce cache dependency

* wrap any file reading/writing function with try/catch [skip ci]

---------

Co-authored-by: Konstantin Ullrich <konstantinullrich12@gmail.com>
2024-08-09 23:15:30 +03:00
..
lib Cw 688 avoid wallet file corruption (#1582) 2024-08-09 23:15:30 +03:00
test CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
.gitignore CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
.metadata CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
analysis_options.yaml CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
CHANGELOG.md CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
LICENSE CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00
pubspec.yaml Cw 453 (#1306) 2024-05-29 17:43:48 +03:00
README.md CW-432-Add-Bitcoin-Cash-BCH (#1041) 2023-10-13 01:50:16 +03:00

TODO: Put a short description of the package here that helps potential users know whether this package might be useful for them.

Features

TODO: List what your package can do. Maybe include images, gifs, or videos.

Getting started

TODO: List prerequisites and provide or point to information on how to start using the package.

Usage

TODO: Include short and useful examples for package users. Add longer examples to /example folder.

const like = 'sample';

Additional information

TODO: Tell users more about the package: where to find more information, how to contribute to the package, how to file issues, what response they can expect from the package authors, and more.