Block is stale error message

fogoat commented 5 years ago

Telegram user stating pool.biblepay.org keeps saying BLOCK_IS_STALE in the error column.

{
  "blocks": 103791,
  "blocks_tip": 103791,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 1051.253582791459,
  "difficulty_pow": 7.550028225481274,
  "difficulty": 1051.253582791459,
  "errors": "",
  "genproclimit": 4,
  "networkhashps": 960.0027597283831,
  "hashps": 626.1982468675625,
  "minerstarttime": "02-25-2019 22:59:01",
  "hashcounter": 28018558,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "Submitting Solution 02-26-2019 11:23:22; ",
  "poolinfo3": "",
  "podc_tried": 23,
  "podc_sent": 3,
  "podc_sent_amount": 521862.4400000001,
  "podc_average_amount_sent": 173376.2259136213,
  "miningpulse": 28587,
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "poolmining_use_ssl": true,
  "pool_high_tithe": 83.45,
  "pool_my_total_tithes": 0,
  "pool_total_tithes": 495.79,
  "pog_difficulty": 763.3974055225635,
  "pog_min_coin_age": 0.95,
  "pog_min_coin_amount": 292.20999999,
  "pog_max_tithe_amount": 9.890000000000001
}

biblepay commented 5 years ago

BLOCK_IS_STALE happens if users chain is out of sync with the pool chain. Please see if they can verify the top block hash, then if bad obviously kill dat files and resync entire chain.

biblepay commented 5 years ago

I just removed the CPID_SIGNATURE_INVALID check from the pool.

fogoat commented 5 years ago

PoW difficulty of 7 would indicate different/wrong chain. I will let them know.

biblepay / DELETED

Block is stale error message #16