Topic: restoring old wallets but stuck on database sync (Read 135 times)

Armory reads blockdata from disk. It can do all you describe while Core is not running. You need Core to run to see new incoming blocks and to broadcast your own transactions. You should start it too, the node will display as connected.

bitcoin core downloaded    100%   and yes its over 667GB
 the end of the debug.log file    above this is just all th eother blocks downloading

2024-11-27T19:57:17Z UpdateTip: new best=000000000000000000017174cb87fb8409cb83a146132285b2b39ef9afffd9c5 height=872233 version=0x32000000 log2_work=95.293725 tx=1123742196 date='2024-11-27T19:07:34Z' progress=0.999982 cache=251.7MiB(1823832txo)
2024-11-27T19:57:18Z UpdateTip: new best=000000000000000000014c5c92e93d8f64e9fb19e56f93f425838cab036c8901 height=872234 version=0x3fff0000 log2_work=95.293738 tx=1123746427 date='2024-11-27T19:18:45Z' progress=0.999986 cache=252.5MiB(1831580txo)
2024-11-27T19:57:24Z UpdateTip: new best=00000000000000000001bb965d2798852273dcf0d42ceb03bab1421ec0324dcc height=872240 version=0x2ff18000 log2_work=95.293817 tx=1123763348 date='2024-11-27T19:56:10Z' progress=1.000000 cache=256.5MiB(1860955txo)
2024-11-27T19:59:40Z Saw new header hash=000000000000000000027e858bfb768237a3ce6889f9a7c033336644730fa75d height=872241
2024-11-27T19:59:42Z UpdateTip: new best=000000000000000000027e858bfb768237a3ce6889f9a7c033336644730fa75d height=872241 version=0x2737c000 log2_work=95.293830 tx=1123766113 date='2024-11-27T19:59:02Z' progress=1.000000 cache=256.5MiB(1864543txo)
2024-11-27T20:03:12Z New block-relay-only v1 peer connected: version: 70016, blocks=872241, peer=261
2024-11-27T20:14:10Z New block-relay-only v2 peer connected: version: 70016, blocks=872241, peer=264
2024-11-27T20:15:19Z New block-relay-only v1 peer connected: version: 70016, blocks=872241, peer=266
2024-11-27T20:18:14Z Saw new header hash=00000000000000000002bcfb64f693e34d0392dea6ab7d04e5116824fe1a81a3 height=872242
2024-11-27T20:18:14Z UpdateTip: new best=00000000000000000002bcfb64f693e34d0392dea6ab7d04e5116824fe1a81a3 height=872242 version=0x2b1de000 log2_work=95.293843 tx=1123769825 date='2024-11-27T20:18:01Z' progress=1.000000 cache=257.8MiB(1874230txo)
2024-11-27T20:22:31Z New block-relay-only v1 peer connected: version: 70016, blocks=872242, peer=267
2024-11-27T20:23:12Z Flushed fee estimates to fee_estimates.dat.
2024-11-27T20:23:57Z tor: Thread interrupt
2024-11-27T20:23:57Z opencon thread exit
2024-11-27T20:23:57Z addcon thread exit
2024-11-27T20:23:57Z Shutdown: In progress...
2024-11-27T20:23:57Z torcontrol thread exit
2024-11-27T20:23:57Z net thread exit
2024-11-27T20:23:57Z msghand thread exit
2024-11-27T20:23:57Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-11-27T20:23:57Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-11-27T20:23:57Z scheduler thread exit
2024-11-27T20:23:57Z Writing 4042 mempool transactions to file...
2024-11-27T20:23:57Z Writing 0 unbroadcast transactions to file.
2024-11-27T20:23:57Z Dumped mempool: 0.002s to copy, 0.021s to dump, 2546324 bytes dumped to file
2024-11-27T20:23:57Z Flushed fee estimates to fee_estimates.dat.
2024-11-27T20:23:59Z Shutdown: done


installed armory .965
launched the armory.db       it said that the  %appdata%/roaming/armory   did exist so i closed  it
launched armoryqt     an my logs started to capture

