state changes may be needed in the future, but for now the GUI will be
able to refresh wallet balances in response to offer soft-cancellation
and addition.
* disonnect from untusted faster, fork point change, pool state handle
* name conflict
* deadlock
* fix inclusion validation for first sub epoch, don't fetch header blocks on every new peak
* lint
* can be none
* revert changes
* stop wallet peers if trusted peer is connected and synced
* remove pool changes
* remove cononfusing log
* Fix running blocks with generators that use back-references
* Update tools/run_block.py
Co-authored-by: Thomas Pytleski <pytlesk4@gmail.com>
Co-authored-by: Thomas Pytleski <pytlesk4@gmail.com>
conflicting with DEFAULT_ROOT_PATH when CHIA_ROOT is set. When the GUI
launches chia services, CHIA_ROOT is set, which was preventing the
wallet backend from copying existing DBs from the standalone_wallet.
* CLI support for performing an incremental keyring migration. This handles the case where new keys were created by an older client or the light wallet, and those keys then need to be moved to keyring.yaml.
* Opportunistically perform a silent incremental keyring migration when the GUI unlocks the keyring.
Track when keyring migration occurs so that we don't needlessly attempt on each GUI launch. ~/.chia_keys/.last_legacy_migration will contain the app version that last attempted migration.
* Formatting & linter fixes
* Tests for `chia keys migrate`. Missing a test for incremental migration.
* Additional keyring migration tests
* Formatting updates from black in files unrelated to this branch.
* Revert "Formatting updates from black in files unrelated to this branch."
This reverts commit a85030e8e0ea7406683efd8ae41e224c861e08ff.
* Exit loop if remaining_keys <= 0
* Linter fix? Manually making this change as black doesn't identify any issues locally.
* Linter fix again...
* Rename migrated standalone_wallet wallet db to use '_new.sqlite' suffix
* Removed unnecessary format string
* Wallet DB is now named "v2" instead of "_new"