It's probably still loading it's wallet
What does the debug.log say?

On linux, you'll have to switch to the user running bitcoin and do something like (untested, since i don't have a daemon running on the testnet, hence i have no way of verifying the complete path)

have you followed this tutorial:
https://github.com/keepkey/multibit/wiki/Export%20and%20limited%20import%20of%20private%20keys
?

exit code 0 usually means successfull..

https://bit.ac/contact
tells you the name of their company

https://www.companydatabase.org.uk/company/10567776/4541181/bitbase-ltd
tells you that bitbase is indeed a company, albeit, it's registered under a different address as the address listed on their site.

https://www.gov.uk/complain-about-a-limited-company
tells you how to file an official complaint against a LTD company

Wether or not you follow the official route by registering an official complaint, or try to wait it out some longer is up to you. (a lot of companies in this business tend to respond really slow, sometimes taking weeks to answer a ticket)

you can't cancel a transaction in the literal meaning of the word... There are 2 things you can do tough:
1) stop rebroadcasting the transaction, and wait untill most nodes drop it from their mempool
2) double spend the inputs that were also used in the stuck transaction in a new transaction with a higher fee.

T9 cost = 1,250 USD (plus S&H + customs)
T9 hashrate = 12,5 Th/s
T9 power draw = 1686 Watt
Your electricity rate = 8 cent/Kwu

http://www.coinwarz.com/calculators/bitcoin-mining-calculator/?h=12500&p=1686&pc=0.08&pf=1&d=595921917085.41600000&r=12.50000000&er=2530.11820000&hc=1250

At this moment (current diff, exhange rate and block reward), it'll take you 126 days to break even... BUT:
- the diff changes every 2 weeks (usually, it goes up, but not allways)
- the price BTC fluctuates
- the block reward will halve in a couple of years
- no "extra's" were included in the price (shipping, handling, customs fees, shelves, cooling, network, cabling,...)
- bitmain is known to have "less than perfect" customer support... They have 3 months factory warrantee, and have been suspected of selling used miners, broken miners,... Or simply not honoring their very short warrantee period at all)

This image still doesn't show the transaction id's, nor does it show any unconfirmed parents/double spend indication/dust outputs... But based on this image, you added a fee less than 1  sat/byte for one of the transaction, so you cannot use viaBTC.

The other 2 transactions *could, potentially* be accelerated by viaBTC, but based on this image, there is no way to tell this with a degree of certainty..

If you post the transaction id, we can have a look and give you an approximate estimation...

sweeping a private key is basically generating a transaction whose outputs go to the wallet you're using to sweep the key...  Since you generated a transaction, there will be a transaction fee. Because of the huge mempool backlog, the transaction fees per byte of transaction data are going trough the roof (well, theoretically, it's because everybody is outbidding eachother, and not because of the backlog, in reality, the outbidding is a result of the backlog)...
You could use bitcoin core or use electrum to create a non-HD wallet and IMPORT the private key instead of sweeping it

Maybe if you told us which wallet software your friend was using, somebody could point you to a way to export the private key.

No problem... I was in the middle of adding the complete calculation, but one of my servers went down, so i was called away... Here is the rest of my post:

A moonlander uses 5 Watt, a rPi (as controller) also uses 5 Watt (approximately).

Let's assume you have a powered usb hub that doesn't draw any extra power, 10 moonlanders controlled by one rPi...
The total numbers would be:

