BTC update -> reset wallet

[bulhiCzar]

I have updated the version. and my BTC wallet started syncing and the balance disappeared
Server: Sync In Progress (855544 blocks behind). and he was originally filmed. I also lost my balance at 0. I have an old backup.dat file. I tried to upload it to the electron wallet. but the error was falling

[github-actions]

Official Statement from the SHKeeper Development Team

We would like to clarify that the SHKeeper development team consists solely of the following:

• @vsyshost
• @dmytro-samoylenko
• @Olxndr
• @yukonet
• @ikyslyi

It is managed through our official GitHub account https://github.com/vsys-host

We NEVER:

• Share or redirect users to unofficial or suspicious links.
• Request private keys, funds, or other sensitive information.

If you encounter any comments, issues, or users claiming to represent SHKeeper and sharing external links or providing questionable support, please report them immediately. These individuals are not affiliated with the SHKeeper team.

For accurate information and official support, please refer only to:

Our GitHub account: https://github.com/vsys-host/shkeeper.io
Our official SHKeeper website: https://shkeeper.io/
Our official VSYS Host website: https://vsys.host/

Thank you for your understanding and vigilance.

SHKeeper Development Team

[yukonet]

Do not worry — your crypto is still in your wallet.
Is the server sync still in progress?
The sync should have completed by now, and your balance should have returned to its normal state.
Please let us know if the sync is still ongoing or if you are still experiencing any issues.

[bulhiCzar]

I began to notice that my server was running out of memory. occupied +300gb. after updating and syncing BTC

[bulhiCzar]

now +500gb

i think full sync its more 1tb... i dont have this more free space

my config
btc:
enabled: true
mainnet: true
image: vsyshost/bitcoin-shkeeper:1.0.5
legacy:
enabled: true

btc_fullnode:
enabled: true

[bulhiCzar]

kubectl -n shkeeper logs bitcoin-shkeeper-664f8c9989-6qkdw --tail=1000 Defaulted container "app" out of: app, tasks, redis [2025-12-01 23:46:49 +0000] [1] [INFO] Starting gunicorn 20.1.0 [2025-12-01 23:46:49 +0000] [1] [INFO] Listening at: http://0.0.0.0:6000 (1) [2025-12-01 23:46:49 +0000] [1] [INFO] Using worker: gthread [2025-12-01 23:46:49 +0000] [7] [INFO] Booting worker with pid: 7 [2025-12-01 23:46:51,607] WARNING: Get password from shkeeper [2025-12-01 23:46:51,660] ERROR: Exception in main block scanner loop: 'persistent_status' Traceback (most recent call last): File "/app/app/events.py", line 78, in events_listener while not get_account_password(): ^^^^^^^^^^^^^^^^^^^^^^ File "/app/app/unlock_acc.py", line 22, in get_account_password if r['persistent_status'] == "disabled": ~^^^^^^^^^^^^^^^^^^^^^ KeyError: 'persistent_status' [2025-12-01 23:46:51,661] WARNING: Waiting 66 seconds before retry. Copied /root/.bitcoin/shkeeper/wallet.dat → /app/tmp_bitcoind/wallet.dat --> Executing method 'blockcount' with arguments: () --> Calling method 'blockcount' on provider 'bitcoind' (attempt 1) --> Error from provider bitcoind: Request-started --> No result, retrying 1/3 in 2s... --> Calling method 'blockcount' on provider 'bitcoind' (attempt 2) --> Error from provider bitcoind: Request-started --> No result, retrying 2/3 in 2s... --> Calling method 'blockcount' on provider 'bitcoind' (attempt 3) --> Error from provider bitcoind: Request-started --> Failed to get result for blockcount after 3 retries --> list(self.results.values())[0] dict_values([]) 10.42.0.63 - bitcoind-user [01/Dec/2025:23:47:46 +0000] "POST /BTC/status HTTP/1.1" 200 51 "-" "python-requests/2.28.1" [2025-12-01 23:47:50,217] WARNING: Get password from shkeeper [2025-12-01 23:47:50,231] WARNING: Encryption is disabled 10.42.0.63 - bitcoind-user [01/Dec/2025:23:47:50 +0000] "POST /BTC/balance HTTP/1.1" 200 35 "-" "python-requests/2.28.1"

`
btc:
enabled: true
mainnet: true
image: vsyshost/bitcoin-shkeeper:1.0.5
legacy:
enabled: true

btc_fullnode:
enabled: false
`

[dmytro-samoylenko]

Hello,

Looks like you enabled local BTC fullnode in your values.yaml: btc_fullnode.enabled=true. That's why it is consuming your disk space. BTC wallet migration take around 1 hour per 1 year of history, meaning if you BTC wallet were created in 2023, it may take ~2 hours to catch up.

