Is this for testing or "real mining"?
Because the internal miner was removed since: v0.13.0 (release note: https://bitcoin.org/en/release/v0.13.0#removal-of-internal-miner).
Although there's a RPC call for testing purposes and reasons written in the link.

Code? it's still in github: https://github.com/bitcoin/bitcoin/blob/master/src/miner.cpp | miner.h.

Just do exactly what you did when creating the "new Electrum wallet" with both uncompressed and compressed private keys,
excluding the step when you've added a password.

I will also ask for your password before sending txs, signing txs and messages.

Do the instructions in the post above to load your wallet.dat.
For the console, first enter: walletpassphrase "your_passphrase" 300,
then you can now use dumpprivkey "bitcoin_address";
you should indicate the bitcoin address, not its public key.

I can't understand the question completely, but based from what I get: you're trying to retrieve your private key from a lost wallet.dat just by using the same "passphrase"?.
But some newbies are misusing "passphrase" from "mnemonic seed" from wallets that supports it,
if you're positive that it's from a Bitcoin Core client, then it must be your wallet's passphase and it's not possible if this is the case.

Those are all of the "unconfirmed transactions" that your node had accepted, both newly broadcast and not yet mined.
For the time, it's Epoch timestamp and you can use this online tool (as you requested): https://www.epochconverter.com/

You can find the answers in this bitcoin core documentation, including why it has a block height: https://bitcoincore.org/en/doc/0.16.0/rpc/blockchain/getrawmempool/
And everything RPC command-related info by using the menu on the right side.

So you're talking about my comment to your artwork about a typo.
Hmm, I distinctly remember that there's no credit link whatsoever in that post when I merited it (it's about 3hrs later) so, you must be lying.

Otherwise, I wont send any merit since I personally dislike "copy->edit arts".

Too bad, the earliest in the "Ending soon" category will end in 5 days 17 hours.
And FYI, they got a bonus for early betters, so it's best if you pick and bet on the events that will happen after a week or month.

There's a drop-down list: "Select Category" in the betting tab, use it.

The node where it was broadcast will save it in its mempool then relay that particular TX to its peers and those peers will also save and relay it as long as it complies with their relay/default settings;
after a short while, it will eventually reach a miner/pool's node.

For the meantime if it didn't get mined, it'll stay in the node's "mempool" as long as it wasn't "mined",
eg. saved in the data directory of their bitcoin core as mempool.dat.

It will work;
@both of you: but it didn't in the linked topic because it was mentioned that the balance was held by an "imported address" which wont be restored by the SEED.
It was somehow resolved by OP after saying "transferred" which either meant "imported, swept the prv key or sent the bitcoins".

There's no relation between the fees and the amount being sent, it's the number of available UTXO when used together in a transaction.

Additionally, if the user somehow created two "wallet names" in the settings,
he can restore the second account by changing the derivation path from m/44'/0'/0' to m/44'/0'/1' "1" for the next account and onward.
The only problem is those old SEEDs which were just a backup of the log-in details.

Make sure to use the smaller resolution with the original aspect ratio.