costs = 10 moonlanders + 1 Hub + 1 Rpi + 1 Psu + network cabling = BTC /USD/EUR
power draw = 11 * 5 Watt = 55 Watt
hashrate = 10 * 1.2 MH/s = 12 Mh/s
Power cost = 10 cent/Kwu??? (at my place, i actually pay 27 cents, so you'll probably have to redo the calculation)

If we use this link: https://www.litecoinpool.org/calc?hashrate=12&speedunit=MH%2Fs&difficulty=240940.12682341&price=25.67&currency=USD&power=55&energycost=0.10
We can see that at current diff, price and block reward, this setup would make ~16 USD/month.

Not bad, but i can only assume that your hardware costs would be several hundred bucks, so it would take a long time to break even...
Do note that the diff and price fluctuate, so those 16 USD/month is only at this very moment... Also, it seems like 1.2 Mh/s is rather optimistic, and it's unsure if the power draw would only be 5 Watt if you run it at 1.2 Mh/s

First, please move this topic to the mining (altcoins) subforum.. This subforum is dedicated to hardware for bitcoin mining

Secondly, do you mean something like this: https://bitcoinware.net/collections/gridseed-dual-ltc-and-btc-miner/products/futurebit-moonlander-scryptusb ?

1.2 MH/s @ 5 W (+ power draw of your controller)

quoted

and verified

If you want to gain experience, i'd either suggest looking up a good faucet rotator, or install a testnet wallet and claim a couple testnet BTC.

Faucet rotators can probably be found here: https://bitcointalk.org/index.php?board=212.0
But fair warning: if you use faucets to collect dust inputs to your wallets, you might end up paying a fee that is higher than your wallet balance in order to spend these dust inputs!!!

Also, it's far more profitable to get a minimum wage job and convert 1 or 2 bucks and hour to BTC compared to claiming from faucets...

First things first: there never was a fixed fee of 0.0001 BTC. 0.0001 BTC was just a "lazy" option of wallet designers/services that didn't want to calculate the proper transaction size and multiply it with the best fee at that time. So, instead of calculating the optimal fee, they just overpayed by sticking to a 0.0001 BTC fee. However, optimal fees are so high lately, the 0.0001BTC does no longer cover a lot of transaction sizes.

The fee is calculated in this way:
transaction size in bytes * optimal fee in satoshi/byte = optimal fee for your transaction in satoshi

The transaction size for P2PKH (= most standard transaction) is calculated as:
tx size =~ nr of inputs*147 + nr of outputs*34 + 10 + number of inputs

Since at this very moment, there is a huge backlog, people outbid eachother, so the optimal fee in satoshi/byte is really high... This drives up the average fee spectacularly... IF either the number of broadcasted transactions goes down, or more transactions fit into a block, i suspect the fee will go down again.

I don't follow all the politics around UASF, segwit, BU,... But rest assured: many people are working on (conflicting) sollutions... So expect the average fee to go down sooner or later...

For the time being, you can allways use my tool to calculate the optimal fee for a transaction, so you don't over/under pay: http://www.mocacinno.com/page/feeestimate

You have to realise your old transaction will probably still exist in the mempool of several nodes.
It means there is still a chance this old transaction will be confirmed. If you want to avoid this at all costs (even if the odds are small), you have to re-use the unconfirmed outputs as input for a higher fee transaction.

In that case, read the post by achow101: https://bitcointalk.org/index.php?topic=1933569.msg19201753#msg19201753
or restart your wallet with -zapwallettxes

If it has sync'ed and verified 404977 blocks, it's not completely sync'ed yet... At the time of writing the height is 468699.
Before panicking or searching any further, i'd try to make sure your wallet was completely sync'ed

I was typing up about the same message
The thing i wanted to add: if you're not in a hurry, you can always try to open the debug console and issue the command abandontransaction "txid".
If this doesn't work, either read achow101's post here: https://bitcointalk.org/index.php?topic=1933569.msg19201753#msg19201753 or close your wallet, and re-start it with the -zapwallettxes , it'll rescan, so it'll take a while.

Both command should have the same net result: your wallet will no longer know about your stuck transaction, so it will stop rebroadcasting it, and it will allow you to re-use the unspent outputs to generate a new transaction (in this case, you're double spending the outputs)

No,

Bitcoin core will keep rebroadcasting your transaction... This way the nodes will not drop it from their mempool, so it will not return to your wallet without an intervention. (abantontransaction or zapwallettxes, to lazy to look up if the spelling of those comands is correct tough)
If you post the txid, i'll see if viabtc is an option for you.

Stop right there... Don't mine with your CPU, don't mine with your GPU... Not even to learn the ropes.
Just for fun, i calculated how much BTC you could potentially mine with a server with XEON CPU's and 6 of the best GPU's available, turned out to be about $11/year for running 24/7, power costs not included.

If you want to learn how to mine BTC, invest some cash in geccoscience's latest USB miner or buy a second hand antminer S5 or something. You'll never break even with this gear, but at least your hashrate will be high enough to find a couple of shares now and then... A GPU won't even find enough shares to properly register on a pool.