bitcoin debug.log

2024-11-27T20:29:28Z Bitcoin Core version v28.0.0 (release build)
2024-11-27T20:29:28Z Script verification uses 7 additional threads
2024-11-27T20:29:28Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-11-27T20:29:29Z Using RdSeed as an additional entropy source
2024-11-27T20:29:29Z Using RdRand as an additional entropy source
2024-11-27T20:29:29Z Default data directory C:\Users\hplaptop\AppData\Roaming\Bitcoin
2024-11-27T20:29:29Z Using data directory C:\Users\hplaptop\AppData\Roaming\Bitcoin
2024-11-27T20:29:29Z Config file: C:\Users\hplaptop\AppData\Roaming\Bitcoin\bitcoin.conf
2024-11-27T20:29:29Z Config file arg: rpcpassword=****
2024-11-27T20:29:29Z Config file arg: rpcuser=****
2024-11-27T20:29:29Z Setting file arg: listen = true
2024-11-27T20:29:29Z Setting file arg: wallet = []
2024-11-27T20:29:29Z Command-line arg: datadir="C:\\Users\\hplaptop\\AppData\\Roaming\\Bitcoin"
2024-11-27T20:29:29Z Using at most 125 automatic connections (2048 file descriptors available)
2024-11-27T20:29:29Z scheduler thread start
2024-11-27T20:29:29Z Binding RPC on address ::1 port 8332
2024-11-27T20:29:29Z Binding RPC on address 127.0.0.1 port 8332
2024-11-27T20:29:29Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2024-11-27T20:29:29Z Starting HTTP server with 4 worker threads
2024-11-27T20:29:29Z Using wallet directory C:\Users\hplaptop\AppData\Roaming\Bitcoin
2024-11-27T20:29:29Z init message: Verifying wallet(s)…
2024-11-27T20:29:29Z Using /16 prefix for IP bucketing
2024-11-27T20:29:29Z init message: Loading P2P addresses…
2024-11-27T20:29:29Z Loaded 64449 addresses from peers.dat  138ms
2024-11-27T20:29:29Z init message: Loading banlist…
2024-11-27T20:29:29Z SetNetworkActive: true
2024-11-27T20:29:29Z Script verification uses 7 additional threads
2024-11-27T20:29:29Z Cache configuration:
2024-11-27T20:29:29Z * Using 2.0 MiB for block index database
2024-11-27T20:29:29Z * Using 8.0 MiB for chain state database
2024-11-27T20:29:29Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-11-27T20:29:29Z Using obfuscation key for blocksdir *.dat files (C:\Users\hplaptop\AppData\Roaming\Bitcoin\blocks): '0000000000000000'
2024-11-27T20:29:29Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-11-27T20:29:29Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-11-27T20:29:29Z init message: Loading block index…
2024-11-27T20:29:29Z Assuming ancestors of block 000000000000000000011c5890365bdbe5d25b97ce0057589acaef4f1a57263f have valid signatures.
2024-11-27T20:29:29Z Setting nMinimumChainWork=000000000000000000000000000000000000000088e186b70e0862c193ec44d6
2024-11-27T20:29:29Z Opening LevelDB in C:\Users\hplaptop\AppData\Roaming\Bitcoin\blocks\index
2024-11-27T20:29:29Z Opened LevelDB successfully
2024-11-27T20:29:29Z Using obfuscation key for C:\Users\hplaptop\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2024-11-27T20:29:33Z LoadBlockIndexDB: last block file = 4632
2024-11-27T20:29:33Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=32, size=52576079, heights=872203...872242, time=2024-11-27...2024-11-27)
2024-11-27T20:29:33Z Checking all blk files are present...
2024-11-27T20:29:34Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-11-27T20:29:34Z Opening LevelDB in C:\Users\hplaptop\AppData\Roaming\Bitcoin\chainstate
2024-11-27T20:29:38Z Opened LevelDB successfully
2024-11-27T20:29:38Z Using obfuscation key for C:\Users\hplaptop\AppData\Roaming\Bitcoin\chainstate: 2f50e7963d6ac991
2024-11-27T20:29:38Z Loaded best chain: hashBestChain=00000000000000000002bcfb64f693e34d0392dea6ab7d04e5116824fe1a81a3 height=872242 date=2024-11-27T20:18:01Z progress=0.999996
2024-11-27T20:29:38Z Opening LevelDB in C:\Users\hplaptop\AppData\Roaming\Bitcoin\chainstate
2024-11-27T20:29:38Z Opened LevelDB successfully
2024-11-27T20:29:38Z Using obfuscation key for C:\Users\hplaptop\AppData\Roaming\Bitcoin\chainstate: 2f50e7963d6ac991
2024-11-27T20:29:38Z [Chainstate [ibd] @ height 872242 (00000000000000000002bcfb64f693e34d0392dea6ab7d04e5116824fe1a81a3)] resized coinsdb cache to 8.0 MiB
2024-11-27T20:29:38Z [Chainstate [ibd] @ height 872242 (00000000000000000002bcfb64f693e34d0392dea6ab7d04e5116824fe1a81a3)] resized coinstip cache to 440.0 MiB
2024-11-27T20:29:38Z init message: Verifying blocks…
2024-11-27T20:29:38Z Verifying last 6 blocks at level 3
2024-11-27T20:29:38Z Verification progress: 0%
2024-11-27T20:29:40Z Verification progress: 16%
2024-11-27T20:29:41Z Verification progress: 33%
2024-11-27T20:29:42Z Verification progress: 50%
2024-11-27T20:29:43Z Verification progress: 66%
2024-11-27T20:29:43Z Verification progress: 83%
2024-11-27T20:29:44Z Verification progress: 99%
2024-11-27T20:29:44Z Verification: No coin database inconsistencies in last 6 blocks (16587 transactions)
2024-11-27T20:29:44Z  block index           14727ms
2024-11-27T20:29:44Z Setting NODE_NETWORK on non-prune mode
2024-11-27T20:29:44Z block tree size = 872243
2024-11-27T20:29:44Z nBestHeight = 872242
2024-11-27T20:29:44Z initload thread start
2024-11-27T20:29:44Z Loading 4042 mempool transactions from file...
2024-11-27T20:29:44Z torcontrol thread start
2024-11-27T20:29:44Z Leaving InitialBlockDownload (latching to false)
2024-11-27T20:29:44Z Bound to 127.0.0.1:8334
2024-11-27T20:29:44Z Bound to [::]:8333
2024-11-27T20:29:44Z Bound to 0.0.0.0:8333
2024-11-27T20:29:44Z Loaded 2 addresses from "anchors.dat"
2024-11-27T20:29:44Z 2 block-relay-only anchors will be tried for connections.
2024-11-27T20:29:44Z init message: Starting network threads…
2024-11-27T20:29:44Z net thread start
2024-11-27T20:29:44Z init message: Done loading
2024-11-27T20:29:44Z msghand thread start
2024-11-27T20:29:44Z addcon thread start
2024-11-27T20:29:44Z dnsseed thread start
2024-11-27T20:29:44Z opencon thread start
2024-11-27T20:29:44Z Waiting 300 seconds before querying DNS seeds.
2024-11-27T20:29:44Z Progress loading mempool transactions from file: 10% (tried 405, 3637 remaining)
2024-11-27T20:29:44Z Progress loading mempool transactions from file: 20% (tried 809, 3233 remaining)
2024-11-27T20:29:45Z Progress loading mempool transactions from file: 30% (tried 1213, 2829 remaining)
2024-11-27T20:29:45Z Progress loading mempool transactions from file: 40% (tried 1617, 2425 remaining)
2024-11-27T20:29:45Z New block-relay-only v1 peer connected: version: 70016, blocks=872243, peer=1
2024-11-27T20:29:45Z Progress loading mempool transactions from file: 50% (tried 2021, 2021 remaining)
2024-11-27T20:29:46Z Saw new header hash=0000000000000000000182aa6a4b6ee544f149d128a05dcb58b34e85edd4f99d height=872243
2024-11-27T20:29:46Z New block-relay-only v2 peer connected: version: 70016, blocks=872243, peer=2
2024-11-27T20:29:46Z Progress loading mempool transactions from file: 60% (tried 2426, 1616 remaining)
2024-11-27T20:29:46Z Progress loading mempool transactions from file: 70% (tried 2830, 1212 remaining)
2024-11-27T20:29:46Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=3
2024-11-27T20:29:46Z Progress loading mempool transactions from file: 80% (tried 3234, 808 remaining)
2024-11-27T20:29:47Z Progress loading mempool transactions from file: 90% (tried 3638, 404 remaining)
2024-11-27T20:29:47Z Imported mempool transactions from file: 4042 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-11-27T20:29:47Z initload thread exit
2024-11-27T20:29:50Z UpdateTip: new best=0000000000000000000182aa6a4b6ee544f149d128a05dcb58b34e85edd4f99d height=872243 version=0x20c00000 log2_work=95.293856 tx=1123772628 date='2024-11-27T20:25:33Z' progress=0.999998 cache=2.5MiB(18013txo)
2024-11-27T20:29:50Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=4
2024-11-27T20:29:50Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=5
2024-11-27T20:29:55Z P2P peers available. Skipped DNS seeding.
2024-11-27T20:29:55Z dnsseed thread exit
2024-11-27T20:29:56Z New outbound-full-relay v2 peer connected: version: 70016, blocks=872243, peer=6
2024-11-27T20:30:03Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=7
2024-11-27T20:30:14Z New outbound-full-relay v2 peer connected: version: 70016, blocks=872243, peer=8
2024-11-27T20:30:14Z New outbound-full-relay v2 peer connected: version: 70016, blocks=872243, peer=10
2024-11-27T20:30:34Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=11
2024-11-27T20:30:35Z New outbound-full-relay v2 peer connected: version: 70016, blocks=872243, peer=12
2024-11-27T20:30:41Z New block-relay-only v1 peer connected: version: 70016, blocks=872243, peer=13
2024-11-27T20:31:17Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=16
2024-11-27T20:31:23Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=17
2024-11-27T20:31:40Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=18
2024-11-27T20:31:41Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=19
2024-11-27T20:32:11Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=20
2024-11-27T20:32:11Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=21
2024-11-27T20:32:42Z New outbound-full-relay v1 peer connected: version: 70016, blocks=872243, peer=22
2024-11-27T20:33:13Z New outbound-full-relay v1 peer connected: version: 70015, blocks=872243, peer=24
2024-11-27T20:33:18Z New outbound-full-relay v2 peer connected: version: 70016, blocks=872243, peer=23
2024-11-27T20:43:39Z Saw new header hash=000000000000000000014a53016dae4743496c7ccc7699002a2f05c97d79fa6b height=872244
2024-11-27T20:43:41Z UpdateTip: new best=000000000000000000014a53016dae4743496c7ccc7699002a2f05c97d79fa6b height=872244 version=0x20800000 log2_work=95.293869 tx=1123776009 date='2024-11-27T20:43:01Z' progress=1.000000 cache=4.8MiB(35398txo)
2024-11-27T20:49:51Z New block-relay-only v1 peer connected: version: 70016, blocks=872244, peer=25



