ok.. 55 BTC i guess. Will give it to some recover specialist. Thank you for your help.  That's a pretty big stash IMO, I don't blame you... Providing this thread to the recovery service (and in particular the example file, and the post about what strings to search for) could help. Best of luck to you.... |
|
|
|
I use 2FA.
Here's my best recommendation. If you had a large amount of Bitcoin stored there, I'd shutdown the machine ASAP and send the drive to a recovery professional. If you didn't have enough to justify that, I'd shutdown the machine ASAP, and then boot it off of a Live Linux CD or USB to search the hard drive for the master public/private keys (I'm not sure what the easiest way to do this is because I'm not much of a Linux desktop guy, so no instructions included for this option, sorry...). If you just had a little, download and install HexEdit, (preferably to a drive that's different from where your wallet file is stored), run it and then open your C drive (or which ever drive had the wallet file) using File -> Open Special. Please note that installing anything or continuing to use your PC decreases the chances of a successful recovery. Search for these two text strings one at a time, (no spaces, but double-quotes and colon included): - "master_private_keys":
- "master_public_keys":
Just as in the example file I posted above, you're looking for one master_private_keys with the label "x1/" and three master_public_keys with the labels "x1/", "x2/", and "x3/" (you need to keep track of which key which label). Even if you find the bare minimum, I'd keep searching for more until the entire HD has been searched, just to be thorough. If you manage to find them, it may be possible to recover your funds. Let me know, and I'll post the final instructions for recreating a wallet file once you have all four keys. Good luck.... |
|
|
|
>> from PyQt4.QtGui import QFileDialog
>> util.json.load(open(QFileDialog.getOpenFileName(gui)))
Traceback (most recent call last):
File "..\contrib\build-wine\build\pyi.win32\deterministic\out00-PYZ.pyz\json", line 278, in load
File "..\contrib\build-wine\build\pyi.win32\deterministic\out00-PYZ.pyz\json", line 326, in loads
File "..\contrib\build-wine\build\pyi.win32\deterministic\out00-PYZ.pyz\json.decoder", line 366, in decode
File "..\contrib\build-wine\build\pyi.win32\deterministic\out00-PYZ.pyz\json.decoder", line 384, in raw_decode
ValueError: No JSON object could be decoded
>> When I open my wallet, there is pretty much nothing that i can read. I got a lot of *.py files too, anything we can do with that? If there's no readable text (like in the example file), then whatever file it is that you have isn't an Electrum wallet file (perhaps due to HD corruption of some sort). If you have no wallet file backups, and no seed backups, recovery will be difficult or impossible. First: you didn't answer an earlier question: was your wallet a 2FA wallet or a standard wallet? |
|
|
|
I have the default_wallet.dat file and pretty much everything else i could restore.
I still remember the password of the wallet and got the 2FA google stuff here too.
If you're using a 2FA wallet (are you?), the seed cannot be recovered from the wallet file (it's not stored in there). Electrum tells you this when you first set up the wallet. You need either your seed or a working wallet file to recover your funds. If you have a completely corrupted / missing wallet file, you might be out of luck. If your wallet file is only slightly corrupted, you may be able to fix it. First (very important), make a backup of it so there's no chance of making things worse. Next, open your wallet file in a text editor (such as Notepad on Windows). It should look something like this: {
"accounts": {
"0": {
"change": [
[
"03ac0342c7c8f92d41458bdb22f0abec55eedd5aa8f982e8c91318d68631337812",
"021b939f6db543de61e6c18b037c0aea1279a9c47b35b0f5ad6a45060487a99cc9",
"03ecc8024843d6da37c1b4a6096f7a30d67518402369d3cbbd8c893ee65672f8af"
],
[
"02407ab9bd1c32aceb0e42aea0e1ac69ac06fcb070ff8fcacbacb7b08d29cb8cba",
"028d07f31a64365bd63eaf6c3fe8379142264d468975a86376cf9bf861986c1824",
"03ffd76f226ccd257a015c9c437b693a5d2edf34e6f2e27d7a0c5ba8c33ac00670"
],
[
"03f1bbdfe1be7c533e7e789b04b6da25f74a8dcf4c2a2239fc867f63a32965cc64",
"02b7b63d7fc1d61124ad9ae0e97c15725c439d6e4d61bb3a3e9c958ebca43ea7e7",
"02979116cfc78f395719a5bd8ded064b49e6b5bf89963a5a1d817e8869b459aa7f"
]
],
"receiving": [
[
"037f4e76573fb495b0d96d7961e99b588c2bcf58bce2baef094156d62fc0a8cd45",
"02d082c279324b606dd925b77daed33a7a9b01355b7d653d0cdfa1e4d4f72eba8d",
"03f6e932c7e25f5e40c72c7d981ca76235c0b38f65b7858d41356472549a4c9790"
],
[
"025330a72b7311f94e519c679641f783e4f8efc3f9b8b146ba1f03b0689d0e6e5f",
"02881777cd44bf1cd724bccdf1a9b2f695b689c2da373b0c842a1ea64522eae277",
"035000d2b358b19566a4ea074a29f9095bb3c15b551783bc5bb632ab8a8a7686c1"
],
[
"036b1a078c412f7961eecb49bba365c279c4567ba937805dd9ac34e157f0b47e5a",
"038f22a1e99351b2aa9a482bfebc43890e8f5ac9be7d150d758f063b56ac647715",
"02175a44e790b3f3c8e41b8d5275e68f3aa0332f3d6631cbc99842ca723bfd7dab"
],
[
"0258cc18d2843702bde79bbcf4df74b2aee88ddf9fb4fae03005e7367196a4f69b",
"02f3f0237562f79bc95321b7d2c8ca2e946602e29939d9ac87a4cac534e4ca469e",
"0388246d6a3c73e9f3aa1e4370ad4f3dd9f20c67ec0fcfabc931151464adda090f"
],
[
"025bf61d138fea2e5868049d69bf627de5ed8e4e11daef757b19d1c6ce94f87a5c",
"02066c0e6ca63122f8a9e7413658d87dc04814236e999fa6cc6a5da0188ad4f2b9",
"02a63fd35ee7373d0b79fee31075d02ff53f11639fbf23a02c6d27fdab9acaf9e9"
],
[
"022ae832008e773d2126aadbfee6750827e4ed0d698e2d4700cc4f3c968bf51dee",
"03716958ed0073e38584a95d2ec9dad71884e93d8fa482c609ad702fe4157180bf",
"028a8b8f82d97fa5dfc61f065276acd63cca8eb45e9cb4101219db64bf4b1957b0"
],
[
"020decc7b97b3e8e355b8dcaa9cf66b2c6d56665d89abc46990d405a634efeeda4",
"03b90f527d22a3ac69114ef1646ede9d31bf83fb154f551f0645acdf8a2f581c7f",
"026c59a9fc1c16dc6efc6cac1caa0c1998e9c7a3ce09c0d6cc63a379bf55552f81"
],
[
"02b300cd992b2020b0a03954191ba8bef1a091cdc468b99212fb1070ad05f8560c",
"02038dca3242db4d107b6cf0ac7c5a66b9a9996e14522d8ef3cd836157618e82c8",
"03578b8f14ce86902213352da549f985b205800b533a1d1a447d6185ea90848de5"
],
[
"038a02fa807574173baa1f13dba508d26958417f209cb8d9564276c9ff05fd3377",
"02123ae61fb2dc5f134abf14c217b79c556f65ebe00ea344a54931c118afe663d7",
"0324f09a257fe5d583083bbc398495d4f3ecdcf2918a6499dde991262daf270f2b"
],
[
"0231dfa361f1f805067b7f2846c4fa62d793179f36af0b28ce32ac1cb775e76ae9",
"02e8eb42d24274473e3581609a3e7537ac8472fb8ac63e61fda074bf7ca57d5e47",
"03d3dd7b39b5fb812e1d8088f5ccc0a50c00cd9f9539a10d1155e71407d609b623"
],
[
"03b9e4444488511abeb992b682637e971f45d43e1f3256fe9377ac937313c9ec32",
"02593b49a6cd93ae929a2ffb14fc97977b144a692b40d4e01da4f43aede8cf4276",
"032412b8383bbd10a2d00ca1fbbc0887c5407e0dc7d0220c61623b8a84df54e6fd"
],
[
"03db584f5b6d5f7af655b525c800b7826b61f9fd8ba597371a286419a1ebfced73",
"0302d0d83b68a618d618a59a2fdb860634fcfc36314b11afd6ac44669101183ae6",
"03a1153c84ec94c702e148cc032cfefe17530674ea26568c799cb3a6aea3cdb672"
],
[
"03db20128d0ba7b1de844663e4072009c9a309cf3405171487dbd56752d99315a0",
"028aba0ea4fb17eb6de96e93c23b3299e4c07d5751cf4782fc73f3dff46542dd2c",
"03f30d88ce7743054046c75b558a136a6616a111e48b216e9d81caa5594593ebe4"
],
[
"022294e54daa3cb03dc264963fe2697e8372e81882d5b81222f728c1f7f2c1714a",
"03f0c9b27946dd3460c2261b6769c3cfbf256eb1dc108965377b9179ada8ee717d",
"0310a35c633e14cd3b94021b9928d2a3a71892940df47294e4e5bda52cc60b007a"
],
[
"034cb8e3e6b58a123d83882e6c45e86c2ff5eb16fd47c1f1feab7ad177782aafcc",
"022eb76270b1ac47e7701a0d77232446a8406671db39160a086c6740ab35d41c0d",
"0347a903bea538bf9e800f1ac59072ae0038bea30e8c3ac3b56c08ab35c9e672c1"
],
[
"03e565a126627b3ea1e4e5f2ce6064447c9ee2ca37543e27da36cf8dab7355d132",
"0279e9538ce91a7386fbec166b17bb42e4ecaba2de8db785b83bb70db6e4db21f7",
"021ec3738cd8889424768babaa46f77a69db027651c90e4132c82f68b8e0b90deb"
],
[
"023346f43393acdf93a2ccf92d9f44b4213f6e2aa7a1d9a5b5812ce85ddc6d45a6",
"0238a4deb9f67bf0b8f4bb6045a0ce17782d43a84875c2f4f90742ce745f6a46bf",
"02de5065f947ff944114fcc8fb5896efc9712beb7d148c073763de26fb2a9197b4"
],
[
"02d9e049b552386a66eb08e1ead8f4b55432df9002a7aa3269ae7ff146ab5fd040",
"020983271bc3ea8c466743997d29279e242fbb3c5456b78bc488b657f32079623b",
"022faf4d3d33cbe2b5cc1f20f8750941a4960a58a4c9e8d116801b43f82ebf8b4f"
],
[
"020d9ebff72467155429b16ff0042d05b23ce48dcbc1a49f1c47eab18fa1a724ac",
"036fd3c3e38834202c58dc28dba042756bb2d6b87c7b463a570f525a2e7f780226",
"023629847b9e38ef40d5b80526c1ec85dbc793f29026682537794ea7f1a4db2390"
],
[
"03e04943a31bd43d0bd112e59525aa5cc535b26ad9f32ebc92b3424e784cfd28fb",
"02c1fdf9ea0e4a82ba62eeb223b5c114b2190cde7a6578a38e1d3e462d2f9f8018",
"027046fe6d8d01629e48afc5d04d53ef843cfe5378f8550217aeab2434961c4dee"
]
],
"xpub": "xpub661MyMwAqRbcF7S3zTDZ1QBaDKi8eUjSETyxtajGrbNKHHoMv8vWt1yiamfQGvRaxcHRovmUzeGqPeySjRL6pKTb57Cu3dSrDaGkFbx7LaB",
"xpub2": "xpub661MyMwAqRbcFTQiUpNzWsZLa9tSpW1ut3Xet7gFUWzydmRzvfr8So9vkhseiftjuCAiMs6X8APqUf2VMp13XEU7fBAmhYoFXpTqxvVupwd",
"xpub3": "xpub661MyMwAqRbcGTQ1T3H5pmertr31JLddqwqVcWedoSFHY3AnjYQUnqiGAhNzofPf22kJXAtJQhmsFXin4T41k4xGLLzCt3RvskGmja4Buoj"
}
},
"accounts_expanded": {},
"master_private_keys": {
"x1/": "lvZ5FCGXcS6+qhc2aq9nENE6uEe6DdUJmEruIg30pdKS4doc5at50W5+aH0pkIYVJY1UM3QGoClTCFPxKJXJ/nkP9Vzn3sFHDdie/EbSMKmUDevhj8Wvf3ttfQ3NHTZuXq5twD2mTOLFDuKgcirEFPSp5FzDOQVXvypUhbiVUSg="
},
"master_public_keys": {
"x1/": "xpub661MyMwAqRbcF7S3zTDZ1QBaDKi8eUjSETyxtajGrbNKHHoMv8vWt1yiamfQGvRaxcHRovmUzeGqPeySjRL6pKTb57Cu3dSrDaGkFbx7LaB",
"x2/": "xpub661MyMwAqRbcFTQiUpNzWsZLa9tSpW1ut3Xet7gFUWzydmRzvfr8So9vkhseiftjuCAiMs6X8APqUf2VMp13XEU7fBAmhYoFXpTqxvVupwd",
"x3/": "xpub661MyMwAqRbcGTQ1T3H5pmertr31JLddqwqVcWedoSFHY3AnjYQUnqiGAhNzofPf22kJXAtJQhmsFXin4T41k4xGLLzCt3RvskGmja4Buoj"
},
"seed_version": 11,
"use_encryption": true,
"use_trustedcoin": true,
"wallet_type": "2fa"
}
You're looking for missing syntax. For example - make sure all of the braces and brackets ( the {s and }s and the [s and ]s ) match up and that there's a closing brace at the very end of the file
- make sure there's nothing following the last closing brace
- make sure there a comma after each pair of items, except for the last item in a list
- make sure there's a colon between each pair of items
- make sure the double-quotes match up
If you find an error, try correcting it, saving the file and loading it in Electrum. If you can't find an error, you'll need to find someone you trust who understands JSON (that's Electrum 2's file format) who can look at the file for you. If you can't find any problems, you could try getting a more specific error message by doing this: 1. Move your default_wallet file to a different directory. 2. Start Electrum and let it create a new wallet for you (you don't need it for anything). 3. Go to the console tab and type in this: from PyQt4.QtGui import QFileDialog
util.json.load(open(QFileDialog.getOpenFileName(gui)))
It will ask you for your wallet file, and then print an error message that may help you find the problem. If you get it fixed, you should create a new 2FA (or standard) wallet to transfer all of your funds to, and this time write down the seed!  Is the wallet file the same version of Electrum? If it was created with an older version you need to use that version to restore it, since I believe that the newer versions of Electrum have changed the file format? Not sure, but that is what I would try.
FYI the new version of Electrum can read either wallet format. If it finds an old format wallet, it converts it to the new format (which actually isn't a whole lot different). |
|
|
|
importprivkey "your_private_key" "Some_Descriptive_Label_Optional_Here" true
You will need to do it for each of the private keys you exported from your MB wallets. There's also an importwallet RPC command that I think can directly read the key export file (with all the addresses at once) created by MultiBit, but I haven't tried it in a while and I could be wrong. |
|
|
|
Are you OK posting (or if not posting, at least PMing) your public IP?
Got your PM. It's not obvious what's going on, though. Confirmed that your node is accepting connections on TCP 8333, 3-way handshake succeeded. After the initial connection, my node sent a version message as expected. Your node ACKed receiving the message at the TCP level. At this point, your node should have sent it's own version message to mine, and it should have ACKed the version message at the app level with a verack message. My node received neither. There are no MTU issues (yet) -- all of the initial messages are far under 1481 bytes (the point at which MTU issues might rear their ugly head on an older PPPoE connection). There was no obvious evidence of a transparent proxy (no differing TTLs), but it's always possible. What Bitcoin node software are you running? Do you have any familiarity with tcpdump (I'd be interested if your node was responding at all, and if the response was getting lost, or if it's not responding at all)? Anything interesting in the logs? |
|
|
|
Thank you for the advice. If the MTU issue is the case, how does that explain the fact that the node was reachable normally for days. The problem occurred after a planed server restart.
I tried some different MTU settings but still not reachable, but the port is reachable from the outside...
Also tried removing bitcoind and installing it from the ppa:bitcoin/bitcoin. Still does not work.
Any other advice anyone?
Are you OK posting (or if not posting, at least PMing) your public IP? |
|
|
|
hi, i just download electrum ,but cant open it, message say "cannot read wallet file default wallet"
i checked in electrum files and default_wallet is empty file.
maybe it bkz i have old version in my PC too and it have conflict with just downloaded version?
Which OS? I'm going to assume Windows 7 or earlier. Try this. To to Start -> Run..., type this and then press OK: This will open up an Explorer window. Find the Electrum folder and rename it to Electrum-old (right click, Rename). Then start up Electrum again. If you don't have any BTC in your old Electrum, you can delete Electrum-old at some point (at your own risk). |
|
|
|
Now that the new version of Electrum recommends 13 word seeds, would it be a good idea to convert both my 12 word seeds into 13 word ones? Are there any security implications for doing this manually as opposed to generating a new seed automatically? Could (should?) I choose a word from the Electrum dictionary and simply append it to the end of my existing seed to turn it into a 13 word seed?
You can't convert an old-style seed with 12 words into a new-style seed with 13 words -- the two are completely different beasts. AFAIK, the old-style seeds will continue to be supported indefinitely. The only potential advantages I could see (and they're pretty minor) of a new-style seed from an end-user's point of view would be: - A larger gap limit, by default (not all that useful, given that you can increase the gap limit manually if you have a need for it).
- Some compatibility with other wallets, for example you can export a master public key from a new-style wallet into a Mycelium for Android wallet (to create a watching-only wallet)... not really much advantage since you can already do that with Electrum for Android.
- Easier to recover a mistaken word or two; if you're in the habit of trying to memorize your seed (not something I'd ever suggest), new-style seeds are easier to recover if you're off by a word or two.
Of course there are many other improvements in Electrum 2.x in terms of other new wallet types, but if you're only interested in having a standard wallet, there isn't a strong argument to create a new-style wallet to replace your old-style one (I stand to be corrected though). |
|
|
|
Needs an additional column :
BIP-44 passphrase support yes/no
For example myTrezor support BIP-44 with passphrase, as does electrum's trezor plugin
However Ledger's Chrome wallet and electrum's btchip plugin are BIP-44 without passphrase support
Do you mean BIP-39 passphrase support? That's a good idea (It'd probably be a requirement for "full" compatibility, but not for "partial" compatibility). Would it also make sense to add one line for each software/hardware combination, e.g. Electrum/TREZOR, MultiBit HD/TREZOR, myTrezor/TREZOR, etc., since they might offer different levels of support? Or are all TREZORs pretty much the same? (and all btchips, etc.) Unfortunately I don't own any hardware wallets, so that makes it more difficult for me. |
|
|
|
I was too lazy too read reply in this thread  No worries  BTW, mSIGMA let you use Full Validation / Simple Payment Verification Sort of.... mSIGNA requires that you install Bitcoin Core (either on the same machine or on some other machine in your LAN) in order to use it. mSIGNA doesn't do any validation itself, it depends on Bitcoin Core for that. So it's a full-validation wallet in practice, even though it shouldn't get "credit" for doing validation. |
|
|
|
Multi-sig is more of a developer feature than a user feature. It is nice to know what multi-sig can do in smart contracts. A less complex single-sig client is sufficient for average users.
Given that multi-sig is a key component for good 2FA, I couldn't disagree more.... |
|
|
|
Are there any windows / android wallet which can generate multi-signature address ?
So far, i have found multi-signature address in online services
Other than greenaddress.it, I've not heard of any. I would recommend greenaddress though. I do believe you both have some reading comprehension issues... GreenAddress.it is an online service. This post just above lists three desktop clients which support multi-sig, one of which (Electrum) is also available for Android. |
|
|
|
You won't find an option named "Android debugging" in Settings. Correct name is "USB debugging"*.
* Settings -> Developer Options -> Debugging -> USB debugging.
FYI the Developer Options are only visible if you've gone through the unhiding procedure. If they're not visible, then USB debugging is disabled, and you're safe from this attack vector. Coinbase isn't a good wallet because you can't access to private keys. You will have to trust them and if their server is down, you can't access your Bitcoin. They can easily steal your Bitcoin if they want to. Recommended wallets are This is a good list IMO. To help you decide: Some wallets do strong (server-assisted) encryption of the wallet stored on your phone. If you lose your phone, a determined thief who is able to root your phone can steal wallets without strong encryption. Strong encryption: GreenBits, Hive Wallet. Brute-forcible encryption (takes longer than no encryption, but still stealable): Bitcoin Wallet. No encryption (just a PIN check): Mycelium Some wallets offer better privacy than others. Bitcoin Wallet is the best in this category; the other three share your transaction history with a centralized service as part of their operation. Some wallets need to trust a centralized service to tell them about new inbound transactions, and to broadcast outbound transactions on the wallet's behalf. A centralized service could theoretically lie to the wallet -- it could withhold an inbound transaction or make up a fake inbound transaction. Mycelium and Hive Wallet fall into this category. Bitcoin Wallet and GreenBits do not depend on a centralized service for transaction verification. Of those listed, only GreenBits offers two-factor authorization. (Of course, for 2FA to be effective you'd need a second device, e.g. a different phone or a laptop.) All of the listed wallets are shared source, i.e. their source code is published and viewable. However Mycelium is not open source, you may not modify it nor redistribute it yourself. The other three are open source. |
|
|
|
I want to use Armory's Python library for running a watch-only wallet on a machine unable to store the entire blockchain.
I'm not sure how you'd go about implementing a watch-only wallet using Armory without having the entire blockchain. Armory is designed to require it. If you want some Python software to implement a watch-only wallet, something Electrum-based might fit your needs better. After running make on the Armory Github source, which files are required to import armoryengine.ALL?
FYI you don't need to build Armory from source in order to use its libraries, you can just use one of the distributed packages (unless of course your target platform isn't among those supported). I know that doesn't answer your question, though.... sorry I don't know the answer, but my guess would be most of the .py and .pyd files except the BitTornado stuff, although I really don't know the details. |
|
|
|
as well as services using multi-sig.
You might want to make the distinction between multi-sig providers, where a trusted third party controls one key, and standalone wallets, where you and/or your associates control all of the keys. You might also want to make clear that some online wallets offer optional multi-sig, whereas others require multi-sig. Additional mult-sig providers (whom you need to trust in some ways): https://www.bitgo.com/https://trustedcoin.com/ (also available as part of Electrum's 2FA) Standalone wallets: ArmorymSIGNAElectrum |
|
|
|
This wallet DOES have my email associated with it, so that's good news, I suppose?
It is... it means it is possible (although a small bit painful) to recover your funds, even in the worst case. What can be done at GA's end with this info?
tryexcept is a GA employee, I'd wait for his response, perhaps he can help. (edited: oops, looks like he beat me to the punch) Might be a good idea in the GreenAddress UI to make a note that "more is better" (?) to prevent others in the future from making this mistake?
I agree, if someone enables only a single 2FA method that offers no recovery option, it would be nice to warn them of potential issues. |
|
|
|
Thanks. But a question still remains unclear: are these new change addresses (beyond the first three) covered by the original seed? Or in this case I'll need to do a new backup?
All of the change addresses (and normal addresses) are covered by the original seed. |
|
|
|
I'm posting this here just 'cuz I'm not sure where it should go... already tried emailing for support (over a week ago) but got no reply as of yet, so...  Hmm... the one time I emailed them, they got back to me the next morning.... GAuth is working fine for other sites I use it with (LBC, BC.INFO, etc) so it's not likely a time-sync issue.
I'm not sure what the technical issue might be. FWIW it's working for me at the moment. I *do* still have my mnenomic for the wallet, so hopefully that means that I can, somehow, still get the bitcoin out of this wallet, if the 2FA problem/issue cannot be resolved? How would I go about doing that, exactly?
The whole point of 2FA w/multisig wallets is that you can't access them without your 2FA... if there was a simple recovery procedure, that'd mostly defeat the purpose. I take it you only set up one 2FA method, with no backup method? Did you ever add an email address to your GA account (you can't add one now because it requires a 2FA code)? If so, it is possible to regain access to your funds even w/o GA's help but there will be a pretty long delay (probably around 90 days). Let me know and I'll point you towards the directions to do this, in case GA doesn't get back to you. |
|
|
|
It is 12 letters. Second thing is that I used random string generator, with both Lower, upper, numeric,... So bruteforce would be only way, but on so large password I doubt it would be worth trying.
(26 lowercase + 26 uppercase + 10 digits) ^ 12 = over 3 thousand billion billion permutations (for comparison, that's somewhere around the number of grains of sand on planet Earth). If it was in fact generated randomly, it's completely unbruteforcible. I think anything more than 9 characters is considered pretty strong.
It's somewhere around there, but it depends on the details. For example, if it was only lowercase letters and 10 letters long, and if it was for a wallet that doesn't use key stretching (e.g. MultiBit Classic, Electrum), then it would cost me somewhere around $2,500 - $3,500 USD in compute resources & power to brute force, and it could be done in a few weeks. It might be even cheaper to create specialized software that'd run faster and cost less to run, but that's harder to estimate. |
|
|
|
|
Show Posts
