It is weird that Armory seems to accept your custom location to start with, but then looks for the blocks in another place: 2019-01-09 16:15:29 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths 2019-01-09 16:15:29 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = O:\btc-core\ ..... 2019-01-09 16:15:29 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\david\AppData\Roaming/Bitcoin/blocks is not a valid path
I know it is not a valid path, the slashes are switched at the end.
That isn't actually a problem... that's more of a "display" issue with the \'s and /'s in the logs, than the reason it is "not a valid path". I have created the config file armoryqt.conf with satoshi-datadir="o:\btc-core" inside it. Placed that file in my appdata\armory, also o:\btc-core but still get that error in the logs.
I have my Bitcoin datadir set as a "non-standard" location as well... "E:\Bitcoin". My armoryqt.conf file has the following content: satoshi-datadir="E:\Bitcoin"
What settings do you have within Armory itself? Did you set it with "Let Armory run Bitcoin Core/bitcoind in the background"? and did you try to configure the Blockchain and DB paths there? I have both the "let armory run Bitcoin" box UNticked... and the paths are empty... (it shows the correct paths below the text boxes): I manually run Bitcoin Core (GUI client)... and then start Armory afterwards. It seems to find the running instance of Bitcoin Core ok... and also finds the correct blocks folder in the custom location.
|
|
|
I have Bitcoin Core installed and synced.
Did you install/configure Bitcoin Core to store the blocks in a non-standard location during the first run/setup? If you run Bitcoin Core and look at the "Help -> Debug Window -> Information"... what is the value of "Datadir"?
|
|
|
Is there a way to convert a standard seed into a segwit one? I also want to know if I change the first letter on an xpub to z is it then a zpub or is it completely different checksum wise?
Just to go back to your original query... I stumbled across this today and thought of this thread: https://jlopp.github.io/xpub-converter/
|
|
|
Do you guys see the export wallet option from the menu?
I'm not sure what you mean by export wallet? Do you mean backup? or something else? The only thing I can see in the settings is the "Show Recovery Phrase" option which, of course, gives you the BIP39 seed mnemonic that you can use to move to a different wallet. and the sign message feature? This feature I definitely cannot find... but it is just a beta, so hopefully they'll add in more features as they go
|
|
|
I've just checked the website and apparently, the wallet is out If anyone is interested in trying it. It says Beta though so It may not be what we're expecting. Downloaded it for shits and giggles... it doesn't look too bad. Has dark and light themes which I appreciate (I prefer dark). Seems to support a large number of coins... NOTE: adding a large number of coins causes the program to lag a bit (and suck up lots of network bandwidth) during initial startup as it tries to refresh all coins etc. Generates bc1, P2SH-P2WPKH and "legacy" addresses (for Bitcoin anyway)... labelled as Default, Compatibility and Legacy, respectively. However, it appears to be generating Xpubs for all 3 address types... instead of Z, Y and X that I know Electrum generates... So, I'm not sure if this may lead to issues later. EDIT: Ian Coleman BIP39 tool says these xpubs are invalid! but bip32.org will accept them??? Has builtin exchange functionality with ShapeShift and Changelly. Other than that, it's an 80+megabyte download and definitely looks a LOT more polished than the "alpha" that I previously posted about.
|
|
|
Honestly, that is very strange... it seems like your connection to Electrum servers specifically are being blocked. It is possible there is an outgoing firewall rule blocking your connection... But I'm honestly just guessing really.
Are you running on Windows or Linux? Are you running via a VPN or using TOR or any other "custom" network setup on your PC and/or router?
|
|
|
I'm currently connected to the following: Server: dedi.jochen-hoenicke.de Port: 50002 I'd also try: electrum.hsmiths.com NOTE: You can't click on the servers shown on the "Overview" tab. So, in the Network dialog, make sure you click the "Server" tab at the top... and "uncheck" the 'Select server automatically' box... then you should be able to enter what you want in the box (or double click the servers in the list below). After selecting the new server, if you don't see the "green" dot... try closing down Electrum and restarting. As for recovering the coins, it is complicated by the fact that you're trying to recover from what is effectively a "multisig" address. You can't just import a private key (or seed) into another wallet and away you go You'd probably need to manually create and sign the multisig transaction... not impossible, but not exactly a "couple of clicks" type activity either
|
|
|
I just tried and was able to create a new 2FA wallet and it retrieved the ToS for TrustedCoin fine. Maybe its a DNS/routing issue on your end? Can you view https://api.trustedcoin.com/#/electrum-help So, I guess, your options are to either wait and try again later... or restore without the 2FA. If you go for the 2nd option, it'll basically revert to the same functionality as a 2-of-2 multisig wallet where both sets of private keys are in the same wallet... you might want to consider moving your coins to a new wallet to prevent any issues further down the road. If you aren't pressed for time, maybe wait for a bit and try again later to see if the TrustedCoin works? EDIT: see if you can access this in your browser: https://api.trustedcoin.com/2/tos?billing_plan=electrum-per-tx-otp
|
|
|
Terms of Service? Are you using a "2FA" wallet that uses the TrustedCoin service? What is the seed type shown as when you started to restore the wallet?
|
|
|
Am I on an older version (2.5.4) and should I just keep working through the server list?
Wait... you're using version 2.5.4 of Electrum??!? Yeah, that'll be your issue... older versions are known to have sync issues. Update to 3.3.2 here: https://electrum.org/#download
|
|
|
Click the coloured dot in the bottom right corner... and see what the number of blocks showing under "blockchain" is...
If it isn't showing "557502 blocks" or higher, then the server you are connected to is lagging and not updating properly. Try switching to a different server.
Also, what colour is the dot in the bottom right corner? Is it green?
|
|
|
i accidentally deleted my electrum wallet with BTC on it from my computer! But i still have the private key.
Do you mean that you uninstalled the Electrum program by accident? As opposed to deleting the actual wallet file from your PC? If you just uninstalled the app, your actual wallet file will NOT have been deleted. It is stored in a folder structure that is normally "hidden" by default. In this case, you can simply reinstall Electrum and it will automatically find your wallet file again. However, if you actually deleted the wallet file (reformat, deleted appdata folder etc) then you will need to restore using the 12 word seed mnemonic that you have.
|
|
|
Seeing as how it is a single address, if you goto a block explorer and lookup that address, how many transactions do you see?
Also, what country are you in? Is it possible that your country has started blocking traffic? I recall that Russian users have had issues with Electrum...
|
|
|
The directory '/home/my idrectory/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Possibly stating the obvious... but did you follow the suggestion in the error message and use "sudo -H..."?
|
|
|
I can't think of a single reason to not use bech32 (segwit, ḅc1.. addresses).
Most exchanges don't support bech32 addresses so people have difficulty withdrawing to their wallets. Pretty much this is the biggest reason preventing widespread implementation of bech32. Lack of support. It is a catch-22 situation... users won't use it until services support it... services won't support it until users are "demanding" it. For now, you can get the best of both worlds, universal address support and segwit benefits by using the nested segwit (P2SH-P2WPKH) "3" type addresses
|
|
|
Edit: Sad thing is the OTG cable for the Ledger S is f**-ing expensive. 30% of the price of the device. And i read somewhere a generic OTG cable won't work.
There is no difference between the OTG cable sold by Ledger and any regular one.
Yeah, can confirm 100% that any OTG cable should work... Ledger isn't doing anything "proprietary" here... I have a cheap-as OTG micro-usb to USB socket adapter that I got from AliExpress for $1 (incl shipping)... and a very short USB-A to micro-usb cable. Have used successfully with Ledger (and Trezor) and Mycelium, on an old S5. Haven't tried with my newer phone which is USB-C, as I'm still waiting for AliExpress to deliver the adapter As for the Ledger X... I don't need storage space for 100 coin apps... and I don't really need BT support either, think I'll stick with the Nano S (and Trezor One) for now
|
|
|
Yeah... sounds like an issue with the Mycelium servers. Probably a timeout so your wallet updates to the info it has, ie. "zero"... Then when you refresh, it connects and finds the correct info. If you're concerned, just check your addresses on a blockexplorer... if the BTC is still there, then your coins are safe. The only time you really need to worry is when you see a transaction that you did not create and send!
|
|
|
|