armory dblog.log


Log file opened at 14:29:34.000: C:\Users\hplaptop\AppData\Roaming\Armory\dbLog.txt
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: C:\Users\hplaptop\AppData\Roaming\Bitcoin\blocks
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\hplaptop\AppData\Roaming\Armory\databases
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 14:29:34.000: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 53641
-INFO  - 14:29:36.140: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: dcd46b3493683e6833f8
-INFO  - 14:29:44.609: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node

armory.log

2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1281 -
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1282 -
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1283 -
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.22621--Multiprocessor Free
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\hplaptop\AppData\Roaming
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\hplaptop\AppData\Roaming\Bitcoin
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\hplaptop\AppData\Roaming\Armory\
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 7.65 GB
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : Intel64 Family 6 Model 140 Stepping 1, GenuineIntel
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 8 cores
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 152 GB
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 152 GB
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1305 -
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\hplaptop\AppData\Roaming\Armory\ArmorySettings.txt
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\hplaptop\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\hplaptop\AppData\Roaming\Armory\ArmorySettings.txt
2024-11-27 14:29:04 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2024-11-27 14:29:04 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2024-11-27 14:29:04 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2024-11-27 14:29:04 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background.  
2024-11-27 14:29:04 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2024-11-27 14:29:04 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2024-11-27 14:29:04 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2024-11-27 14:29:06 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\hplaptop\AppData\Roaming\Armory\ArmorySettings.txt
2024-11-27 14:29:06 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2024-11-27 14:29:06 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2024-11-27 14:29:06 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 0
2024-11-27 14:29:25 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1513 - URL-register action: DoIt
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1516 - Registering Armory  for current user
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1526 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1526 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\URL Protocol
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1526 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1526 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\open\
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1538 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\open\command\
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1538 -    Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\DefaultIcon\
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1699 -    From: Advanced
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1707 -      To: Advanced
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2024-11-27 14:29:27 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2024-11-27 14:29:27 (INFO) -- SDM.pyc:254 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2024-11-27 14:29:27 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2024-11-27 14:29:27 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2024-11-27 14:29:27 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2024-11-27 14:29:27 (INFO) -- SDM.pyc:175 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2024-11-27 14:29:27 (INFO) -- SDM.pyc:340 - Called startBitcoind
2024-11-27 14:29:28 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=C:\Users\hplaptop\AppData\Roaming\Bitcoin
2024-11-27 14:29:28 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\hplaptop\\AppData\\Roaming\\Bitcoin']
2024-11-27 14:29:28 (INFO) -- SDM.pyc:451 - PID of bitcoind: 6076
2024-11-27 14:29:28 (INFO) -- SDM.pyc:452 - PID of armory:   3640
2024-11-27 14:29:28 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\guardian.exe', '3640', '6076']
2024-11-27 14:29:32 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2024-11-27 14:29:32 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\hplaptop\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\hplaptop\AppData\Roaming\Armory\" --dbdir="C:\Users\hplaptop\AppData\Roaming\Armory\databases"
2024-11-27 14:29:32 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\hplaptop\\AppData\\Roaming\\Bitcoin\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\hplaptop\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\hplaptop\\AppData\\Roaming\\Armory\\databases"']
2024-11-27 14:29:36 (INFO) -- ArmoryQt.py:1824 - Connecting on port 53641
2024-11-27 14:29:36 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2024-11-27 14:29:37 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2024-11-27 14:29:37 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2024-11-27 14:29:37 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-11-27 14:29:37 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode


