If your "send" transaction is showing as "unpaid" like this:


it likely means that you clicked the "save" icon instead of clicking "Pay"... (or possibly that your transaction failed to broadcast to the network, but it should give an error message if that happens).


To correct this, tap on the transaction, you'll see this screen:



Tap the "Pay" button, and you'll be prompted to select the fee etc:



After setting the fee rate to what you want, tap the "OK" button, and you'll be prompted to confirm:



If you're happy, tap the "OK" button... you'll go back to the "Send" overview screen... and after a short delay, your transaction status should change to "Unconfirmed":



If it stays as "unpaid", then it essentially means that your transaction has not been broadcast for some reason and is only stored locally on your android device. Check your network settings (3 dot menu -> Network) and make sure you are connected to servers:

To recreate a 2-of-3 wallet in Electrum... you absolutely require 3 master keys... Electrum will not allow you to use individual private/public keys to create a multisig.

Electrum will only create a multisig from seeds or master keys... To be able to recreate and spend from a 2-of-3 multisig wallet using Electrum you need, at a minimum:

- 2 seeds or 2 master private keys
- 1 master public key

That would allow you to recreate the wallet and be able to spend from it... as the wallet file would contain the necessary private keys to be able to sign transactions.

If you also had 3 seeds or 3 master private keys (or some combination that resulted in having 3 seeds and master private keys in total) then you would also be able to recreate the wallet file.


No. There is no way to determine what the missing xpub is... if you only have 2 xprv's (or 2 seeds), then without either the 3rd seed, xprv or xpub, there is no way you can recreate the wallet in Electrum.

There are just so many red flags here...

The domain was first registered in February of this year... this "exchange" has basically no history. Considering they claim they setup in 2017... and basically don't have any history.

The basically identical but similar named coinetrux (instead of coinedux)...

The fact that there support team forwarded you to links for "trust" reviews instead of answering your question as to why your account was locked etc.

scamdoc gives it a score of 1%: https://www.scamdoc.com/view/528875

And as the others have mentioned... "deposit to enable withdraw" is a very well known scam... do not give them any more money than you already have. It is 100% a total scam and should be avoided.

Doesn't sound like any wallet that I know of... the only one I know of that puts a balance in the lower left corner is Electrum, but that doesn't use "Big numbers" and it doesn't have the balance with a yellow background.

There really were not a lot of desktop wallets around back then... mostly a lot of webbased services... are you sure it wasn't a web wallet? (especially because you were using faucets)

hashcat should be much faster than btcrecover. Hashcat is written in C (which is a compiled language), whereas btcrecover is written in Python (which is an interpreted language).

If hashcat isn't using your GPU, then most likely it is a driver issue, or your GPU is not supported... I would suggest you start reading here: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_do_i_install_hashcat

And thoroughly read the "How does one install the correct driver for the GPU(s)?" and "GPU device not found, why?" sections of the FAQ if hashcat is not using it properly.

What GPU do you have?

How exactly did you "invest"? Do you just remember "buying some BTC" or something?

The point of my line of questioning is trying to figure out what wallet you might have used... or where you might have bought the BTC from so that you can figure out exactly what these 32 characters are... and whether or not the 2 sets of 32 characters need to be put together to make a 64 character HEX private key... or if they're something else entirely.

Without knowing exactly how you got the BTC, or where you had stored it... these 32 hex characters may have nothing at all to do with BTC...

So, where exactly did you find these 32 characters? were they written down on paper? where they in an email? are they marked as "BTC Key" or with some other notes to indicate that they're actually related to Bitcoin? Or did you just find 32 random hex characters somewhere and you just believe that they're related to Bitcoin because you "invested in 2010 2011"?

You can shortcut some of this process by using ElectrumG (as it should allow you to recreate the multisig)... basically, you'll need to restore your 2FA wallet in Electrum (BTC version) using the 12 word seed and use the "DISABLE" option when prompted if you want to keep or disable 2FA.

Also, DO NOT set a password on the wallet file... otherwise you won't be able to open in a text editor...

What this does is create a copy of your 2FA wallet that contains TWO xprvs and ONE xpub which you can use to recreate the multisig in other versions of Electrum.

After the "disabled" 2fa wallet is created, you should be able to open it with a text editor and copy the the "xprv" from the x1/ and x2/ sections and the "xpub" from x3/ section of the "disabled" BTC wallet file. Once you have the two xprvs and one xpub, you can do the following in ElectrumG:

You can then create a multisig in ElectrumG (BTG version) using these "keys" to recreate the wallet in BTG.
- New/Restore
- Multi-Signature Wallet
- From 3 co-signers, require 2 signatures
- "use a master key"
- paste xprv from x1/ and click "Next"
- Enter co-signer key
- paste xprv from x2/ and click "Next"
- Enter co-signer key
- paste xpub from x3/ and click "Next"
- Add password if you want

This will generate a BTG multisig wallet in ElectrumG that should match the 2FA wallet from Electrum and have your BTG showing (assuming there is some BTG on those addresses)


NOTE: it may take quite a while for the wallet to sync... as there don't seem to be too many BTG electrum servers still running... I could only find 2

Any chance you can document this solution somewhere to help the community out? Or are you looking to "sell" your knowledge?

