token
tutorials from the website.
geth --testnet
?
geth --testnet --mine
geth attach
, and then for example:> eth.mining
true
> miner.hashrate
885210
web3.fromWei(eth.getBalance(eth.coinbase))
I0425 12:18:30.510606 7634 worker.go:348] 🔨 Mined block (#818956 / 569708c0). Wait 5 blocks for confirmation
...
I0425 12:19:13.502412 7634 worker.go:447] 🔨 🔗 Mined 5 blocks back: block #818956
eth.mining
and miner.hashrate
geth attach
eth.mining
true
miner.hashrate
0
eth.syncing
false?
miner.hashrate
again? Does it stay zero, or was that just a spike?
--mine
?
top
display? Does it show geth
using CPU?
net.peerCount
?
miner.hashrate
15
net.peerCount
3
net.peerCount
3
miner.hashrate
0
net.peerCount
4
admin.peers
mtr
if you can.
mtr
, and see if it shows packet loss. Intermittent packet loss can easily cripple your connection stability.
mtr
lets you see what hop that the packet loss starts at: if it's lossy from the very first hop, then it's probably your Wi-Fi reception.
d
to cycle between mtr
's display modes, by the way.
?
s then it's just a product of Wi-Fi packet loss, yeah.
?
s) are fine if the ones after them are fine.
r
to reset the statistics.
miner.hashrate
30
miner.hashrate
20
miner.hashrate
40
geth
after each network change, just in case?