armorycpp.log



Log file opened at 14:29:04.000: C:\Users\hplaptop\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 14:29:47.906: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 14:29:47.906: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:359) POLLERR error in readAndWrite


i dont have any walley loaded in bitcoin core nor ARMORY yet

and i sit at  on the armory GUI    preparing database
so i say there for 1 hour  and nothing progressed in any log except the debug.log  showing more downloaded blokces and they came from the network

so i shutdown armory  and this was in the DB.log
2024-11-27 15:52:50 (INFO) -- ArmoryQt.py:5477 - BDM is safe for clean shutdown
2024-11-27 15:52:50 (INFO) -- SDM.pyc:465 - Called stopBitcoind
2024-11-27 15:52:53 (ERROR) -- SDM.pyc:491 - can't connect socket
2024-11-27 15:52:55 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!


then started only armory.db   and its updating my db.log  and shows the below


Log file opened at 15:54:07.000: C:\Users\hplaptop\AppData\Roaming/Armory/dbLog.txt
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: C:\Users\hplaptop\AppData\Roaming/Bitcoin/blocks
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\hplaptop\AppData\Roaming/Armory/databases
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 15:54:07.000: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 9001
-INFO  - 15:54:13.109: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 15:54:14.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 15:54:14.375: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 15:54:14.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 15:54:14.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 15:54:17.797: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #6
-INFO  - 15:54:17.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #7
-INFO  - 15:54:20.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #15
-INFO  - 15:54:24.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #23
-INFO  - 15:54:28.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #27