Do you still have an error after deleting btc_fullnode.enabled from values.yaml?

[bulhiCzar]

if i set btc.fullnode=false; btc.legacy=false, btc-shkeker not worked, next logs

if btc.fullnode=false; btc.legacy=true, next logs

and i see btc its offline

also iam use remoute rpc BTC fullnode. i think is work like tron or bnb, just sync bloks, without dowload fullnode

[fatchan]

I think I'm facing the same issue. From the logs, it looks like the "wallet migration failed", but I don't see a specific reason and so it's stuck behind by a lot of blocks:

logs:

10.42.0.155 - bitcoind-user [04/Dec/2025:09:24:56 +0000] "POST /BTC/status HTTP/1.1" 200 43 "-" "python-requests/2.28.1"
[2025-12-04 09:24:59,092] INFO: Wallet migration required, starting migrate_wallet_task...
[2025-12-04 09:24:59,096] INFO: Waiting for migrate_wallet_task to finish (this can take hours)...
[2025-12-04 09:24:59,097] INFO: Migration still in progress... waiting 60s before next check
--> Executing method 'blockcount' with arguments: ()
--> Calling method 'blockcount' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385
--> Executing method 'synced_status' with arguments: ()
--> Calling method 'synced_status' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385

...

10.42.0.155 - bitcoind-user [04/Dec/2025:09:26:41 +0000] "POST /BTC/status HTTP/1.1" 200 43 "-" "python-requests/2.28.1"
10.42.0.155 - bitcoind-user [04/Dec/2025:09:26:50 +0000] "POST /BTC/balance HTTP/1.1" 200 35 "-" "python-requests/2.28.1"
--> Executing method 'blockcount' with arguments: ()
--> Calling method 'blockcount' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385
--> Executing method 'synced_status' with arguments: ()
--> Calling method 'synced_status' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385
10.42.0.155 - bitcoind-user [04/Dec/2025:09:26:51 +0000] "POST /BTC/status HTTP/1.1" 200 43 "-" "python-requests/2.28.1"
[2025-12-04 09:26:59,103] ERROR: Migration failed.
[2025-12-04 09:26:59,119] WARNING: Wallet still not marked as migrated, retrying later...
10.42.0.155 - bitcoind-user [04/Dec/2025:09:27:00 +0000] "POST /BTC/balance HTTP/1.1" 200 35 "-" "python-requests/2.28.1"
--> Executing method 'blockcount' with arguments: ()
--> Calling method 'blockcount' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385
--> Executing method 'synced_status' with arguments: ()
--> Calling method 'synced_status' on provider 'bitcoind' (attempt 1)
--> Success from provider bitcoind: 926385

I don't have the space for a full node, so I believe this runs pruned?:

ethereum_shkeeper:
  extraEnv:
    LAST_BLOCK_LOCKED: "FALSE"
eth_fullnode:
  enabled: false
  mainnet: true
  url: https://--redacted--
eth:
  enabled: true
eth_usdt:
  enabled: true
eth_usdc:
  enabled: true
btc:
  enabled: true
doge:
  enabled: false
ltc:
  enabled: true
monero:
  enabled: true
  fullnode:
    enabled: true
storageClassName: local-path

[ludmildev]

I managed to change the btc BTC_API_SERVER_HOST and it started to sync.. However it stopped due to error:

WARNING btc.py:95 getaddrbytx(): Transaction {txid} response: {'msg': 'txid is not related to any known address', 'status': │
│ ERROR api_v1.py:448 walletnotify(): Exception while processing transaction notification: BTC/{txid} │
│ Traceback (most recent call last): │
│ File "/shkeeper.io/shkeeper/api_v1.py", line 398, in walletnotify │
│ for addr, amount, confirmations, category in crypto.getaddrbytx(txid): │
│ ~~~~~~~~~~~~~~~~~~^^^^^^ │
│ File "/shkeeper.io/shkeeper/modules/classes/btc.py", line 97, in getaddrbytx │
│ for address, amount, confirmations, category in response: │
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ │
│ ValueError: not enough values to unpack (expected 4, got 3)

[dmytro-samoylenko]

@fatchan wallet migration takes place in tasks container, please post tasks logs. Please take a backup of bitcoin-shkeeper db before any further actions:

kubectl -n shkeeper exec -it $(kubectl -n shkeeper get pods | grep maria | grep Running | awk '{print $1}') -- mysqldump -pshkeeper bitcoin-shkeeper > bitcoin-shkeeper.sql

Make sure the command created a non-empty dump bitcoin-shkeeper.sql.

Restart bitcoin-shkeeper using kubectl -n shkeeper rollout restart deploy bitcoin-shkeeper

It is important to take backup before you restart the deployment, as there is a chance that a temporary wallet that was created before wallet migration might already generated addresses.