In the History-tab there is no new transactions...
Is your wallet synced? Is the circle at bottom left corner of the window green? If the circle is not green, that means that there's a problem with electrum connection to internet. You can also check if they have sent bitcoin using block explorers. Go to blockchair.com and enter the address you gave them. Do you see any transaction there? |
|
|
|
|
Recently, I have problem with Exodus when using the desktop version even after upgrading to the latest version which was released a few days ago.
But on Android, whether I use VPN or not, it works well. The wallet is synced and I should be able to make transactions.
|
|
|
|
Also, what is KYC?
KYC stands for Know Your Customer. In many of exchanges, KYC is mandatory. That means that you have to verify your identity to be able to use their service. Note that some exchanges may allow you to make a deposit and don't ask you to verify your identity until you request a withdrawal. Therefore, you should always read the terms and conditions of the exchange before you make a deposit. |
|
|
|
Can that be extracted somehow? Am I currently safe?
All your private keys can be derived from your seed phrase, but it's not possible to derive the seed phrase from the private key. If one of your private keys has been compromised, other private keys are safe. I read your previous posts in this thread, but I didn't get whether you have generated a new wallet or not. As already suggested by others, create a new wallet with a new seed phrase, move all your fund to that and don't use the old wallet anymore. In this way, you will be sure that you will never use the address corresponding to the compromised private key. |
|
|
|
How can we possibly tell that there is a possibility that a wallrt service has the info of our seed phrases on their database? Is it because of they being open-source/close-source? Does being closed means that they're the only one that fully knows what the codes are so they can hide something?
If the wallet is close-source, there is no way to know that. They may claim that they have no access to users keys, but there's no guarantee that they tell the truth. If the wallet is open-source, one can read the code and know whether the keys are stored on their server or not. |
|
|
|
I will be switching to the Mew wallet because my dad recommend it to me. Its decentralized so the keys are stored on your device. I think this is my best bet because then I can manually backup my keys in a encrypted file on my computer.
With storing the keys on your device, you don't make your wallet secure. If the wallet has been created using an online tool or the keys are stored on an online device, there's the risk of getting hacked.
Download a wallet that doesn't have any terms of service requirements instead, crypto wallets should be fully decentralized like trust wallet, if any wallet is asking to pass any terms of service they have your private keys believe me
There is no guarantee that trustwallet doesn't have access to your private keys (or your seed phrase). Trustwallet is close-source and we don't know whether the keys are stored on their server or not. |
|
|
|
|
The profile you are referring to belongs to Cyrus.
If Cyrus posts in boards moderated by him (Marketplace, trading discussion, Romānă (Romanian) and Other languages/locations), the last coin is displayed in red.
If Cyrus posts in any other board, the last coin is displayed in faded-out green.
|
|
|
|
The Bitcoin Cash still appears in another wallet as an imported address, watching only. Any suggestions?
Note that even if you import the wallet into Electron Cash successfully, the watch-only wallet will still show the balance. By importing the seed phrase into a new wallet, you don't move the fund to a new wallet. You can have multiple same wallets at a same time while all of them show the balance. The m/44'/145'/0' is only used for "new" Bitcoin Cash wallets. ie. ones created after the fork.
Thanks for the correction. I do leave spaces between the seed words don't I?
Yes, use space between the words. Word1 Word2 Word3 ...................... |
|
|
|
Anyway to access the btc without having to download the blockchain??
You can export your private key and import it into a SPV wallet like electrum. In SPV wallets, you don't have to download the blockchain. For exporting your private key(s) from Armory, you can follow the guide the provided by HCP. (Click here) In electrum, create a new wallet, select "Import bitcoin addresses or private keys" and then enter your private keys. Warning:
Download electrum only from its official website and do not forget to verify your download. |
|
|
|
Every private key can generate three types of addresses. Legacy: Addresses starting with 1 Nested Segwit: Addresses starting with 3 Native Segwit: Addresses starting with bc1 bitaddress.org only supports legacy addresses. imtoken has probably generated another type of address.
Meaning: I wonder why imToken generated nested segwit address, I later noticed it does not support legacy and native segwit addresses, even if you generate Bitcoin wallet on imToken, the address will start from 3 which is nested segwit.
I just installed imtoken on my android phone to see how it works. It allows users to have legacy addresses as well. To OP: If you want to have a legacy address on imtoken, tap on 3-dots button (Shown in the image below).  After that, tap on "Advanced" and then "Toggle Address Type". Select "General". Note that it's not recommended to use legacy addresses. You will have to pay higher fee when sending from legacy addresses. It would better to use native segwit addresses (which is not supported by imtoken, of course) |
|
|
|
|
Since Exodus is close-source, there is no way to know whether they are technically able to block you from accessing your wallet or not. But even if you can't access your wallet on Exodus for any reason, you will be able to access your fund using your seed phrase (the series of 12 words that you should have saved) in other wallets.
Note that this doesn't mean Exodus is 100% secure. There's the possibility that your keys are stored on their server.
|
|
|
|
Afaik they can't cost you more than the fees you pay to attempt to swap it unless they have access to your machine or something.
Such tokens are usually sent for advertising purposes and you won't lose anything other than the transaction fee when swapping them. But that hasn't always been the case. Read the following article for more information. Creative attacker steals $76,000 in RUNE by giving out free tokens |
|
|
|
You can user trust wallet Instead in your phone.
You shouldn't prefer trustwallet to electrum, just because it's more user-friendly. Electrum is open-source and trustwallet is close-source. When you use trustwallet, there is no way to know whether your keys are stored on their server or not. Electrum also allow you to make a transaction without your keys touching the internet. Being open-source and the ability of signing a transaction without being online are much more important than being more user-friendly. |
|
|
|
OK. I'll have to do that tomorrow as I access my Blockchain from another computer which is elsewhere. I can't remember seeing any 'private key' in the blockchain wallet? Just the address.
For exporting the wallet from blockhchain.com, you can use the seed phrase. In blockchain.com, click on "Security" at top of the page. After that click on "Backup Funds" and then "View Secret Private Key Recovery Phrase" . You will see a series of 12 words which is your seed phrase. The seed phrase can be used for recovering both bitcoin and bitcoin cash. For bitcoin, Use Electrum. Create a new wallet. Select "Standard wallet" and then "I already have a seed". Click on "Options", check BIP39 and click on "OK". Paste your seed phrase and click on "Next". In the new window, select "Legacy" if your addresses start with 1 and "Native segwit" if they start with bc1q. For bitcoin cash, use Electron Cash. Standard wallet > I already have a seed. Options > Check "Force BIP39 interpretation of this seed". Leave the derivation path as default (m/44'/145'/0') Change the derivation path to m/44'/0'/0'. ( Thanks HCP for the correction.) If you have both bitcoin and bitcoin cash, for more security, move your bitcoin before trying to move bitcoin cash or other forks. |
|
|
|
It also says, 'imported address, watching only' if that's of any help?
That means that you imported the address instead of the private key and made a watch-only wallet. Note that it's impossible to spend fund from a watch-only wallet. Create a new wallet (File > New/Restore) and import the private key (not the address) this time. |
|
|
|
I want to leave them there for the time being but I hope to send them to my Coinbase wallet later on. Do you need to save this or just quit or what?
You can safely close it. No need to do anything. Whenever you want to spend the fund, you can open the wallet and make a transaction. Note that as long as you have the private key(s), there is nothing to worry about. Even if you lose the wallet file, you can recover your wallet using the private key(s). |
|
|
|
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. |
|
|
|
Post armorylog.txt found in ~/AppData/Roaming/Armory. This should have some relevant error verbose.
Once I click on "Create Paper backup" button, the following error is added to the armorylog.txt file. 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' |
|
|
|
|
Username: hosseinimr93
Post Count: 2461
BTC Address (must be SegWit): bc1q89wyt7en7hxr5jc4jdnxlw4vzmapp90e8jlr25
|
|
|
|
|
Show Posts
