Possibly caused by a "bad" server that is trying to phish you with fake error messages in an attempt to get you to update to a fake version of Electrum that will steal your coins. As you have discovered, simply manually selecting a different server from the "Network" settings within Electrum will generally fix this sending issue.

NOTE: the "bad" servers cannot steal your coins. They can only try and send fake messages. The exploit has been patched in Electrum since 3.3.4, so that is why you see the generic "unknown error", rather than the message with a download link.

No worries, glad to (hopefully) be of some help... please do keep us updated whether you are successful or not. It's nice to know what the final result was!

Good Luck!

Possibly some weird DNS issue in your location that was preventing the login process from completing properly... or possibly Bitamp did indeed have an issue in their backend and connections from your location were being "load-balanced" onto a server that was having issues preventing you from logging in.

Anyway, glad that it appears to be sorted... in the meantime you might want to investigate backup solutions (like Electrum etc) in case you experience a similar situation in the future and need quick access to your funds.

Does your wallet have a lot of transactions? like hundreds of transactions? Perhaps if you have "hundreds" of transactions, it is causing issues for bitamp to scan your entire wallet history during login and it is timing out?

As Royse777 asked, are you able to connect using one of the 12 word seeds we've just posted? They're all empty, so there isn't any history to scan etc. so should log in fairly quickly if your problem is being caused by a large transaction history.

That's odd... Is the transaction that puts the money into that address actually confirmed? or is it "pending"? I don't think coinb.in should care either way... it should let you spend unconfirmed coins, as long as the transaction has propagated properly...

When you enter the address in coinb.in, is it showing the same transaction ID for the "input" as the block explorers show?


That's not going to be possible because of this:
iOS == iPhone/iPad

There is no iOS version of Electrum...

Go to a blockexplorer like:

https://btc.com/
https://blockchair.com/bitcoin/
https://live.blockcypher.com/btc/
https://www.blockchain.com/explorer

and enter the Bitcoin address that you believe your coins were sent to... then see if the current balance is non-zero...

If the balance is zero, then the address is empty... so either the funds were never received from the market, or they were subsequently spent. You'd need to look at the transaction history for the address to figure out which scenario is true. You should see this history on the block explorer.

I was able to go to the "generate wallet" page just now and got given a "new" 12 word seed, and was able to "login" using that 12 word seed here: https://wallet.bitamp.com/#/login.html

Try this one and see if it works:

If you're not able to login with that, it could be something on your end (adblocker? browser extension? antivirus/antimalware etc) that is preventing the website from working properly. Maybe try clearing your browser cache etc... or maybe a different browser altogether?

"Missing Inputs" means that it cannot find the UTXO(s) that you are attempting to spend... ie. they do not exist or have already been spent.

You should check that the inputs you are attempting to use actually exist and are unspent.

Then it seems that PyWallet was not able to recover anything useful... it found 6 objects (while scanning the first 8gigs of F: drive) that it thought might be wallet.dat files, but was unable to actually retrieve any keys from these objects.

That could be caused by PyWallet only finding a small fragment of the wallet.dat file on the disk, or possibly that an incorrect wallet passphrase was used when trying to recover.

If dumpwallet (or the hex editor method) is allowing you to export the keys, then you're probably better off just ignoring the "--recover" option in PyWallet for now and just get to importing those private keys manually.

You can speed up the process by either:

1. when using importprivkey in Bitcoin Core, use the "false" value for the "rescan" argument... so:

Until you get to the very last key... then use true... that way, Bitcoin Core will only run a rescan once for all the keys, rather than running rescan every time you run importprivkey (which can take a very long time!)

or

2. You can bulk import the WIF private keys into an SPV wallet like Electrum... it'll load and scan all the private keys in a matter of minutes.

