I'm on Windows 10 and I've installed 96.5. Here's the logs: (ERROR) BDM.pyc:268 - setSatoshiDir: directory does not exist: C:\Users\****\AppData\Roaming\Bitcoin
...
(ERROR) BDM.pyc:197 - DB error: C:\Users\****\AppData\Roaming/Bitcoin/blocks is not a valid path
Do you actually have Bitcoin Core installed and fully synced? If so, what is the "datadir" value that Bitcoin Core shows in the "Window -> Information" screen?  If you don't have Bitcoin Core installed, then Armory will not be able to function properly, as Armory requires a non-pruning instance of Bitcoin Core to be installed and fully synced to function properly. Armory directly scans Bitcoin Core block data and uses the Bitcoin Core RPC interface to send/receive transaction information etc. |
|
|
|
The thing is what about those ppl who daytrade and have btc and altcoins then? I mean surely they keep their coins there if they daytrade right? I mean they aren't sending btc and altcoins to their wallets every night and resending it daily as that would be expensive?
Of course they leave their coins on the exchanges... and that is a risk that they take (and must accept) if they want to participate in day trading... jerry0, it's great that you take your time and think about things, but you are really overthinking pretty much everything involved with bitcoin and ledger and wallets. People have given you plenty of very good solutions, and you just go "yeah, but what about XYZ?"... At some point, you need to act... otherwise, you end up in the situation you have now... where you put off doing anything about your dim screen for 7 months, your ledger eventually died and now you're back here going "what should I do? But what about XYZ?"  |
|
|
|
I'm not sure what risk you think there is in putting in a promo code? How do you think using a promo code could be used against you? All a promo code does is tell the checkout system to apply a specific discount to your order. It might have some requirements like Nano X added to order to receive 50% off Nano S... or it might be "set shipping to $0 if 2x Nano S added to order" etc... Using a promo code is not going to infect your PC with malware or reveal your seed or mean you get sent a modified ledger... At worst, it might "link" your purchase to someone providing an affiliate code, but they're not the same as promo codes... affiliate codes don't tend to provide a discount. And given affiliate codes tend to get posted all over the place, being linked to an affiliate doesn't really much to anyone... except perhaps the person who owns the affiliate code... and they don't even get details of your purchase, they just get some $  |
|
|
|
As long as the response from the forum members will be positive like they actually earn even a small profit then I will try to download your application and will likely to start from a small amount. In my side, I can say that it is a little bit risky as I am not that familiar on how it operates but I think I can handle it as long as your application is safe.
You realise that the dicebot is NOT a "guaranteed to make you win" type system right? It is just a tool, like a web browser... that lets you automate certain aspects of your betting and allows you to create or run custom scripts so you can try various "systems" or strategies... It is NOT guaranteed to win, it does NOT increase your chances of winning etc... the odds are exactly the same as if you used the site manually through a web browser. Anyone that tells you otherwise, is a fool... and if they're trying to sell you a "winning" script, they're a scammer. |
|
|
|
|
Thanks for the headsup... I've left a message over there. It is most likely that they are using Python3.8... a lot of old scripts written for Python2.7 simply do not work under Python3, due to non-backwards compatible changes made to Python3
|
|
|
|
C:\Python38\decrypt_bitcoinj_seed-master>py decrypt_bitcoinj_seed.py
Don't use Python3... I believe that "decrypt_bitcoinj_seed" will only work with Python 2... As per the install instructions on github: Unfortunately, there are quite a few differences between Python2.7 and Python3 that "broke" a LOT of things... so there are numerous old scripts that just don't play nicely with Python3.  |
|
|
|
So the words aren't all on either list!!
That is problematic, as it means it is neither a BIP39 wallet seed mnemonic, nor an Electrum wallet seed mnemonic so if it's a blockchain password and I don't have a wallet ID can I scan my old PC to find this "wallet.aes.json" file? any special software or method to target such file??
Try the recovery methods at Blockchain.com... https://login.blockchain.com/#/helpIf you don't have wallet-id, but have an idea of what email address you might have used... and you still have access to the email address, you can try the wallet-id reminder option. You can also try the "Forgot your password" option and see if it works... unlikely given you have nonBIP39 words... so also try the old recovery: https://login.blockchain.com/wallet/forgot-password?guid=do I have to enter the 12 words live online? or can I do it offline ( to a hardware wallet or software) to generate public/ private keys?
Yes, it's an online web-based platform... so if you want to try blockchain.info recovery, you have to do it via their website. any difference between blockchain.com/.info? No, blockchain.info was moved to blockchain.com a while ago... the .info domain now redirects to .com |
|
|
|
Nothing installed, clean Win10.
Removed the wallet and rebuilt it from seed - everything was ok.
Must have been a "glitch in the matrix" then Possibly some sort of corruption in the wallet file or something that was causing it to send or request "bad" data from the servers which was getting your client disconnected/timed out (banned? )... I've honestly never seen that behaviour before. Glad you managed to fix it by simply rebuilding the wallet tho. |
|
|
|
The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.
Unknown error
That could potentially point to the fact you're connected to a "bad" server that is attempting to send you the "please upgrade to our malware version of Electrum" error message. "Normal" servers should not be sending error messages that the client is unaware of... which is what generates the "unknown error". Go into the network settings and manually try a different server. If you keep getting the "unknown error" message, you could try taking the raw, signed transaction from Electrum and try broadcasting it manually... You can do this by right clicking the transaction in your Transaction History, select "View Transaction", then click "Export -> Copy to clipboard":  That will copy the raw, signed transaction data to your clipboard. You can then paste and broadcast it manually here: https://live.blockcypher.com/btc/pushtx/If there is indeed something wrong with the transaction, it should hopefully give you a more detailed error message. |
|
|
|
How do you know the secure element inside is destroyed? How would you know?
Once the board and all the chips are in tiny pieces (or "dust" if you hit it long enough)... disolved in acid... or a big blobby molten charred mess... it's fairly safe to assume the secure element is destroyed. The internals aren't much... pry open the case before starting and the point of destruction of the internals would be fairly obvious.  I don't know why but I regretted not sending the btc to coinbase/binance in the meantime when my nano ledger s had that dimmed light. I mean have you heard of cases of coinbase or binance accounts getting hacked? I keep some coins there in binance but very little but i never felt concerned of my funds in binance.
Yes, Binance got hacked once: https://www.wired.com/story/hack-binance-cryptocurrency-exchange/There have been other "big name" hacks like Bitfenix, Cryptopia and of course Mt Gox... and a lot of smaller name exchanges that have been hacked over the years. Have a look here: https://selfkey.org/list-of-cryptocurrency-exchange-hacks/There is a reason people say "don't leave large amounts on exchanges"... as always: "not your keys, not your coins." |
|
|
|
I took a look on amazon.com and the cable you mention seem to cost ten dollars... the cheaper one on amazon is like 5 dollars. Of course i can't buy it now since im outside the US.
Almost any electronics store or mobile phone store should be able to sell you one. They sell them everywhere here, like supermarkets, gas stations, dollar stores... it's just a very basic, very common cable... Pretty much any android mobile phone would have come with one as a charging cable (prior to the move to USB-C which is really only the newer devices). https://www.aliexpress.com/wholesale?SearchText=micro+usb+cableWell, the reason you wouldn't return it is because of security reasons right? Like if you send it back to them, and somehow they enter the pin correctly even with three tries, then you are at risk?
Correct. For my piece of mind, securely destroying a $50 device is a small price to pay. How would you securely destroy the old one?
Fire, a hammer, acid... take your pick. Just need to make sure that the secure element inside the device is destroyed. |
|
|
|
So, any success?
I have been helping the OP walk through the process of checking the wallet.dat that he had recovered... unfortunately, it appears that either the OP used two wallets or his recollection of past events is incorrect. After syncing Bitcoin Core and then opening the old wallet.dat, there were only 2 transactions showing (both from 2013), one incoming and then one outgoing (about 8 hrs later) that spent all the funds from the first transaction. The result being that the wallet.dat was completely empty and has been since 2013. We tried exporting the private keys from the wallet.dat and importing them into Electrum in case there was some issue with the Bitcoin Core rescanning and/or the fact that the wallet was synced on top of old blockchain data... and Electrum showed only the same 2 transactions. OP is adamant that he must have had leftover BTC somewhere and that there was a 2nd wallet.dat that randomly appeared during a search of the HDD for "wallet", but that his HDD "lagged" when he attempted to access it and that no sign of this wallet has been seen since. OP has already tried to use Recuva on the HDD, but nothing resembling a wallet file was found. I would note that the (empty) wallet.dat that the OP originally found, was found in a directory underneath a folder called "Windows.old", which itself was in a folder created by a backup app called "backup4all"... my suspicion is that any other wallets that were used, might have been lost during a Windows system upgrade or "restore"... and the data on disk was subsequently overwritten some time in the last 7 years. |
|
|
|
I can't use my iphone charging cable for it right?
No. That will be a "lightning" connector... completely different. Do you think its worth buying one right now where im located now to try to see if that would work?
Cable shouldn't cost more than $1-$2... so it's not a huge expense if it turns out that the original cable is fine and the device is just dead. Well would you say its better keeping it in a box as oppose to having it in a fanny pack zipped up if my apartment is humid? Again almost all apartments here are humid where located... no escaping that unless you want AC on all the time.
It really makes no difference. Like I said, if it's not airtight, moisture will get in. You'd be better putting it in a ziplock bag or other airtight container with some of those silica packs if you're concerned about humidity. You agree best option is buy a new one first and then put the seed in right? Then if seed works, send back old nano ledger for a replacement so i have an extra one? Like don't just send the old one back to a new one for replacement first right?
Personally, I wouldn't bother sending the old one back... once I had a new device, and had restored using the seed mnemonic, I would (securely) destroy the old one. |
|
|
|
Lucius is correct, decrypt_bitcoinj_seed is definitely the best option for seed recovery from a MultiBitHD wallet file if you know what the password is. I also have a modified version of the "decrypt_bitcoinj_seed" script, to help with MultiBit/MultiBitHD issues, back when MultiBit development was stopped. They're available here: https://github.com/HardCorePawn/multibit_recoveryThe "find_unspent_multibitHD_txes.py" script will just dump keys for any "unspent" coins. But I would highly recommend you try the "decrypt_bitcoinj_seed" script first!  |
|
|
|
Given how it existed from the start and he envisioned a system with one-cpu-one-vote, it's not hard to see why it isn't that much bigger. He probably didn't expect Bitcoin to shift from CPU to GPU and to ASICs nor pooled mining.
There was a comment in one of the early emails purported to be from Satoshi Nakamoto where here said: At first, most users would run network nodes, but as the network grows beyond a certain point, it would be left more and more to specialists with server farms of specialized hardware. A server farm would only need to have one node on the network and the rest of the LAN connects with that one node. If that email is indeed from Satoshi, then it would seem that they were fully aware of, and expecting, that mining would end up the domain of "farms". |
|
|
|
Yea the ledger doesn't turn on when connected to my laptop. Do you think its possible its a cable issue and getting a new cable could fix it? But where would i buy a new cable? Again, im outside the US at the moment.
It's not a "special" cable... it's just a standard micro-USB cable... they're available pretty much everywhere. Speaking of humidity, what if you keep your nano ledger s in the box it already came with? Does humidity affect that or it would have no effect if its inside the box? I put my nano ledger in like a fanny pack zipped up. But again, I left it there for a long time before this and had none of these issues.
Unless it is an airtight box (which the ledger ones are not), then there is still a way for moisture to get in... that's the thing with electronics... quite often they will work "fine" over extended periods of time while humidity is busy taking it's toll on the internal components... until one day "poof" it stops working. The dim screen was probably a good indication that your device was defective and/or slowly dying. You should have sourced a replacement months ago when the issues with your device first became apparent. Where do you guys store your ledger nano then? I mean it could be humidity but then again i read of ppl who said their devices dimmed and dimmed and won't turn on and none of them mentioned humidity. But humidity most likely played a role here?
You're asking for absolute answers to scenarios with multiple, unknown variables... the only way you'll know 100% what happened to the device is if a suitably qualified technician pulls it apart and inspects it. Humidity is one option, a defective unit with bad components or some latent manufacturing flaw is another. But is there any risk of going to a repair shop or trying to find someone that could fix it if it indeed doesn't work anymore? But doing this would mean you definitely can't get a replacement right?
Of course, you'll void any warranty by physically opening the device and attempting any repairs. |
|
|
|
I think the OP's question is whether the server code can be manipulated to request that information. Electrum client does have access to the device ID, and it would make sense that it's not sent it to the server, but are there any safeguards prevent the server from accessing the device ID?
As far as I can tell... it is mostly simple request/response initiated from the client... That is to say, the client sends a request, the server sends a response. However, as per the Electrum Protocol, the client does receive "notifications" when it has "subscribed" to receive updates regarding various scripthashes. But this is not the server querying the client as such, it is simply sending a message with the updated data. Also, from my limited testing on my personal electrs server, the requests made from the client when using a Trezor, look much like the requests made from a client using a "standard" wallet. I don't see anything obvious in the raw request data that would enable you to differentiate between the two types of wallets. I realize this is an Electrum thread, but I am reminding readers that Satoshi Labs grabs the device # for sure and even uses it in the connection url's ----- bothersome for sure!
I guess that's because the wallet "client" and "server" are essentially the same thing when using the Satoshi Labs web wallet... but yes, deviceID being transmitted in URL plaintext is a bit of a privacy concern. |
|
|
|
Sounds like the device is most likely dead. I vaguely recall, from previous statements you have made, that you live in a relatively hot/humid environment... it's possible that the high humidity has killed your device. Your options are: 1. Contact Ledger support and see if there is anything they can do. or 2. Buy a replacement hardware wallet (can certainly understand if you chose a different manufacturer! ) and restore from the seed mnemonic backup or 3. Restore your seed mnemonic into a BIP39 wallet like Electrum I would suspect that there isn't much Ledger can really do to help... if the device isn't even powering on, the options for recovery are very limited... and I'm not sure I would want to send an "initialised" hardware wallet to anyone anyway. If you are having issues with support, you might also want to post on the "LedgerWallet" reddit, there support team are way more active over there. |
|
|
|
|
Show Posts
