in Bitcoin Core, I don't see the balance.
Blockchain explorers do confirm that address 1PMoUJpj73FUTbjMiKwJfJoo4fJaUE9bTr still holds 8 BTC. So that suggests there has been no hacking or improper removal of money.
first the older key without rescan,
I would re-import the older key with rescan. I would also make sure the wallet has completely synchronised. ...
The "accepted answer" is technically correct but it's INCORRECT in it's reasoning and doesnt explain that there are actually 2 RPC auth methods for bitcoind (which bitcoin-cli communicates with).
The commandline -rpcuser and -rpcpassword are NOT FOR rpcauth accounts. Thats the first problem that was never mentioned in the accepted answer.
It also ...
The hashing power is estimated from the number of blocks being mined in the last 24h and the current block difficulty. More specifically, given the average time T between mined blocks and a difficulty D, the estimated hash rate per second H is given by the formula H = 2exp32 D / T
txid - hash of the transaction itself
Indeed. It is the hash of the transaction without witness data included (if any).
hash - hash of the transaction itself. If transaction is non-segwit, txid == hash, otherwise in segwit transactions the transaction hash is different.
Indeed. It is the hash of the transaction with witness data included (if any). The ...
generatetoaddress generates a block using transactions from the mempool. It uses the given address for the coinbase output.
generateblock generates a block with the given transactions in the given order. It does not automatically select transactions from the mempool like generatetoaddress does.
Both RPCs are only relevant on regtest and are used for testing. ...