Yes, there is likely to be a minimum of 100 keys (That's what the old keypool minimum was)... at some point I believe the keypool was increased to 1000 keys.


I'm not sure what you mean by this exactly?

If you create a brand new wallet in Bitcoin Core, you will be able to import all the private keys using importprivkey command. It will be slow and annoying, but it will work.

Using --recover with PyWallet... should, theoretically, create a "valid" wallet.dat that you should be able to open using Bitcoin Core... Unfortunately, I do not know of an easy, realiable way to "corrupt" a wallet.dat so that I can test the "--recover" option with PyWallet and see if Bitcoin Core will then load the recovered wallet.dat

OP already solved the problem:

The current steps were made to get into this situation:

1. Binance > Withdrew crypto amount into an address I did not even remember putting there, so this is were it even started going wrong (Binance cannot help me though).
2. For some reason I considered Electrum to be able to open this address so I download the android app and the amount is now as a balance in my electrum wallet (possibly just watching-only but I am not completely understanding this I guess).
[/quote]
You will need to identify where this address came from... it seems you downloaded Electrum after you had already sent the coins from Binance??!?

So, the first question you need to find the answer to is: where did you get that address from? Did you have Electrum installed on a PC before you installed the android version?

What operating system are you running? Newer versions of Electrum have some issues with older versions of Windows, as per the electrum download page:

Basically, Windows 10 should work without issues, Windows 7 can be quite problematic to get running properly, since version 3.0+ of Electrum

Why?

If he had had a "normal" electrum seed, he still would have had the same issue of the "next" button being unable to be clicked... as he had the seed incorrect. It had nothing to do with the wallet being 2fa.

I'd have to be honest and say "No". Most people don't use "12 words" to encrypt/decrypt a Bitcoin Core wallet... Bitcoin Coin simply uses a "passphrase" which is essentially just a "password"...

The user is free to make it whatever they want... from a simple password like "abc123" to something very long and complex like "Th1s Is My Super SecRet P@55 Phrase That Uses Symb0ls Numb3rs and Upper and Lowerc@se Letters And is vErY Long!2020#"

As mentioned in the other thread, if your wallet file didn't have a password, you should be able to search the file for the hexstring: 0201010420

The 32 bytes of data following that string should be a private key (in hex). You can then use other tools like bitaddress.org to convert that hex to a private key in WIF format that could be imported into a wallet.

---

I quickly downloaded a free hex editor called "WinHex"... then opened a copy of an old wallet.dat that has no password... and did a hexstring search:



We use 020101420 as the string to search for:



This finds the following location in the wallet file:



So, now we want the next 32 bytes... a "byte" is TWO hex characters, so we want to copy the next 32 pairs of characters:





In this instance, we get:


We put that into the "wallet details" tab on bitaddress.org and click "view details":



We get the following:



Now, that is just ONE key... the wallet.dat will have multiple locations of "0201010420", you need to find every instance of the hex 0201010420 in your wallet.dat and then get the 32 bytes following that and convert them to a private key.

---

---

Searching for individual hex private keys in a wallet.dat is a long, tedious process... honestly, using the PyWallet "dumpwallet" command is likely to be a lot easier:

for instance, if my wallet file was in J:\Dump\ and called "wallet.dat", and I wanted to store the output in a file called walletdump.txt, I would use the command:


NOTE: When you open the walletdump.txt file, depending on how "old" the wallet file is, you might see a bunch of warnings like this:



That's fine, you can just ignore them... scroll down until you find the line that starts "The wallet is not encrypted":



All your private keys/addresses will be displayed below that. The private key (in WIF format) is the field labelled "sec".

That's why I used the term "mnemonic encoding scheme"... I would not regard it as a "seed" phrase either, as there is no "seed"... As o_e_l_e_o stated, it's just an encoding of the private key data.


Also, I get the feeling that the OP was hoping that they could generate a single BIP39 compatible mnemonic that would restore all of their paper wallet private keys... which is impossible. But the question was a big vague in that respect, so don't beat yourself up about it!

As mentioned in that topic... it only works if your wallet.dat had no password.

If your wallet.dat had a password set, then the private key data is stored encrypted, so you cannot simply do a search with a hexeditor to retrieve the private keys.

Yeah... the important takeaways from this should be that:

1. While you can create a "mnemonic encoding scheme" for a single private key... it will NOT be a BIP39 compatible seed! Restoring from mnemonic to private key will not be possible using a BIP39 compatible wallet

and

2. You cannot create a single mnemonic seed that will restore multiple "random" private keys

NOTE: I DO NOT recommend that you do any of this, it is purely for educational purposes

---

You would have to create an individual mnemonic for each wallet, you cannot create one mnemonic which will recover ALL of your paper wallets, which kind of defeats the purpose really... as you're still needing to keep a backup of some form for each wallet. The only advantage would be that it would be easier to backup/restore without transcription errors than a long bitcoin private key in WIF format.

Additionally, there is no "standard" way of converting a single private key to a mnemonic... you could use a "method" similar to BIP39, ie. using the 256bits from the private key as the "entropy", calculating the 8 bit checksum, and then break the 264 bits total into 11 bit chunks and then convert those chunks into 24 words from the BIP39 wordlist.

WARNING: if you put those 24 words into a BIP39 wallet, it won't generate your original private key/address... it'll generate something completely different!

---

As a worked example, we'll cheat and use Ian Coleman's mnemonic code converter to do the "heavy lifting"...

Let's say that our Paper wallet was as follows:
(Compressed) Address: 19zAL47SZ1xBLiZmwiPt4fK9SSoxxCETfi
Private Key: L3Dt4emdX52UJ9R1gSghpR81sEVuXtv3r17iMRrCWQ1c1TLxCy3D

If we put that Private Key into https://www.bitaddress.org/ we can see that the private key in hex is:



Now using IanColeman's Mnemonic Code Converter, we select the "Show Entropy Details" option:



We can then put in our 64 char hex private key in as 256bits of entropy:



And it automatically gives us a 24 word mnemonic:


However, as noted above... this mnemonic does NOT generate our private key/address:



Instead, to go from our mnemonic back to private key, you need to go in reverse using Ian Coleman's tool... paste the 24 words into the BIP39 mnemonic box, click the "show entropy details" box, then copy/paste the 64 char hex from the "entropy" box into the "Enter Private Key" box on the "wallet details" tab of bitaddress.org:



I DO NOT recommend that you do any of this, it is purely for educational purposes