What you have created is a non-expiring "request"... it's like creating an invoice and sending it to a client...

If all you want is an "address" that someone can send funds to, then click that entry in the list, then click the "address" tab at the top-right of the "Receive" page:


NOTE: It is only pending, because has detected that no funds have been sent to that address yet, so the "request" has been filled So you will be able to receive the funds sent to that address.


Alternatively, you can use "View - Show Addresses" and then click on the "Addresses" tab and select an address from that list.

OSX App Store? I wasn't aware that Electrum was available on the Mac App-Store...

The only legit location I know of is the download section at electrum.org (https://electrum.org/#download)

Is it possible you downloaded a fake version from the app store? Is it still listed on the OSX App Store? Can you provide a link?

Your wallet data ends up in the "%AppData%\Electrum\wallets" folder. This is likely to be something like: C:\Users\YOURUSERNAME\AppData\Roaming\Electrum\wallets

In the "wallets" folder you'll find all the individual wallet files listed by the name chosen when the wallet was created. The "default" wallet is usually called "default_wallet"


Refer:
Where is the Electrum datadir located?: https://electrum.readthedocs.io/en/latest/faq.html#where-is-the-electrum-datadir-located
Where is my wallet file located?: https://electrum.readthedocs.io/en/latest/faq.html#where-is-my-wallet-file-located

In that case, your "pathing" is more than likely going to be "OK"... and Armory is looking in the correct directory for the block data that it needs. So, I'm fairly certain it is just a corrupted database.


Don't forget to report back with the results!

Just to be 100% sure, when you run Bitcoin Core, what value is displayed as your "blocksdir" when you open "Window - Information"?

If that says C:\Users\Owner\AppData\Roaming\Bitcoin\blocks then that setting is just fine...


It's quite possible, that running the older version has resulted in some incompatibilities in the Armory database(s)... You can try the "Rebuild and Rescan Databases" option from the Help menu in Armory and then restart.

Have you tried anything to rectify this issue yet? For instance, have you tried the "Rebuild and Rescan Databases" option?

- What are the specific versions of Bitcoin Core and Armory that you are using?
- What is the block count showing in Armory?

You said you had 4.0.1, so you will need to look for the version of the installer that you used here: https://download.electrum.org/4.0.1/

Then download the matching .asc file... so if you used the installer named "electrum-4.0.1-setup.exe", you would need to download "electrum-4.0.1-setup.exe.asc". Then follow the directions  for your OS here: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/

Surprisingly, they actually relented on this at some point... The newer versions of Exodus now shows your 12 word seed mnemonic when you create the wallet (and gives the option to view it at any time).

So, while it still has some other "features" that I dislike (inability to manually set fees, for instance), at least it doesn't require you to commit funds to actually test wallet restoration

Does Electrum not work like BIP39 in the sense that you start with a random seed (ie. very large random number)... and then convert that seed to the mnemonic phrase? As opposed to generating a mnemonic phrase and then going from that to the seed?

It's been such a long time since I looked at the inner workings of the Electrum code

What version of Electrum were you using? And did you ever do the digital signature verification when you installed it?

That all seems a bit "wasteful" and/or convoluted... I'm not sure why you would want to send your data outside of your local network (even with TOR)?

Why not just keep it all internal? Or are you concerned that your ElectrumX server could get hacked and then the hackers could read the logs from that to determine which connections (and therefore which transactions/addresses etc) are your personal ones?

Short Answer: No, you do not need GPG.

Long Answer: Installation of Bitcoin Core does not require GPG... but it is recommended. GPG is used to verify the cryptographic signature of the compiled binary files... this is to help assure the user that the compiled binary files that they downloaded are indeed legitimate (and not fakes/possibly malware). Note that Bitcoin Core will work fine without GPG installed, but the end user cannot be 100% sure they used a legitimate binary installer unless they verified it with GPG first.

Pywallet does not have any such facility. It is written and distrbuted in a scripting language (Python) so you can inspect all the code by simply opening the .py script in a text editor.

To know if you have it installed correctly, you run it and see if it works. Generally something like "python scriptname.py --help" or "python scriptname.py --version" to see the script help and/or version number respectively will tell you if you have Python, the script and any dependencies installed and working OK.

They're just talking bullshit and guessing... there is no way to simply "look" at a given hash and say "there are definitely symbols and numbers in it"

That could be a problem with the site and not the dicebot.

After their upgrade, it would appear that Bitvest have modified the API and possibly removed the ability to change the seed... there is nothing the Dicebot can do if the site doesn't support the functionality.

Ask Bitvest if their API still supports changing the seed

Bitcoin Core doesn't create seed mnemonics... so I'm not sure what wallet you actually used??!?

There have been a few "scam" wallets that use names similar to "Bitcoin Core" that give pre-generated seeds and will steal funds... specifically this one: bitsblock.io

If you used that website, I would recommend you immediately transfer any funds to a different wallet and then stop using any wallet that you have created with the seed mnemonic you received from it.

PyWallet works fine as it is... you just need to make sure that you have the appropriate password to be able to decrypt the private keys.

If the wallet is encrypted, there are no modifications that can be made that will allow you to view the private key data without the password. Do you have the wallet password?

Sadly, this doesn't appear to work as one might expect...

Firstly, when attempting to build the docker image, it struggles with the git version:



If we modify the Dockerfile to use the current git version(1:2.17.1-1ubuntu0.7), then the docker image build goes ok:



However, during the building of the binaries using docker with this command:

It will stop with an error saying that it can't find a git repo



If you then create an "empty" git repo using "git init", and have the .tar.gz files extracted to it... we get a slightly different git error...



So, then we try "git add" and "git commit" etc to create a local version of the repo... it will still error out as it can't seem to deal with the 'locale' files during the build and creates a "*" folder instead of the actual proper locale folders





which then causes this failure:



I even tried manually downloading the locale files and extracting them into the correct location, and it still errors out.

---

However, if you simply do ONE initial "git clone" from the Electrum github repo, all problems will disappear and the build process works flawlessly...


build the docker image:


checkout 3.3.8:


build the binaries:

---

So, either the 3.3.8 "tag" release .tar.gz on github is missing some critical files... or there is something in the Docker build image that absolutely requires that you have cloned from the github repo to work properly Anyone have any ideas?

In the meantime, I'll continuing experimenting to see if I can work around the "locale" error...

How exactly did you create the message in the first place? Did you use Electrum?

If so, try and create the signed message again from within Electrum, but this time... make sure you also take a screenshot and post the screenshot here so we can see!

It's possible that you've done something a little "non-standard" that is preventing us from being able to verify your message (given that the format you have posted your message in is NOT the format that Electrum outputs)

I'm not sure I understand what you mean... there is an issue with the device itself so when you're asked to enter the PIN you can't see the numbers?

The output you are getting is from an "encrypted" wallet... it has a password set... That is why you are getting:
Without the wallet password, you will not be able to access the private keys!

If you know what the password is, you can specify it when running pywallet (or enter it when it prompts you).


If you aren't 100% sure what the password is, but you have some idea of what the password might be (ie. number of characters in the password and possible combinations of words/letters/symbols etc) then you might be able to use something like btcrecover or hashcat to try and bruteforce the password.

If you have no idea what the password is, then you have ZERO chance of bruteforcing the password and any bitcoins in that wallet are effectively "lost"