a wallet.dat is a database file... if you interrupt Bitcoin Core in the middle of a write operation, then the file will be damaged.

The database has a set structure... much like how a Bitcoin transaction has a set structure. If you mess up a Bitcoin transaction raw hex... ie. you put things in the wrong place, or you put bad data in, then the transaction parser will output an error when you try to decode that transaction.

Same with the wallet.dat file... it is expecting the data to follow a set layout... if it doesn't, then the app flags it as "bad" and errors out... The app is not able to figure out how the file is damaged, all it can tell you is that it is damaged...

You might get lucky and it might be something unimportant like a label... and all your key data is actually "OK" and you can possible extract it using tools like PyWallet... or you might get unlucky and it might corrupt all your key data.

A corrupt wallet.dat should not be an issue... because, as the Bitcoin Core devs have advocated since the beginning, you have backups of your wallet.dat... right? riiiiiiight??!?

What makes you think that this is a Bitcoin Private key?

Was it written on a piece of paper (or in a text document etc) labelled "Bitcoin Private Key" or something similar (like a paper wallet printout etc)? Or was it just 32 hex characters that you had noted down somewhere? Are there any notes or indications as to what software/system these 32 characters came from?

If you can identify where these 32 hex characters from, you might have a better chance of figuring out how it leads to a private key.

Yeah... sounds like it was most likely just a cached file somewhere in amongst it all. I've had similar issues with other applications before where recompiling doesn't seem to be picking up the latest changes and then magically it starts working at some point and I can't figure out why!

Anyway, glad you got it fixed.

Wait... so your copied/renamed the wallet file while Bitcoin Core was running? If so, that is highly likely to result in wallet file corruption...

As far as I'm aware, there is no "one size fits all" method to be able to fix it... As it depends on what exactly was being written to the wallet file when it was renamed/copied etc.

If it has been corrupted so badly that PyWallet is unable to open it using --dumpwallet, then it could prove quite difficult to recover. You might have to try --recover and see if it is able to extract the keys and rebuild a new copy of the wallet.

Otherwise, you can try the bitcoin-wallet tool and see if the salvage command can fix it...

Ok... not that I think it is the problem... but what are the file owner/group and permissions for your bitcoin/src/qt/res/icons/bitcoin.png file?

After creating and copying to that directory... mine were set incorrect and I had to change to 644 and change from root:root to the user account like the rest of the files in the "icons" directory.

Also, can you post a copy of your bitcoin.png file to a file hosting service... I'll try and use your file, it might be that the PNG is in the wrong format? (unlikely I would think)

So, I had a play with it... managed to get the bitcoin-qt.exe in Windows Explorer showing the modified icon:



However, within the app it is still showing the original



To get the custom icon showing... I actually had to manually delete all the *.o (object files) in the "bitcoin/src/qt/" and "bitcoin/src/qt/res" directories and then use make

It seems that just changing the .ico file etc was not enough to trigger a proper recompilation. So, I'm guessing, if you have already made the project, then tried to change the icons, that it will indeed be using the "old" resources.


And finally... I managed to get the "in app" icon changed:



This is defined by the bitcoin/src/qt/res/icons/bitcoin.png file

Again, I had to:

in both of the following directories:

Then from "bitcoin/src" run make as normal...

No, you're fine... I was talking to fxsniper who posted just above me

Did you then update all the references to those filenames in the code and makefiles?

If you look here: https://github.com/bitcoin/bitcoin/search?q=*.ico

You can see that references are made in various resource file/makefile code to specific filenames... have they all been updated?

Personally, I would try with a "clean" copy of the Bitcoin Core source code... and just try compiling Bitcoin Core itself with just modified icons to see if you can determine which icon files are the ones you need to modify.

Once you have that sorted, you should be able to do the same to your altcoin (and find/modify the necessary references in the various resource and make files etc)

"rebuilding" the block database will not necessarily redownload everything... it will start by processing the block data you already have on disk until it finds an invalid/corrupt block... and then it will continue to "sync" from that point (downloading/processing blocks as "normal").

If you're lucky, the corrupted block file(s) will be one of the most recent file that was being written to when you disconnected the drive, so it should reindex using mostly just the data you already have on disk.

If you restart Bitcoin Core and then click "OK" on the "rebuild the block database" prompt, it should reindex automatically. Alternatively, you can start Bitcoin Core with the -reindex commandline argument and it will begin the reindex without the prompt.

Well apparently you haven't... otherwise your app would be showing the correct icon file!

Jokes aside... have you tried doing a search for all image files located in the source code directory tree? ie. go into the base folder when you extracted the source code and then try:

etc... to make sure that you have found and edited all instances of the image files?


Also... did you rename any of these from "bitcoin.xxx" to "yourcoin.xxx"?

Do you happen to be using an AMD ryzen 3000 or 5000 series CPU on one of the 4xx or 5xx series chipset motherboards (B450/X470/B550/X570)? There have been issues surrounding USB and AMD Ryzen 400/500 series motherboards causing random dropouts of USB connectivity...

Refer: https://www.tomshardware.com/news/amd-suggest-possible-fixes-for-usb-connectivity-issues

Yes... use the getwalletinfo command... in the JSON return, there is a "scanning" value that is set to either false or contains the details of the scan progress: