IP address x.x.x.x exceeded the request-per-interval threshold with Y requests

General
1
  • I am getting regular %mining-on messages, which folks have said is the only current way to verify you’re actually mining?
  • However, I am getting the following message for a specific IP address.
  • I tried adding this IP to my firewall rules to block traffic - when I do this, I am unable to get the %mining-on messages (Even after multiple restarts). So, I’m currently running as-is.

image
image1042×389 153 KB

2
  • I killed and restarted the process and I’m finding more consistent %mining-on logs.
  • However - does validated blocks at 269 mean that I’m only synced through block 269? The current block height is at least 1,479 per DogeMonster’s blockchain stats page.
  • If that’s the case - why would %mining-on log? Is my client actually trying to mine when the block itself is so old (and therefore, not actually available to receive a block reward?). This seems like a hokey logic if it’s true.
  • Is there a way to shortcut a new miner to start at a specific block height? When I stop my miner and restart it, it does retain memory of the last block it attempted.

image
image1014×460 177 KB

3

we are working and plan to release today or at latest tomorrow significant syncing improvements.