With notepad++ i receive only NULNULNUL ....
That's not good.... If you have no wallet file backups, and no seed backups, recovery will be difficult or impossible. 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 to search the hard drive for seeds or master private keys (I'm not sure what the easiest way to do this is, though, so no instructions included for this option...). If you just had a little (you're on Windows, correct?), download and install HexEdit, (preferably to a drive that's different from where your wallet file is stored), and then open your C drive 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, double-quotes and colon included: - "seed":
- "master_private_keys":
If you manage to find one or both of these, along with the string that follows them (as in the example file I posted earlier), it may be possible to recover your funds. Edited to add: if you find one of them, keep searching to see if there is more than one, and save them all in a text file. |
|
|
|
Your wallet file has for some reason become corrupted. 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": [
"0226e2a67847df6a7f46efe9da8b9f6fc7f7d8023f63eef8d636b38203bc56a2d3",
"0389e77e92ca2ab3d721630d2eeef7efc1556fec72dcf0f52b74bf5286a5c4fe94",
"03a31d53b340f76a006984638e5260365cf25f8a49beae1dd29e2606d48f3b498c"
],
"receiving": [
"039bb38c166e55c595891b78325da2025d013ecd5d9694b05e210b48a01168065c",
"0351940ad5247586c6dbfbaeadd38dec431cf97ca7af71fa0552e4c77482dfa640",
"03b75f7d34f2130983e10127d66377eb1f2b1278db96da33dd390779573b405f87",
"03db37551e0dfa2a4c499cd8f64ff3d1f8375fdb7bb8a14af73c6afa7f7a6152b2",
"037777a308fa5bb9bb12bd5de31b6a5d21eb0d94067002236a58dd1787504f1bed",
"02f86a3fd6a2ea654c1ebc65ce01b13c9a700bf77bcd1742b865e223574047f87a",
"03eeb6bd840b2d309254df79cd4554bec50634a897c6f4ff81fbcd87d4f336c8b5",
"02a95c72dd2c5e8a7ef70c764e1a51c0f8910abb23201be0a01c47b091d1fb1bf3",
"03393270a21090a27c84cab77bb94eaf9ef7e1194ccab43e47c031abdacb840aac",
"02fd90ef85469e265326a2a3994daa7d489d2c981d09155021eb58e7bf790ca474",
"03c4cc88a3243d663f92350f58a625c94319b210411d75c4ba10e02dceaedd20c7",
"02ccf9ee6a6cc63cb28e2ff6e46f3a9fe4d14f8efd139fafd3e91d657670da527f",
"0253b5a73f453976414747f1cf0ab6eadabf632d7c51f2504f725fb6fb528516d4",
"03ae45504521514c0a675150937a95775abbaee5e99d85b0e7c91231090de55b8a",
"0349aa147502380ad458648fb535381a902a05938dfbaee4c75dfe4267a28660f2",
"02e22d7e9bdde58ce16627af385df1956091a5e5d0047f356df168df96796adf2c",
"03e560201fbf19a32d7de762a49d50d0c20889a2d509d8ba2fd6a45a296c8d61f1",
"0310fac886fe32afafedb3183f97c836470bc12610c50915797fd2e729d2eb1d78",
"03c800b16bf5787662adfda8dcf0fc99c0f68936c80346c50ec033cf79f0e4ed9c",
"028ac1a7dea5856d201405cc8802fb1198b3dc50884c65c7ae4c79e4ae9da369fb"
],
"xpub": "xpub661MyMwAqRbcGsUXkGBkytQkYZ6M16bFWwTocQDdPSm6eJ1wUsxG5qty1kTCUq7EztwMscUstHVo1XCJMxWyLn4PP1asLjt4gPt3HkA81qe"
}
},
"accounts_expanded": {},
"master_private_keys": {
"x/": "9B961mYKYFV7Bg1zRYZ8ZGw4cE+2D8NF3lp6d2XPe8r87EE8qxVnv/8UA9PxSopPF41RKg9VWR4iyd/rSA6CusnLvkzU8+5Zy9Gb8Fgnu2HpYc7SXHNhiJp8maQjxMCBo8nhXqU3f855ALJGgVlaZflBN06k8XKgOENtCOLrrP0="
},
"master_public_keys": {
"x/": "xpub661MyMwAqRbcGsUXkGBkytQkYZ6M16bFWwTocQDdPSm6eJ1wUsxG5qty1kTCUq7EztwMscUstHVo1XCJMxWyLn4PP1asLjt4gPt3HkA81qe"
},
"seed": "CBjg2RyTk91VOCO9O+X0XlqUoiiBPrTqMcSIOAlJpBP2N9sSgCABTSli5ecy8vpi8JEG3Tkg6aU0wAj0hs74PadfYjpobJLGkR7bDUH5NwZT16DnKzcdsLhnsuHqK+Qp",
"seed_version": 11,
"use_encryption": true,
"wallet_type": "standard"
}
You're looking for missing syntax. For example - make sure all of the braces ( the {s and }s ) match up and that there's a closing brace at the end
- 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 get it fixed, be sure to write down your seed!  Good luck.... |
|
|
|
Any way to mark a thread as "solved"?
Towards the bottom left of the page there's a "lock topic" link you can use if you like (only visible to the OP and to Admins). |
|
|
|
I generated a QRcode of my Electrum wallet, and scanned the QRcode PublicKey with my iPhone - and the iPhone ELECTsUM app took it. It did generate 15 BTC addresses with it. However, none of them are in my Electrum wallet... and the BTC balance in the iPhone app remains at zero! This app has all the red flags associated with a scam...
Good catch, and good point.... it'd be trivial to code up a closed-source app that produced a list of addresses (potentially different for each phone) whose keys are exclusively controlled by the app's dev. |
|
|
|
It was my fault for being a little to hasty and not sitting down and really looking into it as this was my first time using Electrum
There's some truth to that, but... But also fuck ELECTsUM for allowing me to use my PGP public key.
I couldn't agree more, that's some shoddy coding that allowed this. My condolences.... |
|
|
|
Don't worry about these kind of things with mainstream wallets like electrum... some people/miner are still using old bitcoin-qt clients and it is fine.
I take it you're not in IT Keeping software (especially security, financial, and web-browsing related) up to date is very important if you don't want to get infected or hacked (and lose your funds). Running old versions of Bitcoin QT isn't "fine", some versions had major bugs: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures. Is there some way I can get automatically notified when a new version of the Electrum Win wallet is ready for download?
I'm not aware of any built-in way inside the Electrum software, but there is a workaround. 1. Sign up for a GitHub account if you don't already have one. 2. Visit gh-release-watch.com, click Login with GitHub, and authorize gh-release-watch.com to view the email address in your GitHub account. 3. In the Watch field, type in this, and then toggle the Not Watching button to Watching: spesmilo/electrum 4. Make sure a valid email address has been set. Note: I've never actually used this service before, so I've no idea if it's reliable or not.... Should I uninstall the old wallet before installing a new version?
It's not necessary, but it doesn't hurt either. (I will do multiple local and remote backups of my wallet before doing any installs or upgrades.)
That's always a good idea, but it also shouldn't be necessary. The only thing to be aware of is that Electrum 2.x will upgrade your wallet format. In order to downgrade to a 1.x version (not that you ever should need to), you'll either need to restore your wallet from it's seed or use a backup from before you upgrade. Side note: if you do remote backups, be sure you've got a strong password on the wallet, or use a zero-knowledge backup provider such as SpiderOak (and a strong password with them). |
|
|
|
TL;DR - you're probably out of luck.... I downloaded ELECTsUM on my phone thinking it was different than what it was.
To anyone else reading this: ELECTsUM is apparently a watching-only Electrum 1.x compatible wallet for iOS; I don't own any iOS devices and have never tried it. For the master public key I entered the public key that is generated by my GPG Keychain
I'm very confused. I can't think of any way GPG could export anything that looks remotely like an Electrum 1.x master public key, so I can't figure out how you managed to do this.... It then generated 15 wallets
I assume you mean addresses (not that this matters)? the 'next' button [inside the real Electrum client] remains gray and I cannot click it?
Whatever it is you're pasting in, if you got it from GPG, it's surely not a valid Electrum master public key -- that's why the button remains gray. If ELECTsUM accepted what you pasted in as a master public key, then that sounds like a (pretty egregious) bug in ELECTsUM. Can someone please lend a helping hand here?
Regardless of all of the above, if you didn't get a master public key from the official Electrum client, any funds you sent to the addresses displayed inside ELECTsUM are likely lost forever  Edited to add: and if ELECTsUM accepts as input something that isn't at least in the right format of an Electrum 1.x master public key (128 hex digits), then shame on ELECTsUM!  |
|
|
|
Thank you for the explaination. The first thing i thought of reading green address was the green address at mtgox. I believe that was even another thing.
Green address at MtGox was the same thing that MZ linked to (what a surprise that MtGox chose to implement something that was a bad idea....  ) |
|
|
|
i really like it - esp with pipes that way even other typos-file and options will work easily... and it follows the unix-philosphy... i'd really like to help you (and increase my py skills) but i am busy developing monero-tools atm...maybe in a few month FYI a just committed a version with an --exclude-passwordlist option. |
|
|
|
I pm'ed u.
I'll take a look, but FYI it probably won't be for a day or so. |
|
|
|
Yes, that's the other "green address" I alluded to; it was a bad idea and isn't related to GreenAddress.it or the Electrum plugin. |
|
|
|
Im using B. Do you mean to remove half of the seed code and post it here ?
OK, I didn't realize that. seedrecover.py should be able to read an Electrum wallet file, but maybe there's a bug. Two more questions for you.... 1. So, seedrecover.py is for when you have an Electrum wallet file, and most of a seed (and you don't have the password), but the seed you have isn't quite right. Is that what you're trying to fix? 2. Do you think your password is pretty strong? If so, you can PM me your entire Electrum wallet file and remain safe, and I can try to figure out what the bug is. If your password isn't strong, giving me your wallet file would be dangerous for you.... |
|
|
|
It's not a big deal, but it is annoying and an incentive not to update the software.
I have the same issue... it's really not a big deal, and I'm sure there are bigger fish to fry, but it is slightly annoying. Another option might be to change the NSIS script so that it does a IfFileExists before a CreateShortcut, that would at least fix it for me if it didn't overwrite any custom options I've added to the shortcut in the Start menu on Windows. (But again, it's a pretty minor thing....) |
|
|
|
ValueError: Extra data: line 46 column 1 - line 46 column 100 (char 2942 - 3041)
Press Enter to exit ...
How to fix it ? Thanks
Great, I'm glad you're closer... It probably means that you're not loading an Electrum wallet file. If you created a text file yourself, can you please double-check that it looks like this: {"seed": "hGt+sQGFlt7Dhgb3a1kHetNJmlxrMQrZ3D8mheYgVr79ZEGOZK1btAzv44QMwGQ2K+1a/1ct10abxrX56OtvFA==", "use_encryption": true}It must have a { at the beginning and a } at the end, and it must use double-quotes, ", everywhere except for around the last word (true). |
|
|
|
I think a better answer is a combination of the two answers above. The paper wallet is what you need, and the ONLY thing that you need.
As long as you have a working version of Armory on some PC, this is true. It doesn't even need to be online, or be compatible with any version of Bitcoin Core. As tspacepilot goes on to say: Make sure you know how to export your private key and address from armory into some sort of plain text. As long as you can do this, you will not have a problem long term.
And as long as you have a working version of Armory, you can do this. You need to do a Wallet Restore using your paper backup, and then go to the Backup Wallet option and choose "Export Key Lists" as your backup type. This will produce a text file, and although you may need to change the formatting of the text file a little bit to get it to import into another wallet client, it shouldn't be too difficult. It should be noted that you can't export the entire wallet and expect some other wallet client to be able to generate addresses/keys the same way that Armory currently does, instead you have to ask Armory to generate a list of addresses and keys as described above, and import the entire list into the new wallet client. |
|
|
|
I would add Armory to that list as well.
I didn't because doing so seemed redundant... it's dependent on Bitcoin Core for all if its networking needs, so if Bitcoin Core gained split routing, Armory would "inherit" it. Still I think split routing can even enhance the privacy of SPV nodes. Download headers through public channel and send bloom filter requests and outgoing txns through the private channel (tor/i2p/vpn).
Completely agree, e.g. with MultiBit HD and/or other bitcoinj-based wallets if bitcoinj adds Tor & split routing support. It is my understanding that most lite clients today don't even use SPV model but instead use a proprietary 'trust the server' model or if the use SPV they don't use bloom filters.
I think the situation isn't quite that bad. Mycelium uses a 'fully trust the server' model, and Electrum uses a 'query the server for an address' model (but Electrum does do SPV). Even with these two, Tor could help a little (although if they maintain long-term connections to the server, then they're leaking information related to addresses that are associated with one another, despite not leaking the actual IP addresses). On the other hand, MultiBit (Classic and HD), Bitcoin Wallet for Android, and breadwallet are all pretty popular, and they're all "real" bloom-filter-using SPV clients. Also to be fair, multisig wallets w/2FA trade privacy for security, and for some people that's a fair trade. E.g. GreenBits, even though it's a "real" bloom-filter-using SPV client, still needs to get the GreenAddress.it servers to sign their half of a 2-of-2 tx. |
|
|
|
Edit 3: What is this GreenAddress about? Its a widely used term and i dont see a change when having it checked.
GreenAddress.it (practically no relation to the "green address" term you may have seen elsewhere) is a multisig wallet provider. They have an option for their 2-of-2 wallets (which is their default wallet type) that you can enable when sending transactions called "instant confirmation". If you choose to enable it when you send a transaction from your GreenAddress wallet to someone else (the recipient doesn't need to be a GreenAddress wallet), then that transaction is added to a publicly-queryable database which they maintain. The Electrum GreenAddress plugin allows you to query GreenAddress to see if a given transaction has been flagged as "instant". Keep in mind that it's a 2-of-2 wallet, and that GreenAddress exclusively controls one of the two keys. GreenAddress publicly agrees to never sign a double-spend transaction if the user chooses the "instant confirmation" option. As long as you trust GreenAddress to stand by that policy, you don't need to trust individual users. This provides a certain amount of assurance that an "instant" transaction cannot be double-spent (as long as you trust GreenAddress). |
|
|
|
Practically speaking, if some wallet were to implement D&T's split routing, it would probably be a wallet which currently takes privacy seriously. AFAIK, there are only three wallets which seem to fit into this category: - Bitcoin Core
- MultiBit HD
- Darkwallet
These are the only wallets I could find which avoid address reuse, can be used relatively easily with Tor, and do not depend on any centralized service. (I don't think Darkwallet has implemented Tor/SOCKS yet, but it's on their roadmap.) So if anyone were serious about this, that's where they should probably be looking. Also worth noting that the latter two aren't yet considered stable enough for general use by their devs, so I'd guess (it's just a guess) that a new feature request such as split routing probably wouldn't be very high on their priority list.... Edited to add: It looks like bitcoinj might consider adding support for this one day... |
|
|
|
93.0.70 supposed to take care of BDM errors.
93.0.80 supposed to take care of BDM errors.
Now 93.0.82 supposed to take care of BDM, but with a caution.
This all makes me weary a little.
Weary, how? Just to be clear, the BDM issues have nothing to do with your wallet or your funds. If you run into them (I have only once), they are inconvenient, and they can cause a delay if you need to send funds right away, however they shouldn't ever lead to a loss of funds. If the potential delays of having to do a rebuild/rescan before being able to send out funds make you weary, I can understand that. In this case it might be best if you stick with 0.92.x until you're comfortable with 0.93.x. Edited to add: I just noticed your comment in the "0.93 testing release" thread, and that you [opentoe] know all this already, so sorry for implying otherwise.... BTW, Carlton Banks seems to have a slightly unusual setup which could be why he runs into this issue more often then others. goatpig has said that CB's many issues have been helpful to him [goatpig], but I don't think this many issues is common for others (it certainly hasn't been for me). |
|
|
|
|
Show Posts
