I guess i missunderstand the #4 post cause you said anything like restore the old wallet but i would like to know if the same process can be use for other BTC wallet (electrum).
That's off-topic but yes, you can. But Electrum's wallet file doesn't have to be renamed to be loaded by default, you just have to paste it to the data directory: %appdata%/electrum/wallets then open it using 'file->open' menu even if Electrum is running.
|
|
|
If the amount is over 50 BTC you should consider selling OTC as you could get 20% premium for your "virgin" btc.
Dont sweep into one address as it will or could reveal your identity. -snip-
Some will pay a premium for fresh coins as someone above stated earlier.. -snip-
Too bad, he already did. ( https://www.blockchain.com/btc/tx/54aa0aa03fd0dc5f4a6e2c61fc6267e3ae82c36d122d36e0bd6cb1022a154a01) If the link from that article is true and it's really him, then those 20 coinbase transactions are just consolidated to 3CU4AYJH23ePNnKsycinP5TSogCNGsyqCc then sent to different addresses.
|
|
|
Must be because the amount you specified wasn't 'filled' yet. You just received 0.0045 BTC instead of 0.005
But as TryNinja said, you can ignore that because it's not actually required to receive Bitcoins, it's just for label and stuffs.
|
|
|
I got it open with bitcoin core. Not sure what that 17 word thing is for. Wallet was empty as excepted lol
You might want to check if it's a brainwallet. Just download brainwallet's source ( site, the Github link is in the footer) and run it offline. Paste your brainwallet and copy the results, check the address in a blockexplorer if it has any balance. If there is, you can now import the private key to any Bitcoin wallet that you want.
But wait, is core not fully synced yet?
|
|
|
Have a question about restoring old wallet. After gettng old wallet DAT file what is the next procedure cause I'm lost there and none of you guys said something about it.
Read post#4, you need to copy it to the data directory and rename the wallet file into " wallet.dat" ( Bitcoin Core have to be shutdown before proceeding). And Core should rescan when you launch it. The default directories written there are simplified, for Windows, %appdata% is in your hidden C:\Users\Username\AppData\Roaming folder; or just type %appdata% in the run menu ( Win+R), the open " bitcoin".
|
|
|
In addition, for " pyramids", you just need to count how many [quote] and [/quote] are there, there should be the same number of closing /quotes in every opening quote tag. Here's how to pair the opening and closing quote tags ( colors): [quote author=user1] [quote Author=user2] [quote Author=user3] User3's Reply [/quote] User2's Reply to User 3 [/quote] User1's Reply to User 2 [/quote] The first and the last tags are the pair, going to the inner tags. Long post should be shortened/cut though.
|
|
|
Maybe that's a " Brainwallet", did it ring a bell? It couldn't be a BIP39 seed if you're sure that it's from 2013 because it was just published on that year's last quarter ( but there's a chance). Did the words from that 12-word backup matched any of the words in this list: BIP39 Word-list?
|
|
|
The terms used in that email are utter bullshit, the scammer is trying too hard to sound "technical" by using widely used terms for crypto. Words that are weirdly combined and non-existent crypto terms: "Blockchain system", "turnover operation", "default HASH", etc. He used those common terms in a very outlandish way.
Speaking of scams, please check every user's profile that replied here by clicking on their names (left-side of posts, specially the latest ones). Make use of the forum's "trust" feature and I suggest you to do not trust the profiles of those who've got a bad reputation.
Take care.
|
|
|
There's nothing wrong with your transaction.
Currently, 1sat/B is almost at the 2mB+ range (within 1mb is the priority) and there's a good chance for it to be included to a block within this hour (if blocks aren't too delayed and more transaction wont flood in).
Past 4-8 hours's mempool size is worse.
|
|
|
are you sure those wallet files are readable because usually .dat files are used for when you store data as binary not plain text which means opening it with a text editor should technically show you random looking weird characters instead of a readable text.
Try to download v1.8.1 and open the " electrum.dat" or " any_name.dat" file that it created. Even provided with a password, it will just encrypt the seed but will leave everything " readable". I have both wallet.dat file (random gibberish when it's opened in notepad) and then a notepad file called Bitcoin that looks like a 12 word seed. Both dated 12/24/2013
Then it isn't Electrum's wallet file. Also, there's a chance that the 12-word seed isn't connected to that wallet file since Bitcoin Core didn't used seed phrase ever.
|
|
|
I don't know where it came from, but I do have a 12 word seed phrase with it.
Very old versions of Electrum have a '.dat' extension to its wallet files, and ofc a seed phrase. Specifically v1.8.1 from 2013. Have you tried to open a copy of the wallet file using a text editor? If it's Electrum, there should be readable data because the whole wallet file wasn't encrypted back then. If you can read " addr_history" and bunch of addresses, then it must be Electrum. Just restore your seed to the latest version from the official site: https://electrum.org/#download
|
|
|
I'm pretty sure it can. Passphrases are great, and everyone should be using one, but they don't encrypt your seed - they are used as a salt for PBKDF2. -snip- Yeah, it makes sense, you cannot reverse PBKDF2 so it isn't encryption. But every Wiki/Article link about BIP39's passphrase labels it as " encryption" simply because it uses a " passphrase", those need some correction. For the security, it's not that safe as I mentioned earlier: " the seed will be safe for a while" ( the seed, not mnemonic).
|
|
|
Most metal seed phrase storage devices cannot encrypt the seed phrase, which in my opinion is a very important factor. If you store your encrypted seed phrases in more than one cloud storage device it will be much more secure. -snip-
I'm pretty sure it can. The user can always use the standard BIP39 encryption which will only add an additional word to the existing seed ( but not to be included to the backup). Info: BIP-0039Even if the backup is compromised, the seed will be safe for a while since the mnemonic will derive a different set of keys if there's no passphrase or the correct passphrase wasn't included in the import.
|
|
|
The same problem of OP, someone trying to figure out what happened to transaction to this "empire"
Doesn't look the same. In OP's case, the deposit address was already used and there's no activity whatsoever in Empire's side. Pretty much a case of fake URL. In that Reddit link, the OP mentioned that it was labeled as unconfirmed by Empire but removed later; the deposit address wasn't used before, just to receive and send once. Looks like an error on Empire ( legitimate site).
|
|
|
That will work for recovering your Bitcoins but it requires you to sync the blockchain; if you have the resources, do that. To recover your BCH, you can do the same but download a BCH full node instead ( note: BCH blockchain is a lot bloated than BTC's) Alternatively, you can just export the keys from your wallet using dumpwallet command ( usage: https://bitcoincore.org/en/doc/0.16.0/rpc/wallet/dumpwallet/). Using those exported keys, you can import it to other client like Electrum and Electron cash to recover BTC and BCH. Just make sure that you have a backup of that wallet file in case of file corruption.
|
|
|
I just realized I used the term "Root Key" incorrectly previously. For clarity the root key is shown, just using the secure print feature so that it is encoded. I keep the code separately when printing or storing online (in private folder)
Ah so the one stored in s3 bucket and the one being sent to a printing store didn't contain the " encryption code". That would slow-down anyone who took a glimpse on your encrypted root key, but not totally impossible to bruteforce. You might want to read this old topic regarding Armory's " Secure-print" feature: https://bitcoin.stackexchange.com/questions/25694/how-secure-is-secure-printNote: That was from 2014.
|
|
|
Also, for how many years will ASICs like S17+ Work?? Can it work viably upto 3 years?? There is no magic number, it may break on you the day it arrives or a decade down the line. Additionally (@ TheBitcoinChauffeur), those ASICs are quite modular, you don't have to replace the whole unit if it breaks; sometimes one of the three hashboards fails, most of the time it's the Power Supply. But it depends on the environment, if it's too dusty, hot and there's no proper maintenance, don't expect it to last for 3 years. Also, don't forget the " silicon lottery", some units can be set to " Turbo Mode" without degrading, but some might break a few years after.
|
|
|
The Root Key is kept completely separately.
Do you mean, just these parts of the single-sheet backup?: Test WalletIf so, then it's a useless backup, it contains nothing but the wallet ID and info in case you need to manually find it from your computer.
|
|
|
you can't import a dump file like that. -snip-
Last time I tried, importing the keys from the dumpwallet file worked for " importwallet" command. Of course, not the actual wallet.dat file or the file from " backup wallet" option. In OP's case, it's a file from dumpwallet command with '.dat' extension, looks like he accidentally added the '.dat' extension through this: dumpwallet "UsersAdministratorDesktopWalletsDesktopDBitcoinBUwallet.dat"
|
|
|
|