Or just set the width and don't indicate the height, this way, it'll automatically adjust the correct image aspect ratio based from the width.
But do not do it vice versa (do not set the height and no width), it'll look horrible on mobile with low-resolution
(it will stretch to fill the indicated height while using the device's small width).

For example: Your image in the OP became stretched horizontally because the height didn't matched the ratio of the original width & height.
use this instead: [img width=640]yourimagelink.jpg[/img]

You mean just those three "code 43 error" cards?
That's quite a vague error code, mainly because of hardware, installation or every kind of issue, so it's hard to pinpoint with so little info/test.

In my personal experience, I once got that error with a card that died because of an overheat issue.
Just like yours, it is still recognizable in "device manager" but wont work the usual.

For the test, try to install each card (solo, one at a time) to a separate machine and connect it to the monitor to see what's wrong.

Also, I've requested the mod to move this to Mining (Altcoins),
just look for this topic in that board later.

It's a wildcard character when the program that's reading the file have no idea what the data stands for.

Those "recognized" characters happened to be decoded because those parts somehow matched a valid character's string, but that doesn't mean that the data represents that character;
Those are pure coincidence except for the part: "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" which was purposely added in the genesis block.

Use Bitcoin Core (open Bitcoin-qt, then open window->console)

Type: getblockhash 0 to get the block hash of the genesis block.
This will be the result: 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

Then type: getblock 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f 0
To "view" the genesis block in HEX.
Or type: getblock 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f 2
To view the human readable format.

Not synced? Use these online tool instead: https://chainquery.com/bitcoin-cli/getblockhash | https://chainquery.com/bitcoin-cli/getblock
for height 1+.

No spoiler, DIY

Hardware wallets are supposed to be immune to such hacks,
the problem must be the client, address changing malware (clipboard hijacking) or social engineering tactics.
Because if it's the seed, all of the wallet's balance should be wiped by now.

Questions:

• 1. Is the address: 32ZVUuEqNHmN4E3nEGwQ8G4L2awHyM9B7K belongs to you?
  Because you've mentioned that almost half of the amount was sent, so this must be your change address.
• 2. The address: 34Ad7ccMtEhcuN9j1YWvQwcQiwjoT2YGST also belongs to you?
  If #1 and this are true, then that transaction was probably sent with your consent (unintentionally because of the possible reason above);
  if not, there's a problem with your HW.
• 3. Have you tried to send the same amount to another address prior to this "hack"?

In simple words: Bitcoin wallets clients doesn't work like a wallet.
All of the available bitcoins are stored in the blockchain (nodes) but can only be moved/spent using their respective private keys.
The wallet files (eg. wallet.dat) contain the user's "private keys" (encrypted if it has a passphrase), not bitcoins.
The wallet (eg. Bitcoin core) have the capability to "search" the user's "balance" from the blockchain.
Get it now?

Can you answer the unanswered question from your thread (Bitcoin wallet):
Why did you need to open your wallet.dat without using bitcoin core or What's your goal?

That sounds like a double-spent transaction that still lingers in their database.
Or TXIDs inserted in to their database by other means.

Well, it's indeed possible to add fake transactions in wallets/database but not the blockchain itself.
The link on this topic however leads to an "Oops page" and OP mentioned that it was a result of a command (that I guess he'd executed).

What is the name of this "company"?
Be aware that there are tens of thousands of scammers in this whole "investment" industry specially with cryptocurrencies.

It's also dangerous to run an unknown command given by someone you don't know, plus it's a common "double-scam" attempt.
It might have compromised your system or got your funds stolen.

BTW, that transaction hash isn't valid and there's no other unconfirmed transactions going in to your receiving address.
You can check it yourself by pasting it in the same blockexplorer: https://www.blockchain.com/btc/address/1M1u8GsLE97NZVLVoTv3h3FajHeiKJAqDs

What I can tell is: this isn't a problem of a "low fee" unconfirmed transaction.

[2] Your link didn't lead to any unconfirmed or confirmed transaction.
There's no way to create a fake txid, it should lead to a valid transaction, otherwise it won't appear anywhere.

[3] Yes yesterday, 1-7sat/byte might take hours to get a confirmation, but all should be mined by now since it somehow managed to "clear-up" after a couple of hours.
Refer to this graph to find the exact hours of the "mempool clogging": https://jochen-hoenicke.de/queue/#0,24h

[1]This is somehow confusing, you've mentioned that you are "participating", then now you're sending to an investor

Anyways, if the problem is just the transaction fee, you can use RBF (Replace By Fee) if you're the sender
or CPFP (Child Pay for Parent) if you're the receiver.
But if it's something else, like a successful double spend, there's no way to "fix" it.

A few questions that might help solving your case (if not, to identify the problem):
1. What client/wallet did you used?
2. Did your link from Q number 2 lead to an unconfirmed transaction yesterday when you searched for it?
3. If you don't mind, what is the address(es) used as input for that transaction? (since you're willing to show the txid, I guess you wont mind sharing the address)

Manually? That's more troublesome than loading the wallet in the correct client.

If you really need to find the balance (spendable?) without syncing the client, you just have to import the master private key to a light client that supports it(eg. Electrum).

How to get that key?
Remember your other thread about importing a wallet into another wallet?
That dumpwallet file contains the Master Private key, it was saved to the location of your bitcoin-qt.exe if you didn't specified the directory.

Try to make a new folder in the same directory where you created "BitAddress" folder and check if that folder is also marked as sharing folder.
If it is, then it's your desktop or the directory where it is located is the one that's shared ('coz anything in it will be shared too).

I've also downloaded the source (https://github.com/pointbiz/bitaddress.org), extracted the zip but it isn't shared.

Your AV might have quarantined the executable(s)?

Just follow these simple steps (if you have an AV, put an exception for the bitcoin installation folder):

• 1. Download the v0.18.1 installer from https://bitcoin.org/en/download
• 2. Install it over the old version; don't worry about the data dir, it wont be deleted.
• 3. Double click bitcoind.exe or Go to the directory of the executable and Hold CTRL+ALT+Right Click on an empty space within the directory,
  select "Open command window here" then type bitcoind
• 4. Open another command window (using the same steps above) and type in your preferred bitcoin cli command.
  Ex. bitcoin-cli getblockchaininfo (it should work without '.exe' but if it didn't, add it)

Tried it, it worked for me and I've used the same OS  

BTW if it didn't work, you should add server=1 in your bitcoin.conf like I said above.
Go to (hold WIN+R; type %appdata%, open bitcoin folder) %appdata%/bitcoin, then create a new file named "bitcoin.conf" then edit it.
Or just download the default/configured sample from the 2nd post and paste it there.

Correct for bitcoin-qt,
but for bitcoin-cli, bitcoind should be running as well.

That error means that you've given the wrong call, it must be bitcoind.exe for Windows(10) machine.
You can also just double-click the executable since you're on Windows 

But if the problem is in the RPC interface config:
Try ranochigo's post above, but if it didn't work, put server=1 instead or together with it.

You can read the config's description in the same resource link he provided under "RPC API" drop-down list.