|
I'm going to have to agree with Lucius here... if you're not comfortable with enabling the passphrase option on your Ledger device, then please just don't use it.
|
|
|
|
Does anyone know when would be most likely the next update?
Why is this important? Are you trying to plan something around when Ledger are likely to issue a new firmware?  It could be tomorrow (if someone has discovered a severe flaw that needs immediate patching), it could be next week, next month or never...  |
|
|
|
|
I don't believe the second file in that screenshot is a wallet file. The urls listed in screenshot (geotrust.com) and company names VeriSign and RapidSSL, indicate that it is some sort of file related ing SSL certificates and is not a wallet file.
As for the first file, it could be almost any data file containing mostly binary data... it could even be encrypted.
|
|
|
|
How can they provide a "backup" system that requires that still have access to everything??!? That makes no sense. It is a custodial system, I find it very hard to believe that they cannot recover your account for you based on the access you currently have. Yet another reason that users should everything they can to avoid custodial wallets with proprietary (and broken) recovery systems. |
|
|
|
Honestly, I don't really see any worth in a feature like this... but that's just me and my particular use case. I'm sure someone would appreciate a virtual "Bitcoin Nanny" that stops them from spending all their coins on shoes or boats  |
|
|
|
@BitMaxz : it can be like a birthday along with other numbers so that 64 characters is enough, i previously created this wallet and get address but not saved WIF.
Are you talking about a "brainwallet"??!? Where you just have like a 64 character "passphrase" that you used to generate a private key and address? If so, just use the "Brain Wallet" tab on bitaddress.org. Download the .zip that is linked at the bottom of the bitaddress.org page and then run it offline. |
|
|
|
Are there other ways to get rid of this annoying warning besides forced upgrades?
Short version: No. Long version: download the Bitcoin Core source code, edit it to remove the warning, compile and run your custom version. Be happy. |
|
|
|
i have the 12 words, the backup file "samurai.txt", the public id of the only transfer made, and the passphrase
when i try to restore the backup I get an error with the passphrase. It must be a syntax error
Are you restoring the 12 words... or using the backup file and the passphrase? |
|
|
|
I re-installed Electrum and some other wallets and imported the original wallet, but I cannot see the correct balance of the wallet.
Can you please confirm exactly what you mean when you say you can't see the "correct balance of the wallet"... do you mean: 1. That you can see some transaction history on the "history" tab, but that the balance is currently showing as 0 BTC... or 2. That there is no transaction history being showing on the "history" tab (and balance is 0 BTC) |
|
|
|
|
As an aside, it's possible your 18 words might be a MultiBit HD wallet (which would be BIP39 compatible)... So, if you don't have any luck attempting to recover with Blockchain.com, you should definitely try recovering your wallet using a BIP39 compatible wallet and try restoring using your 18 words.
One important thing to note is that MultiBit HD didn't use BIP44 standard derivation paths... it used: m/0' so you'll need to use a wallet that allows custom derivation paths (like Electrum).
|
|
|
|
Honestly, I think you're wasting your time mucking about with Linux/Ubuntu and attempting to decrypt the file manually. If you were able to successfully import the backup file into "Bitcoin Wallet for Android" and use your password and it didn't give you any errors, then the app will have already decrypted the file correctly and loaded in all the private keys from the file. So, if, after importing the backup file, the wallet was showing as zero balance, then the wallet is likely empty. If it also showed zero transaction history, then chances are that you have the "wrong" backup file... and the backup file you have is for a wallet that never contained any coins  |
|
|
|
Theory, recovered wallet.dat is only partial and corrupt. Possible bytes containing private key information might still linger on HDD.
Possibly, but if your memory about password protecting your wallet.dat file is correct, your chances of recovery them using a hex search are essentially zero. The hex searching is only really applicable to unencrypted wallet.dat files. Based on the errors you were getting with the wallet.dat and common tools (Bitcoin Core, btcrecover etc), it honestly just seems like the wallet.dat files you have are corrupted Best of luck with your continuing search tho! |
|
|
|
At first I was quoted around £1,146 VAT included to recover the file from the broken drive
That is probably a little on the high side, but not out of the realms of data recovery charges. Because of the severity of the job, this was a challenge and they struggled to get the BTC from the file (to be extracted and sent in a wallet) they suggested a solution that is having a partner company they have a contract with to assist further. The fees for that is 30% of the wallet.
However, this is quite excessive in my opinion. 30%!!?!  Once the data files were recovered, if you knew your passwords (if any) then the recovery of the funds would have been a matter of minutes Having said that, you appear to be happy with the outcome, which is the main thing. I'm glad to hear that you managed to recovery your coins. It's certainly nice to here of a positive outcome for a change! Best of luck for the future... And make sure you've made some safe and secure backups of your 24 word Ledger recovery phrase!  |
|
|
|
Have you considered submitting a pull request to the Electrum github so that others can benefit from your Superstar self's awesomeness? |
|
|
|
There was a "max size"... it's now a "max weight" for transaction, since SegWit... due to the way it works, it's basically 100,000 bytes (for older legacy transactions) or 400,000 WU (weight units) for SegWit type transactions: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h#L24When you create the transaction in Electrum, check what the "size" value if you look at the detailed/advanced view when you are creating it:  As NeuroticFish suggested, it's likely caused either by too many inputs or, less likely, too many outputs. How many inputs and outputs do you have? |
|
|
|
This makes sense now. Well let's not make it too hard. We always have option to deal with the HD wallet. I don't think anyone need to access only a single public key when it's x to y multi-sig wallet.
The only time I've had this requirement was when trying to "rescue" fork coins from Electrum MultiSig and/or 2FA wallets, for which a "forked" version of Electrum supporting MultiSig and/or 2FA was not available... and that hasn't really been an issue for years now. But basically, it involved taking the master keys... identifying the individual private keys that matched the addresses with UTXOs... then essentially recreating the multisig in the "Core" wallet for the particular chain. It's not impossible to do... it's just a real PITA and requires quite a bit of manual work/console stuff with raw transactions etc. (not to mention having to sync/maintain multiple chains ) |
|
|
|
|
The real advantage that Tails has, is that it was designed to be able to be used offline... easily. In that, it has the option right in the boot menu for booting with networking off.
You may find that running Windows "offline" causes issues with some modules as they're designed to be used in an "always on" environment... but at worst, I would expect an error message or 2... it certainly shouldn't be any showstopper issues that mean the OS is basically non-functional.
|
|
|
|
What exactly do you mean by a "cold storage" wallet? Armory just creates wallets... or you can create a watching-only copy by clicking on the "Create Watching-Only copy" at 'Step 5' of the wallet creation wizard:  or by using the "Delete Private Keys" option (Wallet Properties -> Delete/remove wallet):  "Cold Storage" is not a special wallet type, per se... it's simply a version of Armory running on an offline, air-gapped PC. It's being "offline" that makes it "cold storage". So, if you have the paper backup for your "cold storage" wallet, you can simply restore it on any copy of Armory (offline or online). You certainly don't need to restore it on an offline machine and then transfer the wallet file to an online machine... you can just restore it directly on an online machine. You can easily test this... just create a new "dummy" wallet for your "cold storage" machine... then simply restore that dummy on your online machine using the root key backup. You'll see it creates the same wallet. Or am I misunderstanding what you're attempting to do... and you want to be able to restore your full cold storage setup as it currently is? In which case, restore on the offline machine, create the watching-only copy during wallet creation... and then transfer the "watching-only" copy to your online machine. |
|
|
|
The only option I have to pay with (in crypto) is BitPay but whenever I'm redirected to the invoice, it says that I need to login and verify my identity. Am I missing something here?
Did you try the "crypto.com Pay" option? or was it not available to you?  I just tried it (with dummy data, to order a Nano S) and it gives me the option to pay using BTC without requiring anything other than an (unverified) email address.  (note: click the "Other Cryptocurrency wallets" option)  |
|
|
|
|
Show Posts
