Amount of BTC transacted is unimportant... It is only the fee "rate" ( calculated in sats/byte or btc/kB) that matters for confirmation time.

Unfortunately, it looks like the network is getting busy again... 30k+ unconfirmed transactions and fees getting up to 200+ sats/byte levels again.

Your transaction is "only" 100 sats/byte... So may be delayed for a bit...

I've accelerated it using ViaBTC tx accelerator and also AntPool.. So, hopefully when either of them mine their next block, your transaction will start confirming

EDIT: looks like ViaBTC picked it up

Sadly, very normal... The blockchain data is quite large... Around 140+gigs these days... And takes a while to download, verify and index. This is why I said to just sync up to 2013. You don't need blocks from today if you haven't sent or received any transactions for 6 years!

It should tell you what date you are currently synced up to... If you cant see the full dialog box showing the current block number and date and time remaining etc... Click the green progress bar at the bottom of the main window.

Once it is at a date you're happy with... You can disconnect the client (click the little network icon in the bottom right corner) and then your computer from the network.

Can't answer that... My tinfoil hat is a different size to yours! But there is no point buying a new computer once your coins are already in a hardware wallet... They're supposedly safe on totally compromised systems...

Granted there is some risk having your wallet.dat on the old computer, even for a short length of time online... But you'd need to assess if you're comfortable with that or not.



Fees are based on the "data" size of the transaction... And NOT the amount of BTC being sent... The data size is mostly dependent on the number of inputs to a transaction. The inputs are determined by how many individual payments you received to your wallet. So if your 50 coins came from 50 payments, you'd have 50 inputs (and quite a large transaction)... However, if your 50 coins came from 5 payments, your transaction would only have 5 inputs and be about 1/10th the size.

Regardless of how many inputs you have, sending all the coins in one transaction should result in less fees overall... As then you would only have 1 output (34 bytes) + 1 transaction data (10 bytes) = 44 bytes of "output" data instead of having 50 transactions with 1 output each (50*34 + 50*10 = 1700+500= 2200 bytes)!  

Fees are measured in sats/byte... So, given current fee levels of like 200+ sats/byte... You're looking at 8800 sats for 1 transaction... And 440,000 sats in total for 50 transactions. (NOTE: this is only the cost of the outputs, the inputs actually cost about 5 times as much as the outputs 148-180 bytes per input)...

Would you be willing to explain exactly what you did in the end to recover your coins? I'm sure other users with similar issues will find it helpful in the future to know what you did to fix the problem

It will also help the "helpers" like myself know what works and what doesn't

according to the BitCore GitHub, the format for the send command is:


Why are you using the -f command? Looking at the "send" code... The argument list is fixed: https://github.com/bitpay/bitcore-wallet/blob/master/bin/wallet-send

Fairly sure you shouldn't be using -f to specify wallet....

The simple answer is: yes.

Only HD wallets are created using a "seed"... so if you haven't already, create the HD account in Mycelium, make sure to write down your twelve word seed, and put it somewhere safe!

You should then be able to sweep the coins from the ATM paperwallet into your Mycelium wallet.

NOTE: There isn't an obvious "sweep" option in Mycelium... once you have your HD account set up, Click the "3 dot" menu and select "Cold Storage"... scan the QR Code (or enter the private key from paper wallet) and after it sync and finds the coins... you can use the "My addresses" button on the "Recipient Address" screen to sweep into your account. (Alternatively, go into your account and select "receive" and copy the address to the clipboard before you select "Cold Storage")

If it says "no input found" then there are no "Unspent Transaction Outputs" or UTXOs that are controlled by the private key(s) you are attempting to sweep... in other words, the address(es) belonging to the private key(s) are empty and have no coins.

Have you confirmed, using a block explorer, that the address(es) for the private key(s) you're trying to sweep still have a non-zero balance and all transactions into the address(es) are confirmed?

NOTE: if the keys were invalid, the "sweep" button would stay greyed out and unable to be clicked. The error you're getting definitely indicates that there are no coins found

Simple "Layman" answer: without password or seed, your coins are gone.

You can try an engage the services of "Wallet Recovery Services"... They have a solid reputation for being trustworthy and have helped others recover their coins.


More complex "Layman" answer: to bruteforce the password you'll need to learn how to use Python  and Python scripts. You'll need to install Python and set it up, and then install and configure "btcrecover" which is a set of Python scripts which can attempt to BruteForce passwords of several types of bitcoin wallet.

Given you are asking for answers in Layman's terms... I'm guessing you are not familiar with command line tools and/or running scripts... in which case I'd suggest you either get busy on Google and start reading/learning or you contact the wallet recovery guys.

MultiBit HD has a built in "Empty Wallet" function: https://multibit.org/help/hd0.4/empty-wallet.html

That should allow you to send all your coins to an address of your choosing.

