Ok, shutdown Armory and Bitcoin Core and add the following line to your bitcoin.conf file: Then try this: 1. Delete the Armory log files (armorylog.txt and dbLog.txt) 2. Reboot your PC (this will clear any ghost processes that might be preventing things from running normally) 3. Start Armory If it's still showing as "offline", try the "Help -> Rebuild and rescan databses" option in Armory. Then shut Armory down and restart it. If it still isn't working properly after that, repost the latest copy of your log files. |
|
|
|
Was it safe to update your electrum to Electrum-4.0.7?
I have not had any issues with 4.0.7. I verified the digital signatures OK and it's running fine. It appears to be working just fine with my local "electrs" Electrum server as well. As the others have said, make sure you're downloading from electrum.org and then verify the digital signatures before installing and you'll be OK  |
|
|
|
What is the point of going through with this process if you have to send KYC?
If you don't register, you can guarantee that you won't be getting anything back... to register your claim, you have to complete the KYC process... So, you'll need to weigh up whether your "privacy" is worth more to you than the amount of "loss" you'll suffer by not completing the claim registration. |
|
|
|
I don't think it being specific to Trezor plugin follows from what I said. I used a completely different wallet that signed and broadcasted with Trezor completely outside of electrum. And even PSBT signing with electrum did not work.
I meant the Electrum Trezor plugin... Hardware Wallet support in Electrum is achieved through the use of plugins, specific to each brand of device: https://github.com/spesmilo/electrum/tree/master/electrum/pluginsSo, given it works "completely outside of electrum", it would indicate that it's not an issue with the device itself... and it's not an issue that seems to be within "core" Electrum either (haven't heard of similar issues with "normal" wallets etc)... so my guess would be something within the Electrum plugin for the Trezor. |
|
|
|
Everything looks like it is running OK... insofar that Armory is finding the Bitcoin Core blocks folder and scanning/parsing all the blocks etc. So that's a good start. Are you running Bitcoin Core manually first, then starting Armory? Or do you have Armory configured to manage Bitcoin Core ("Let Armory run Bitcoin Core/bitcoind in the background")?  One thing you might need is to make sure that Bitcoin Core has the following entry in the bitcoin.conf file: I've had issues with Windows where Armory is unable to communicate with the Bitcoin Core node if this setting is not included in the bitcoin.conf file. |
|
|
|
I'm with bob123 on this one... Windows 7 just should not be used today. Attempting all sorts of "hacks" and "workarounds" to try and make Electrum run on Windows 7 is just a "Bad Idea"™, in my opinion. You'd be much better off either upgrading to Windows 10 where Electrum will just work without any issues... or installing a current version of Linux (or even using a Linux Live OS on a USB stick). I suppose, you could even just install a VM like "Virtual Box" ( https://www.virtualbox.org/) and install Linux on that if you get really desperate... but that is basically a "workaround" for running Electrum on Windows 7 and, again, isn't a good idea for long term use. |
|
|
|
I am on macOs Big Sur, the wallet is Trezor hardware wallet, P2WKH in P2SH (3... segwit addr), no other keys were manually imported or anything non standard (except for increased gap limit).
Possibly some obscure Trezor/Electrum Plugin issue? Next time try using the actual Trezor wallet ( https://wallet.trezor.io/) to create/send a transaction as opposed to trying to create/send using Electrum... I made the transaction with btcpayserver and their vault app in the end, worked almost flawlessly. Electrum saw the transaction and the wallet is in correct state again.
If it worked in another wallet, then it's possible my theory about it being Trezor/Plugin specific is correct... anyway, glad you managed to get it sorted.  |
|
|
|
Given that Mac uses a similar file system to Linux, you should find that using commands in Ubuntu like sudo, chown ("change ownership"), chgrp ("change group") and chmod (modify file permissions) should help you fix the file ownership and permissions issues. You should just need to change the ownership to the Ubuntu user which should fix the write permissions. There should be plenty of online tutorials explaining how the various commands work, to save lengthy explanations here |
|
|
|
Easiest/Safest method: - Reindex Bitcoin Core. ie. put the old wallet.dat into the Bitcoin Core data directory, and start Bitcoin Core with the -reindex option. Yes, this will involve downloading the entire blockchain again, but it is the safest method and will not put your private keys at any risk. After Bitcoin Core finishes syncing, you'll see the final balance of your wallet and be able to create/send transactions directly from Bitcoin Core. It might take a few days to resync.
"Quickest" method: - Dump the private keys from the wallet.dat and import into a lightweight wallet like Electrum. Note that "quickest" depends on your level of technical ability etc. Given that Bitcoin Core won't open your wallet file without crashing, you'd need to use something like PyWallet to dump the keys from the wallet.dat. Once you have your private keys, Electrum will sync in a few minutes and show your balance etc. Note that this involves using Python scripts and the commandline. Unless you're familiar with both, I would not recommend this.
Most "robust" long term method: - Turn off pruning in Bitcoin Core, then restart Bitcoin Core using the -reindex option. Note that this will require 350+gigs of diskspace, if you don't have this diskspace available, do NOT try this method, it'll just cause you more issues when Bitcoin Core runs out of storage space |
|
|
|
I'm a bit scared it will take another year until they come up with the next steps.
I wouldn't be surprised... I called their office on Monday, was forwarded to a guy named "Russell", who asked me to email my query to a "Tom Aspin"... I also tried emailing the GrantThornton "enquiries" email address listed on their website on Wednesday and got an auto-responder saying that some lady called "Rachel" was away until Dec 16 and if it was an urgent enquiry to send a text. So I sent a text to the given number. It's now Saturday and I have not received a response to ANY of my enquiries  Based on my experience with this company this week, I don't expect anything to happen in any sort of reasonable timeframe.  |
|
|
|
I wouldn't recommend using "word"... it has a bad habit of including extra whitespace like line breaks/paragraph breaks etc... you can't see it visually, but the computer will interpret these hidden characters and it's possible they are preventing Electrum from parsing the private key properly. Use either plain old "notepad"... or, my personal recommendation, something like Notepad++ ( https://notepad-plus-plus.org/downloads/) it has some excellent features for bulk editing text. Couple of things to try: Try and import this private key into Electrum... see if the "next" button is enabled. 5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF
it's the "example" private key from the Bitcoin Wiki for address 1CC3X2gu58d6wXUWMffpuzN9JAfTUWu4KjIf the next button is not enabled with this key, then your Electrum is "broken". If it is enabled, then the data you're extracting, or something in the way you're editing it is causing issues.
Double check the Armory export, just to be 100% clear, the ONLY boxes that you should tick for exporting your keys are: - Private Key (Plain Base58) - Include Unused (Address Pool) - Omit spaces in key data  You can then click "Copy to Clipboard" and paste the contents into a text editor to strip out the headers at the top and all the "PrivBase58:" parts. Essentially you want a list of "WIF" formatted private keys like this: 5JWNxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx5he
5Jwtxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh8f
5JRyxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxYYu
5KaCxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxLyW
5KbyxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxVD2
5J6RxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxBkr
5JXyxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxgqV
5KJ5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx8Sp
5Hwzxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx7Ab
5JrXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxWJ6
I have just the private key strings that start with a "5"... and are 51 characters long... and nothing else.
If the data from Armory looks "OK", then like nc50lc has suggested, I would also recommend that you try and import just one key to start with... So in Electrum: 1. Select "File -> New\Restore"  2. Enter wallet name like "Imported Armory Keys" (click Next)  3. Select "Import Bitcoin addresses or private keys" (click Next)  4. Copy/Paste in just the first private key from Armory:  - If the next key is enabled, then you can continue adding keys in batches of say 10-20 until it stops working... which will help narrow down which key(s) are "breaking" it... - If the next key is not enabled with just one key then, can you please take a screenshot and blur out/coverup the middle part of the private key that you're pasting in so we can see what the entry screen looks like? (You'll need to post the screenshot to an image hosting sight like imgur etc and then post the link here) Hopefully, one of us will be able to spot what is causing Electrum to refuse your private key(s) |
|
|
|
So which answer is correct? They were probably all correct at some point... Note that the story from wired is a number of years old (29th October 2017)... that's before the Model T was even released (~26 February 2018)... and was for the older Trezor ONE model. Same with the reddit thread that you linked... it's 6 years old. Hence, the different system used. |
|
|
|
...
As I wrote in my first posting: Also when I transferred the backup to my current iPhone the Jaxx-App was put on reset somehow :-/ So I don't know if that would be differently, if I transfer the backup on a "new" device.
If you have already tried using the backup to restore it before... and the app was "reset", then it's highly likely that the backup doesn't include the data from the app that you want If that is the case, then no "backup file browser/extractor", nor any iphone device (real or emulated) will be able to help |
|
|
|
How to retaure Bitcoin wallet whithe this file "Walet.data" ?
What is the exact name of the file that you have? Is it actually "walet.data"? If so, that doesn't match any wallet file naming system that I am aware of. If it is actually "wallet.dat"... then you just need to download and install Bitcoin Core ( https://bitcoincore.org/). Once you have that installed and fully synced, you'll be able to recover the wallet, by shutting down Bitcoin Core, and putting the wallet.dat into the Bitcoin Core "datadir" (you can find what this location is by looking at "Window -> Information" menu option in Bitcoin Core.) Once you put a copy of the wallet.dat in that location, restart Bitcoin Core and let it finish scanning the wallet. |
|
|
|
...but when I launch pywallet with those files I always got an error: "ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again." Either the "recovered" files are so badly corrupted that PyWallet cannot read them, or you are not using PyWallet correctly. Have you tried using PyWallet with a wallet.dat file that you know is "good"? ie. create a new wallet.dat and try and use PyWallet to try and dump the keys from it. Once you've confirmed that PyWallet is actually working correctly, then try again on a copy of one of the recovered files. If you still get the "ERROR:root:Couldn't open wallet.dat/main" error, then the file is most likely corrupted (ie. a "bad" recovery). |
|
|
|
I can stay around on the wallet a few seconds but I always get the same error: Fatal error... the wallet then proceeds to close itself.
I get the same error every time. Let me know if you have the same error or if you have a fix.
You'll need to look in your Bitcoin Core "data directory" (the same directory that has you wallet.dat), and find the "debug.log" file... open this in a text editor and scroll all the way to the end. There you should seem some "obvious" error messages as to why Bitcoin Core is crashing. Note: if you're on Windows, there might be something useful in the "Event Viewer" (look under "Windows Logs -> Application) and see if you can find anything related to "bitcoin-qt.exe" |
|
|
|
So, the private keys you are exporting start with a "5"? If so, there must be something wrong with the exported data or the format it is in... perhaps trailing whitespace of some description or something? Are you copy/pasting that data directly into Electrum or were you copy/pasting into a text editor first? If so, what text editor were you using? |
|
|
|
Isn't there a program for something like a "virtual iPhone" where I can transfer this (unencrypted btw) Backup on to?
Have you tried Google? A simple search for "extract data from iphone backup" seems to throw up a bunch of various apps which supposedly allow one to open iphone backups and retrieve data. No idea if any of them are any good (or actually work), but it is a starting point. |
|
|
|
Mycelium did a great job as far as I am concerned and will keep using. But what about other wallets, will they send back to the original pub addy or into oblivion?
Wallets didn't send coins into oblivion... coins ended up in oblivion because users didn't know or didn't understand how their wallet software dealt with "change". Typically, what happened was that a user had say 1 BTC on paperwallet AddressA. They would import that key into a wallet, then they would create a transaction sending say 0.5 BTC to AddressB... The scenarios for what happens to the change were: 1. The wallet software sends the change back to AddressA. (What most users thought would happen) or 2. The wallet software creates a new, random private/public keypair, derives AddressX from that keypair and sends the change there. (What a lot of wallet software did). The user would then uninstall the wallet and/or delete the newly created wallet file (without realising they needed a backup of this new wallet and/or keypair) So in scenario 1, the user is fine, they still have the paperwallet with the private key and access to the "change". However, in scenario 2, if the user destroyed the wallet file (without any backup), they lost access to the new, randomly generated keypair that they need to access the change that is now in AddressX. It doesn't really matter which way wallet software deals with "change"... as long as the user knows and takes the necessary steps to maintain access/control of the necessary private keys, then they won't lose anything. There is a reason paperwallets are not recommended for new or inexperienced users |
|
|
|
|
Show Posts