more 56-   all the way till this

-INFO  - 16:29:47.469: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4605
-INFO  - 16:29:51.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4613
-INFO  - 16:29:55.625: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4621
-INFO  - 16:29:59.640: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4629
-INFO  - 16:30:12.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4630
-INFO  - 16:30:22.234: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4632
-INFO  - 16:30:26.015: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 16:30:29.187: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 3s
-INFO  - 16:30:35.765: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 2181s
-INFO  - 16:30:35.859: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 16:30:35.875: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 16:30:38.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 16:30:38.797: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking


so nothing else is showing in the DB window    
so i waited 30  min   and launched  armory   and i now see  block chain now complete  :O)
your balance and transaction are now on the transactions tab


SO looks like i have progress and can now add my wallets
i restored my wallets      and have   the balances

it does show NODE offline with 872252 block in brown right bottom corner    
so i guess i can say i am connected and  all it up and running

with ARMORY ONLINE on the DASHBOARD   and saying node OFFLINE bottom right but  with the BLOCKs showing a value and the dollar amounts showing as well.


thanks for the help !!!

You also need to delete the databases folder created by ArmoryDB if you change the underlying blockdata structure

You may encounter a compatibility issue with the blockchain saved by that version since it will store "blk.dat" files with non-zero XOR-key.
That's only if it didn't detected an existing blocks directory.