I've never used it, so I'm not 100% if it shows the transaction fee etc on the confirmation screen BEFORE you actually send the transaction out. You can try and cheap out on fees by messing with the slider in (Preferences -> Fees) but i think it's broken... even though it says Fee is in Btc/kB, it actually just seems to use whatever value is set as the actual fee regardless of transaction size... so I'd it says 0.00010000 btc/kB, the fee will actually be 0.00010000 btc total.

 multiple instances  at the same time would likely cause locking issues with the block data... I doubt you could have multiple instances running off the same datadir at the same time without causing issues and possible data corruption

 you can import one or many private keys, but it would appear that on Android you can only import keys when you first set up a wallet. I couldn't find a way to import keys after the wallet has been first created.


If you have the private keys (or seed of the wallet was an HD wallet) then you can recreate (or restore) the wallet by simply creating a new wallet and importing the private keys again (or restoring from seed).

You say you don't have the a seed and only have private keys, so you'll need to import them into a new wallet.

I have no idea what instructions you're following... or what exactly you're doing... so once you have the command prompt (or powershell) opened where you need it, I guess you should just continue following the instructions

There is a number of different test suites there: http://gobittest.appspot.com/

The one you want for testing WIF keys is: http://gobittest.appspot.com/PrivateKey

Make sure you haven't highlighted a file when you shift+right click...

highlight the folder and shift+right click and you should get either "open a command window here" or possibly "open Powershell window here" (as I think one of the recent Windows 10 updates tried to make Powershell the default instead of command)...

If you really need a command prompt... Press "start"... type cmd and press enter... it will open a command prompt... but probably not at the correct location... you'll need to figure out the path to this "ez setup" folder... and use the "cd" command (http://www.digitalcitizen.life/command-prompt-how-use-basic-commands)

If the next button stays greyed out when you paste your private keys in... then they're not in the right format... are your private keys 51 or 52 characters long, and do they start with a 5, L or K?

Like these:
5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF
KwntMbt59tTsj8xqpqYqRRWufyjGunvhSyeMo3NTYpFYzZbXJ5Hp
L4TT6waRiu1W5CgjPifyGFzCok21mSh2oE9Ly62457nnaJftM14V

Are you making these wallets on mobile or on Desktop Electrum?

No.

If you actually click the "coin control" label it will pop up a little help dialog:

I am fairly sure the "priority" of older transaction outputs doesn't really affect anything these days... i vaguely recall seeing something in one of the Core release notes, but can't find it right at this minute.

Ok, so you mean you deleted/reformatted your drive and you're trying to recover files?

Well, the actual wallet file for Bitcoin Qt/Core is "wallet.dat". If you don't have a wallet.dat file, then your wallet is gone. Unless you can recover the wallet.dat file, there is nothing else for you to do at this point except consider professional recovery services that may be able to run deeper scans on your drive.

Coins can ONLY be sent from whatever address they were sent to... When you send coins to an address, they are associated with that address... and that address alone... it doesn't matter that you have multiple addresses in your wallet... they are all technically separate.

So, to ensure you are ONLY sending from a specific address, you need to use the "coins" tab... if you can't see it from the menu select: "Wallet -> Coins"

You will be able to see exactly which coins are in which address. Select the inputs from the address you need to send from, right click and select "Spend"... only those coins should be used in your outgoing transaction (NOTE: this may mean you cannot send the total balance of your wallet, if other coins are in other addresses).

Also, you may want to disable "change addresses", so that any change will return to the original address. Otherwise, the change will go to a different address in your wallet. (Tools -> Preferences ->  Transactions -> Make sure that "use change addresses" is UNCHECKED):

Yes, you will still incur fees to move coins from one address to another address. It does not matter if the addresses are in the same wallet or in different wallets.

The blockchain has no record of what wallet an address belongs to... as technically, an address does not even need to be in a "wallet"... being in the same wallet does not create any sort of link between addresses. The only way to move coins from one address to another is to put a transaction into the blockchain that reflects this movement of coins... and the only way to get a transaction into the blockchain is to pay fees (or be REALLY good friends with a miner )

I would try restoring your seed to a new wallet and see if it is showing the same issue.

"File -> New/Restore" -> Give is a new name like "RestoredWallet" -> "Standard Wallet" -> "I already have a seed"

If the newly restored wallet is also displaying it incorrectly, it might be something slightly "non-standard" about the transaction causing issues...

I notice that the 0.11632116 was recently (21 blocks) sent on (https://blockchain.info/tx/ebc0912e3f971b8df67765e46a1968c7592d5ed8405d1499136915ab764f4e64)... did you manage to get it all sorted in the end? What solved it?

Electrum on Android shows pretty much the same options when you set the wallet up for the first time:

       

You should be able to select "Standard Wallet" -> "Use public or private keys" and then Paste all your private keys.  NOTE: you cannot "type" the keys in, you can only "Paste" or scan a QR code to enter the key. So you'd need to have all you private keys in a text list so you can copy/paste them.


In any case, if the OP has successfully created a "normal" wallet (I assume they mean a "Standard wallet" with a 12 word seed), they should just sweep the keys (Wallet -> Private Keys -> Sweep) and get all their coins into that wallet.

You can enter a seed created on Desktop Electrum into Android Electrum and it will generate the same addresses/keys...