141
|
Bitcoin / Armory / Re: debian 11/bullseye deps
|
on: November 14, 2021, 08:46:08 AM
|
you're using pyside instead of qt?
PySide2. It's an officially maintained version of Qt5 for Python, but with a less restrictive license than PyQt5. that bypasses the qt version somehow?
It doesn't, I'd have to use PySide6 for Qt6 (there's no PySide 3-4-5, they just went from 2 to 6) it seems that qt4 doesn't exist on debian bullseye
You can build qt4 from source and install locally (look up qt-everywhere). Maybe there's a pyqt4 version on pip that statically links to qt4 and you wouldn't even need to install qt4.
|
|
|
142
|
Bitcoin / Armory / Re: debian 11/bullseye
|
on: November 13, 2021, 09:15:59 PM
|
I'm guessing any psutil functions were rolled into python3 "native" libraries, which doesn't help at all :-/
Got rid of that dependency in the py3 version entirely. It's used to spawn processes and watch over the PIDs for what its worth. to what extent is dev branch at github.com/goatpig/bitcoinarmory usable for everyday stuff?
Unlock wallet flow is a bit busted atm, have to fix it. I suspect the offline signing will throw some exceptions along the way. Nothing design related though, most likely syntax issues (Qt4 doesn't translate 100% into PySide2) and missing imports (I've been refactoring the massive qtdialogs file into a collection of smaller files, in part to get rid of the circular imports). I've signed offline transactions on testnet before but went through some more refactoring lately so I expect some cleanup ahead of me. Could be fixed sometimes in the coming week. That aside, the wallet creation dialogs are probably busted, same with comments (doesn't map over to the new wallet format yet), and the migration dialog from old to new wallets is thread bare. Be warned, the build system isn't super user friendly right now.
|
|
|
143
|
Bitcoin / Armory / Re: Select coin source from 2 different wallets
|
on: November 11, 2021, 10:36:19 AM
|
You can't really do this with current Armory. You'd have to manually manipulate the unsigned transaction or import the priv keys from one wallet to the other. I'll make a not of adding this functionality to the next version.
|
|
|
144
|
Bitcoin / Armory / Re: armory stuck scanning transaction history win10 new wallet
|
on: November 08, 2021, 07:30:20 PM
|
-INFO - 20:09:41.906: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
It would be easier if you presented full logs, it's hard to go off with just this. For now, the line suggests something went wrong when registering addresses with the DB, which is to say that never started scanning in the first place.
|
|
|
145
|
Bitcoin / Armory / Re: Armory 0.96.5
|
on: November 08, 2021, 07:28:22 PM
|
0.96.5 won't be able to spend to native taproot addresses. I'm working to add full support for that address format among other things.
|
|
|
146
|
Bitcoin / Armory / Re: Lost wallet password from 2017
|
on: November 08, 2021, 07:27:00 PM
|
Armory's KDF is particularly resource intensive. Unless you can remember most of your password, you are unlikely to crack the wallet within your lifetime.
|
|
|
147
|
Bitcoin / Armory / Re: chain code validator
|
on: November 05, 2021, 08:14:21 AM
|
By using only the root key in the restore process does that in itself prove the balance is zero?
The chaincode is an integral part of how the addresses are generated, you cant skip it. You mention recreating the chain code from 2 consecutive private keys, but I thought that it was random in the old style wallet.
The chaincode is unique and static for the lifetime of a wallet. 1.35c derives the chaincode from the root key, older versions pull 32 random bytes and use that instead. The chaincode is then used to generate key pairs on the chain. Im not gonna delve in the math but basically to get the privkey N+1, you multiply privkey N by the chaincode. You do the same operation with the public keys. EC maths makes it so that pubkey N will match privkey N, even if you generated pubkey N without ever having knowledge of any private key (that's how we can have deterministic watching only wallets). You cannot divide public keys because that operation does not exist in EC math, so you can't reveal the chaincode by looking at pubkey N and N+1. You can however do that with 2 consecutive private keys, since they are only scalars: priv[N] * chaincode = priv[N+1] <=> chaincode = priv[N+1] / priv[N]
You say there is some way to recreate the chain code?
Unless you have private keys, no. The chaincode for your wallet is a random number, it has no relation to your rootkey, you're going to have to remember it or find an old wallet file with some private keys in it.
|
|
|
148
|
Bitcoin / Armory / Re: chain code validator
|
on: November 04, 2021, 05:14:56 PM
|
also what purpose does the chain code have?
It is clear text data used to generate the address chain. It basically allows the creation of watching only wallets that can derive the addresses without the need to know any private keys. i have a partial chain code
What version is your wallet? 1.35c derives the chaincode from the private key. Old versions use a random chaincode. I'm guessing your wallet is of the former kind (4 lines on the backup instead of 2). That said, with either wallet types, if you have 2 consecutive private keys, you can regenerate the chaincode. hello, is there any test code that i can run to validate a chain code?
There isn't code per se, you'd have to tell me what information you have and I can point to which calls to use to check the chaincode.
|
|
|
150
|
Bitcoin / Armory / Re: Importing extended public key (xpub) into Bitcoin Armory?
|
on: October 13, 2021, 06:30:39 AM
|
Is this possible? This would be useful to have a watch-only wallet while my hardware wallet (which can get me an xpub) is buried in my backyard.
Upcoming version can do this. Working on the GUI for the wallet migration and BIP32 wallet structure next. Current version can't.
|
|
|
152
|
Bitcoin / Armory / Re: Armory 0.96.5
|
on: October 02, 2021, 06:58:40 AM
|
You can send to bech32 addresses (bc1) in 0.96.5. What you cannot do is generate these addresses from Armory wallets.
|
|
|
155
|
Bitcoin / Armory / Re: Step 4: Backup Wallet
|
on: August 24, 2021, 12:24:19 PM
|
This is good info but I'd like to see the whole log file please.
2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1281 - 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1282 - 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1283 - 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************ 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************ 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine: 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1288 - Armory Version : 0.96.5 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1289 - Armory Build: : 8730390989 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1290 - PyBtcWallet Version : 1.35 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1292 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1293 - User home-directory : C:\Users\XXX\AppData\Roaming 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1294 - Satoshi BTC directory : C:\Users\XXX\AppData\Roaming\Bitcoin 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1295 - Armory home dir : C:\Users\XXX\AppData\Roaming\Armory\ 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs : 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1297 - Total Available RAM : 7.91 GB 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1298 - CPU ID string : Intel64 Family 6 Model 42 Stepping 7, GenuineIntel 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1299 - Number of CPU cores : 8 cores 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1300 - System is 64-bit : True 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1301 - Preferred Encoding : cp1256 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1302 - Machine Arch : amd64 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1303 - Available HDD (ARM) : 4 GB 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1304 - Available HDD (BTC) : 4 GB 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1305 - 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py: 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - force_segwit : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - nettimeout : 2 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - rescan : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - force_fcgi : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - ignoreAllZC : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - rescanBalance : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - disableModules : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - port : None 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - interport : 8223 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - coverageOutputDir: None 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - forceWalletCheck: False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - regtest : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - rebuild : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - thread_count : -1 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - datadir : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - clearMempool : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - offline : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - armoryDBDir : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - armorydb_port : 9001 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - satoshiPort : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - disableConfPermis: False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - useTorSettings : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - netlog : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - keypool : 100 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - coverageInclude : None 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - forceOnline : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - disableWalletCheck: False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - redownload : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - rpcBindAddr : 127.0.0.1 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - armorydb_ip : 127.0.0.1 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - multisigFile : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - ram_usage : -1 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - ignoreZC : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - logDisable : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - settingsPath : C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - language : en 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - db_type : DB_FULL 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - doDebug : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - enableDetSign : True 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - mtdebug : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - testnet : False 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - rpcport : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - satoshiHome : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - satoshiRpcport : DEFAULT 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - logFile : C:\Users\XXX\AppData\Roaming\Armory\ArmoryQt.exe.log.txt 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1311 - verbosity : None 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments: 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************ 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt 2021-08-22 17:40:43 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language specified. Defaulting to English (en) 2021-08-22 17:40:43 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en 2021-08-22 17:40:43 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager. 2021-08-22 17:40:43 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 2021-08-22 17:40:43 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data. 2021-08-22 17:40:43 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for 2021-08-22 17:40:43 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed. 2021-08-22 17:40:45 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt 2021-08-22 17:40:45 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings 2021-08-22 17:40:45 (INFO) -- ArmoryQt.py:2120 - Loading wallets... 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 15 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2FW6PfFwV): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2vksCtQ87): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (uRhd3m6X): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2rpbqSLNj): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2Jc6dkLEB): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2J8dm1gP9): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2kGdcor5M): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (PwRgcpgf): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (PMA8UmaF): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (LMBKpBno): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (37cPsFHTD): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (16vgvrTZ): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (8djCjF19): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (2rpibJ2Yo): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:2190 - Wallet (23NCyME2s): "XXXXX " (Encrypted) 2021-08-22 17:40:48 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex... 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done! 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1698 - Changing usermode: 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1699 - From: Advanced 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1707 - To: Advanced 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths 2021-08-22 17:40:49 (ERROR) -- ArmoryQt.py:1862 - Failed to setup SDM Traceback (most recent call last): File "ArmoryQt.py", line 1857, in startBitcoindIfNecessary File "SDM.pyc", line 190, in setupSDM BitcoindError: bitcoind not found 2021-08-22 17:40:49 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0 2021-08-22 17:40:52 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths 2021-08-22 17:40:52 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\XXX\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\XXX\AppData\Roaming\Armory\" --dbdir="C:\Users\XXX\AppData\Roaming\Armory\databases" 2021-08-22 17:40:52 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"' , '--cookie', u'--satoshi-datadir="C:\\Users\\XXX\\AppData\\Roaming\\Bitcoin\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\XXX\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\XXX\\AppData\\Roaming\\Armory\\databases"'] 2021-08-22 17:40:55 (INFO) -- ArmoryQt.py:1824 - Connecting on port 58663 2021-08-22 17:40:55 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1 2021-08-22 17:40:57 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary 2021-08-22 17:40:57 (ERROR) -- ArmoryQt.py:1198 - 18 attempts to load blockchain failed. Remove mempool.bin. 2021-08-22 17:40:57 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted. 2021-08-22 17:40:57 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1 2021-08-22 17:40:57 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:40:58 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:40:59 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:05 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:10 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:16 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:21 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:27 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:41:34 (INFO) -- ArmoryQt.py:1142 - Adding 29 keypress events to the entropy pool 2021-08-22 17:41:34 (INFO) -- ArmoryQt.py:1144 - Adding 1.7 MB bytes of filesystem data to the entropy pool 2021-08-22 17:41:34 (INFO) -- ArmoryQt.py:1146 - Adding 215.6 kB bytes from desktop screenshot to the entropy pool 2021-08-22 17:41:34 (INFO) -- PyBtcWallet.pyc:885 - ***Creating new deterministic wallet 2021-08-22 17:41:34 (INFO) -- PyBtcWallet.pyc:891 - (with encryption) 2021-08-22 17:41:34 (INFO) -- PyBtcWallet.pyc:893 - Target (time,RAM)=(0.250,33554432) 2021-08-22 17:41:43 (INFO) -- PyBtcWallet.pyc:960 - New wallet will be written to: C:\Users\XXX\AppData\Roaming\Armory\armory_iRovMi7q_.wallet 2021-08-22 17:42:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:42:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:42:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:42:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2021-08-22 17:42:26 (INFO) -- ArmoryQt.py:2858 - addWalletToApplication 2021-08-22 17:42:37 (ERROR) -- ArmoryUtils.pyc:3211 - Error in pybkgdthread: dictionary changed size during iteration Traceback (most recent call last): File "armoryengine\ArmoryUtils.pyc", line 3209, in run File "armoryengine\ArmoryUtils.pyc", line 3146, in funcPartial File "ArmoryQt.py", line 5567, in CheckWalletConsistency RuntimeError: dictionary changed size during iteration 2021-08-22 17:42:52 (ERROR) -- Traceback (most recent call last): File "ui\Wizards.pyc", line 127, in initializePage File "ui\Wizards.pyc", line 195, in createNewWalletFromWizard File "ArmoryQt.py", line 2880, in addWalletToApplication File "ArmoryQt.py", line 2723, in walletListChanged File "ArmoryQt.py", line 826, in changeWltFilter File "CppBlockUtils.pyc", line 3068, in updateWalletsLedgerFilter RuntimeError: can't connect socket
2021-08-22 17:42:59 (ERROR) -- Traceback (most recent call last): File "ui\WalletFrames.pyc", line 1118, in clickedDoIt AttributeError: 'WalletBackupFrame' object has no attribute 'wlt'
2021-08-22 17:45:40 (ERROR) -- Traceback (most recent call last): File "ui\WalletFrames.pyc", line 1118, in clickedDoIt AttributeError: 'WalletBackupFrame' object has no attribute 'wlt'
2021-08-22 17:46:13 (ERROR) -- Traceback (most recent call last): File "ui\WalletFrames.pyc", line 1118, in clickedDoIt AttributeError: 'WalletBackupFrame' object has no attribute 'wlt'
Edit: The issue is solved now. I deleted all the files located in AppData\Roaming\Armory. Then opened Armory and created a new wallet. Now, the "Create paper backup" button in step 4 is working fine. It's failing cause it's looking for DB resources as it wants to register the addresses for the wallet that will be generated. I believe this could be fixed by explicitly running Armory in offline mode (start with --offline).
|
|
|
156
|
Bitcoin / Armory / Re: old armory wallet (2011/2012) help
|
on: August 24, 2021, 12:21:04 PM
|
Yeah, what nc50lc said... The earlier versions of the restore process required 4 lines of input... only the 1.35c version is two lines of root key (+ secureprint code, if any). Either, your memory isn't quite correct and your wallet isn't from as long ago as you think... or older roots are also compatible with 1.35c and will work without the chaincode. I don't know if this is actually possible, as like I said, I don't have an older paper backup version to test. paging @goatpig 1.35c derives the chaincode deterministically from the root, hence why it's not part of the backup. If your backup has an explicit chaincode, you need to provide it to restore the wallet. doesn't help me understand why I recognize the wallet id when I only use the root key and without the secure print code.
Why care? Just restore both and check for balance. When in doubt, scattershot. For what it's worth, the only way you can end up in this situation (recognize root without SP password applied) means just that: your root is unencrypted. It's perfectly possible to generate a SP pass for a wallet, then backup the unencrypted root instead, in which case the SP pass is useless.
|
|
|
159
|
Bitcoin / Wallet software / Re: Does any wallet software use the heuristic of adding a dust UTXO in each TX?
|
on: August 18, 2021, 06:19:31 AM
|
Really? Can u have references for that? This goes along very well with my suggestions. . I was also going to add before I saw ur reply, commenting on
Sorry I don't think there is an actual BIP for this. This is an idea that was floated among wallet devs a while back: 1. Merklerize the UTXO set for each new block 2. Commit the merkle root to the block's header 3. Maybe provide an alternate network to grab the full merkle tree per block from. This is debatable. 4. As a miner, modulate tx fees based on added UTXO proof. Originally, committing the utxo tree merkle root to headers was to allow for lightweight UTXO proofs for offline signers (so that they can sign anything without requiring all tx data for each outputs). A corollary use would be to provide proofs for old outputs. Say, miners and nodes only keep UTXOs for the last 3000 blocks in RAM (2 weeks worth). Transactions that spend from these can be use regular fees. Transactions that want to spend older UTXOs need to provide an added merkle proof that the output is spendable. Without the proof, they would have to hike the fee. This allows nodes and miners to segregate older outputs out of the UTXO set in RAM, and comes at a negligible added cost to the transaction signer (they should have the proofs for their own UTXOs pre computed, this is static data for each block). It also improves security for offline signers. Since then, SegWit has mitigated that risk, but there still remains a few attack vectors that can leverage that (get an offline signer to sign anything).
|
|
|
|