If it did, unfortunately, you'll have to set blocksxor=0 to your 'bitcoin.conf' file or command line arg and restart with a fresh datadir.
Or downgrade Bitcoin Core 1 version lower then redownload the blockchain.

I decided to start fresh re-download the complete block chain   using bitcoin core  v28   im at 80% complete
next ill close down bitcoin core
next launch .965 Armorydb from folder  and let it do it tasks
then after complete load the armoryqt
then see what ill end up with

This step is supposed to complete in a few minutes tops. You can post your whole logs by feeding a text file to pastebin and posting the link to that here. I'd prefer to look at full logs. Once that step completes, you can start ArmoryDB.

That'll work per address, but not the whole wallet.
If you want to check the whole wallet's balance, you should check all of that wallet's addresses.

And since it's not synced, you should also check all of its 'unused addresses' (Include Unused) in "Wallet Properties->Backup This Wallet->Export Key Lists".
That includes reserved 'Change Addresses' that you may have used in the past.

(mempool.space in particular has reliable data IMO)

my main goal was to see if i really had any bitcoin in my wallets.. forgot if i had some    after more reading    is it true that i can simply go to https://mempool.space  and with my address   of each wallet ( which Armory gave me  RECEIVING ADDRESS)  put in mempool search and it immediate shows my balance  of the complete wallet ??


BTC

Regarding Bitcoin Core;
Those lines are pertaining to your Bitcoin Core node's "mempool" and "mempool.dat" file on disk and has little to do with the issue with Armory.
The number that you're seeing is normal since it's being updated as it accept unconfirmed transactions from its peers and drop when verification fails or when already included to a block.

Instead, you can check for corrupted data with errors related to chainstate/block/index.
Bitcoin Core will label those with "error" after the line's timestamp.

This wont affect your Bitcoin Core's blockchain and will not certainly force you to redownload the blockchain.
That's unless you've enabled "Prune block storage to" setting or prune=n arg/config,
In that case, a rescan attempt will force Bitcoin Core to re-download all the pruned blocks starting from scratch.

being it took 3 days over fiber to download   the whole block    ill do the re build as last resort    so i did try the armorydb 1st      and looks like  have more progress for i have never seen the below in logs


-INFO  - 08:45:57.093: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 08:45:57.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 08:45:57.406: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 08:45:57.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 08:45:57.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 08:45:59.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #0
-INFO  - 08:46:01.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #6
...    all the way up to this
-INFO  - 09:21:45.422: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4597
-INFO  - 09:21:49.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4601
-INFO  - 09:21:50.234: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4605
-INFO  - 09:21:54.765: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4609
-INFO  - 09:21:54.031: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4613
-INFO  - 09:21:58.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4621
-INFO  - 09:22:03.500: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4625
-INFO  - 09:22:07.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4626
-INFO  - 09:22:30.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4628
-INFO  - 09:22:33.984: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
the above line running for 4 hours now   cpu is at 30%  for the db  

do you know how long it will be on this  Organizing  chain ? 4 hours so far
my database/txfilters = 4GB  and hasnt changed timestamp   since 4 hours ago  when it showed in the logs

1. Stick to Armory 0.96.5, you mentioned 0.94 and 0.95 in your post, don't use those.
2. Start Bitcoin Core on its own, let it complete the blockchain download. Check that your blockchain folder is 600GB+.
3. Since you're having trouble, start Bitcoin Core yourself before starting Armory. It will find your instance of Core.
4. If the database building phase get stuck, start ArmoryDB manually (from the command line) and let it do its thing, then start ArmoryQt on top of it. It will find the db instance and take it from there.

Also post logs, makes it easier to help you.

DETAILS :
I have armory  wallet from 2016 that im restoring (yes forgot all about it till now )  guess 90grand per coin is the reason.  not sure what version armory was on for that drive crashed  but i have a backup paper copy of my 2 wallets. . I see that its a 2 line code 1.35c version  . I also read that i have to download the whole bitcoin chain with  bitcoin core and or armory to review my balance ( might be wrong on that ) anyways i have downloaded the complete  665GB worth   but i do have to say i   used both bitcoin core version 27  to download  90% of it  and then used the Armory .94   for the remaining 10 %    i dont know why i did that but hope they were compatible . I used the standard  settings  on both  so files are in the APPDATA folder. .  

Armory did except the paper backup  values on my restore   and they match my wallet IDs  , they are listed in armory

WONDERING:
Did i corrupt the download  using both to download the chain and blocks  and have to do it all over again?    
Armory doesnt show a balance  just 3 dots in the balance, it should be at least show ZERO if no balance  right ?
I read about electrum to import the base 58 keys from each armory wallet export, using the no space and  all unused  settings .  
I know about the Base58  keys  and i have them with no spaces exported ,   did a import  in electrum   but nothing shows up in their either


MY ISSUE:
 Armory never gets out of the offline mode bottom right corner ,  never  get out of the initialization bitcoin engine. (well its green solid  bar) maybe that means done in version .95
 Building DATABASE  is blank and its spinning the green white circle   to the right
Scan transaction history is blank 0%
my Balance only shows 3 dots      no 0.00       So i suspect something is broken
I have tried the restan balance
i have tried the rescan database
i have let my  laptop run for over 48 hours  , 3.3gz , hard drive is NVME M.2 so its fast
I know the Rbuild and rescan will wipe all my blocks and chain an force me to redownload the 670GB  all over again . so dont want to if i dont have to


FROM the DEBUG
i see this and wonder if my downloads are bad  but this changes after i close  and re open armory multiple time
Imported mempool transactions from file: 506 succeeded, 5434 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-11-25T07:18:56Z Imported mempool transactions from file: 4054 succeeded, 4397 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-11-25T07:41:05Z Writing 10213 mempool transactions to file...Imported mempool transactions from file: 4054 succeeded, 4397 failed,
upgraded to 96.5
see this
2024-11-25T08:00:33Z Imported mempool transactions from file: 10213 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast


MY REQUEST
 how can i verify i have  a good restore  and the verify the balance  is accurate ?.
How can i tell from the DEBUG  armory is not stalling out on some type of error?
do i need to re download  using maybe latest  Armory .96.5

i just read i should download the complete blockchain , then add wallets on restore     i may not have done in that order is it that critical ?
if i have to re do it all over  due my dumbness   what is the best order .. ?


thanks